[SR-Users] New user checking on SIP proxying use case

David Villasmil david.villasmil.work at gmail.com
Thu Jul 22 10:15:48 CEST 2021


In case the local telecom wants to send/receive media to/from specific IPs
and this can’t be provided by twilio, you will need to look into
rtpengine/rtpproxy in order to relay the media as well.

On Thu, 22 Jul 2021 at 03:46, Fred Posner <fred at palner.com> wrote:

> Hi Nick,
>
> This type of use case would be perfect for Kamailio. You can use many of
> the available modules such as dispatcher, drouting, etc to accomplish this
> (or even just a simple call in the request route).
>
> Kamailio just handles SIP, so unless you use an program such as rtpengine,
> no media is relayed— it would flow directly from the carrier to twilio.
>
> -- Fred
> (via mobile)
> Matrix: @fred:matrix.lod.com
>
>
> On Jul 21, 2021, at 9:22 PM, Nick Hurlburt <nick at techmatters.org> wrote:
>
> 
>
> Hello all,
>
>
>
> My name is Nick Hurlburt, and work with a nonprofit tech organization that
> provides a software platform for child helplines around the world.  I am a
> new user to Kamailio, and I'm interested in figuring out if my use case is
> appropriate, getting some tips on how to go about it, and possibly
> enlisting some expert help.
>
>
>
> Our service is built on top of Twilio, but we are working in some
> countries where Twilio doesn't have phone numbers.  So in those areas, we
> are working with local telecoms on ways to integrate using a SIP
> connection.  In one particular example, the telecom company can send SIP
> INVITEs but can only address them to a static IP.  However, Twilio needs to
> receive the invite addressed to a fully-qualified domain name (eg,
> example-setup.sip.twilio.com).  The idea arose to use Kamailio as a proxy
> to accept the static IP-addressed request and then rewrite the request to
> pass it along to a domain name.  Then once the connection is established
> between the two endpoints, the media can flow directly between them.
>
>
>
> I have a software engineering background but still coming up to speed when
> it comes to VoIP technology.  I'd be interested in:
>
> - does this sound like a good use case for Kamailio?
>
> - is there any specific documentation you could point me to for this use
> case?  (I have been looking at the Kamailio documentation, but a quick
> pointer could save a lot of time in digging through it)
>
> - if anyone from the community would be open to helping us develop a
> prototype/proof-of-concept instance of this, especially if you're open to
> contributing to a nonprofit on a volunteer or discounted rate, I'd love to
> talk more
>
>
>
> Thank you,
> Nick
>
>
> __________________________________________________________
> Kamailio - Users Mailing List - Non Commercial Discussions
>  * sr-users at lists.kamailio.org
> Important: keep the mailing list in the recipients, do not reply only to
> the sender!
> Edit mailing list options or unsubscribe:
>  * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>
> __________________________________________________________
> Kamailio - Users Mailing List - Non Commercial Discussions
>   * sr-users at lists.kamailio.org
> Important: keep the mailing list in the recipients, do not reply only to
> the sender!
> Edit mailing list options or unsubscribe:
>   * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>
-- 
Regards,

David Villasmil
email: david.villasmil.work at gmail.com
phone: +34669448337
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kamailio.org/pipermail/sr-users/attachments/20210722/402037dc/attachment.htm>


More information about the sr-users mailing list