You might find this useful http://blog.aeriandi.com/2012/10/08/bt-interoperability-testing-a-guide-to-jumping-the-hoops/

You can configure a pair of sofia gateway to dial them through. Set the register param to false. You'll need to provide a password, but just give a dummy value (1234) as it won't be used since they won't challenge for it.

For incoming calls you'll need to set auth-calls to false on the sofia profile, so that it accepts calls without authenticating them (they wouldn't have a password if you challenged them). You'd need to verify within the dialplan that it's a call from BT using ${network_addr} (unless you can ensure the profile can only receive traffic from BT). Alternatively you could create a user directory entry that authenticated any calls from their IP as a 'BT' user (the cidr attribute). The incoming calls won't authenticate based on the gateway as the magic that allows that does so by putting a magic value in the Contact header during registration, which won't be used in this case.

Steve




On 16 July 2015 at 12:25, Andrew Keil <andrew.keil@visytel.com> wrote:

To FreeSWITCH users,

 

Just a quick question that I hope someone can help me with.  I am sure I can solve this myself when BT sort out their firewall, however while I wait 1-2 days I thought I would post this question here.

 

Currently BT have provided me with two SIP IPs and MEDIA IPs for their Sandbox:

 

BT SBC1 IP: Signalling xxx.xxx.xxx.26 (Media xxx.xxx.xxx.25)

BT SBC2 IP: Signalling xxx.xxx.xxx.23 (Media xxx.xxx.xxx.22)

 

Plus a SIP Trunk Number Range: 0551xxxx100 – 0551xxxx109

Model PSTN numbers: 0207xxxx713 and 0207xxxx714

 

First local CentOS 6.6 FreeSWITCH server (version 1.4.20) has two NICs (eth0: 192.168.2.10 {with public IP address mapped to this IP (xxx.xxx.xxx.67)} ; eth1: 192.168.2.11 (used internally only)}

Second local CentOS 6.6 FreeSWITCH server (version 1.4.20) has two NICs (eth0: 192.168.2.12 {with public IP address mapped to this IP (xxx.xxx.xxx.68)} ; eth1: 192.168.2.13 (used internally only)}

 

They have stated to me that they do not require and registration or authentication. 

 

Unfortunately when I looked at all the samples on the FreeSWITCH Confluence they all seem to mention registering and sip proxy etc….

 

Can someone provide a simple .xml file(s) example for the above (even if it is to only one SBC) to fast-track my setup.  Any other hints or tips (or links to freeswitch.org Docs) I would appreciate.

 

One more thing to note, I am connecting FreeSWITCH via a local Firewall to BT’s SBC’s listed above, there is no SBC on my side since currently it is not needed based on my client’s current requirements.  Hopefully this makes everything a little simpler, however I do understand that this configuration maybe less flexible (especially when commissioning more FreeSWITCH servers).

 

Thanks in advance,

 

Andrew Keil

Visytel Pty Ltd

 

PS. Since I am currently undertaking BT’s testing on behalf of my client in the UK, I will provide back to the FreeSWITCH community the completed  BT Interoperability SIP test cases with the associated FreeSWITCH dialplans used and any comments.  Hopefully this will help any other company to pass BT’s SIP testing requirements in a fast manner J

 


_________________________________________________________________________
Professional FreeSWITCH Consulting Services:
consulting@freeswitch.org
http://www.freeswitchsolutions.com

Official FreeSWITCH Sites
http://www.freeswitch.org
http://confluence.freeswitch.org
http://www.cluecon.com

FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org