Child pages
  • Sangoma SBC Interoperability with SipXcom and Skype for Business (Lync)

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Be aware of 7-digit custom dial plans used for PSTN connectivity when working with the Sangoma SBC. The SipXcom custom dialplan will add the 1+area code prefix to the dialed number and insert into the SIP Request-Line header but leaves the TO: header with the original dialed 7-digits. The Sangoma / Freeswitch standard mechanisms for retrieving called numbers (e.g. $1) uses the 7-digit number when placing calls using a custom bridge macro required for REFER processing. This issue is being worked with Sangoma.

There is a variation of this issue that prevents SipXcom from routing an external incoming call to a remote phone when the SBC upper registration feature is used. The request line has a SIP URI with the remote phone's user extension but the TO: SIP header specifies the DID of the called number. The SBC rejects the call (480 unavailable) as it uses the DID in the TO header of the SIP Invite from SipXcom rather the request URI when placing the call to the remote phone. The workaround is to build an SBC call routing rule for the incoming external call (see IncomingITSPtoSBC call routing plan rule 15) that routes the call directly to the remote phone.

...

The network topology was used to test this point-point video application using private WIFI, public WIFI (cable), and LTE access from an Android client running Counterpath Bria to a Windows lab laptop running Bria. The video quality with private and public WIFI was excellent in almost all testing - LTE access (WIFI was turned off on the Android smartphone) delivered good quality video 80 percent of the time. 

Image Removed

 Image Added