Introducing a B2BUA for far end NAT traversal

[Joegen Baclor]

I think you have already heard about the recent canary release from SIPFoundry.  In this release, we removed all components that are either not used by most people or are so unstable that it becomes hard to maintain it in a real production environment.  One of the items that needed to go is the proxy NTAP plug in and sipXrelay.  The original intent was to leverage Kamailio as the ingress proxy (which is still the case in canary) and use it as the NAT anchor in conjunction with rtpproxy-ng.  However, we learned that kamailio utilizes record routes to preserve NAT states (2 for each call).  If the call goes in from and back out to the internet, the total record route inserted with the INVITE is 5 adding the record route inserted by the proxy for its own state persistence.  For me, this is a show stopper because we are guaranteed to fragment packets for remote workers.  

So we are using a new approach to this and that is by utilizing a B2BUA to handle remote workers.  This B2BUA will sit infront the open internet and sipx-ng and would take care of NAT and media anchoring.  This is similar, in a way, to sipXbridge but is written in C++ and has a built-in media relay, also written in C++.  The downside to this, is since the ingress proxy already own ports 5060 and 5061, the B2BUA has to sit on a different port, presumably port 5062.  This would require that DNS/SRV records visible from the internet should point to 5062 and not 5060.  Only internal phones will register to 5060 directly, bypassing the need for the B2BUA.

Does this make sense to most people or do you see any problems you will encounter with this approach?   We are expecting to release this feature as an update by next week.  

Joegen

[Kurt Albershardt]

Will this eventually be capable of small volume SIP trunking?


thank you~

[Joegen E. Baclor]

Kurt,

Yes that is the plan.

Joegen

--
You received this message because you are subscribed to a topic in the Google Groups "SIPfoundry users and developers group" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/sipfoundry-users-and-developers-group/PiJnKifvDvw/unsubscribe.
To unsubscribe from this group and all its topics, send an email to sipfoundry-users-and-dev...@googlegroups.com.
To post to this group, send email to sipfoundry-users-a...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sipfoundry-users-and-developers-group/e01c9b36-7955-498c-82e1-7678b143e7f9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Marco]

Hi Joegen,

I think it's a good approach.
How are you designing the solution in a cluster configuration? Will the administrator be able to assign the B2BUA functionality to one or more nodes inside the cluster?

Thank you.

Marco.

[Joegen E. Baclor]

A B2BUA can be assigned per node so there can be multiple B2BUA and load balanced via your DNS/SRV global records.

--

You received this message because you are subscribed to a topic in the Google Groups "SIPfoundry users and developers group" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/sipfoundry-users-and-developers-group/PiJnKifvDvw/unsubscribe.
To unsubscribe from this group and all its topics, send an email to sipfoundry-users-and-dev...@googlegroups.com.
To post to this group, send email to sipfoundry-users-a...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/sipfoundry-users-and-developers-group/a16aee38-bbd8-4d77-9cfc-7edc4a3659b5%40googlegroups.com.

[Rick Cogley]

Hi Joegen - just wondering if this feature has been released already? I'm on sipXecs (2016.02.1.7f726 2016-02-24UTC10:02:54 2e5d52493173) update 0. 

Regards,

Rick

[Joegen E. Baclor]

It's there, yes.

--

You received this message because you are subscribed to a topic in the Google Groups "SIPfoundry users and developers group" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/sipfoundry-users-and-developers-group/PiJnKifvDvw/unsubscribe.
To unsubscribe from this group and all its topics, send an email to sipfoundry-users-and-dev...@googlegroups.com.
To post to this group, send email to sipfoundry-users-a...@googlegroups.com.

Visit this group at https://groups.google.com/group/sipfoundry-users-and-developers-group.
To view this discussion on the web visit https://groups.google.com/d/msgid/sipfoundry-users-and-developers-group/bbf1334f-8ec6-48ac-b6a0-e4f837fdbaaf%40googlegroups.com.

[Rick Cogley]

Thanks Joegen. Sorry to be thick, but in Canary, where can I find these settings. I'm happy to read something, but I can't find anything other than what I had read back when I installed 4.4. Appreciate your pointing me in the right direction. --Rick

On Monday, April 11, 2016 at 11:24:23 AM UTC+9, Joegen Baclor wrote:

It's there, yes.

[Ryan Colobong]

Hello Rick,

If you enabled the sip proxy under System > Servers > Telephony Services, SBC should be automatically enabled (You should be able to see the SBC tick box). Once you have apply the changes to your server, you can configure the SBC under Servers > SBC. On the canary release, you can only configure the log level and the advertise IP (by default if empty, this will automatically detected by the SBC).

Hope that helps.

regards,

--
You received this message because you are subscribed to the Google Groups "SIPfoundry users and developers group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sipfoundry-users-and-dev...@googlegroups.com.

To post to this group, send email to sipfoundry-users-a...@googlegroups.com.
Visit this group at https://groups.google.com/group/sipfoundry-users-and-developers-group.

To view this discussion on the web visit https://groups.google.com/d/msgid/sipfoundry-users-and-developers-group/99cb0cab-fec3-4097-bc1a-b79308fc34d6%40googlegroups.com.