Compatibilitie between SIP V1.3.0.23 and SIP V2 Sofia Stack
Hi All Due to time constraints I'm posting here for the hope for a quick response. I'm currently trying to setup a Trunk to our upstream Carrier. The issues we are facing is that inbound calls from them are working 100%. Outbound calls to them are returned with a 500 error. The only immediate differences we could pickup was the SIP versions. They have a Huawei MSOFTX3000 running SIP version 1.3.0.23. I'm running freeSWITCH 1.5.1b+git~20130414T025052Z~969eae39d9 Is there any possibility someone could help me figure out what compatibility issues between the SIP versions could cause, especially for out bound calls to the Carrier? Thank you very much Kind Regards Deon Vermeulen
1.3.0.23 is their software version, not the SIP protocol version. Both will be using SIP v2. Some different devices do have different interpretations of that standard though, which can lead to interop problems between different device types. I suggest you contact your carrier to ask why they're sending 500 - they may be able to advise you what is causing this error. -Steve On 3 May 2013 09:54, Deon Vermeulen <vermeulen.deon@gmail.com> wrote:
Hi All
Due to time constraints I'm posting here for the hope for a quick response.
I'm currently trying to setup a Trunk to our upstream Carrier. The issues we are facing is that inbound calls from them are working 100%. Outbound calls to them are returned with a 500 error.
The only immediate differences we could pickup was the SIP versions.
They have a Huawei MSOFTX3000 running SIP version 1.3.0.23. I'm running freeSWITCH 1.5.1b+git~20130414T025052Z~969eae39d9
Is there any possibility someone could help me figure out what compatibility issues between the SIP versions could cause, especially for out bound calls to the Carrier?
Thank you very much
Kind Regards Deon Vermeulen
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.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
Spotted this on the sofia configuration page: http://wiki.freeswitch.org/wiki/Sofia_Configuration_Files#session-timeout Note: If your switch requires the timer option; for instance, Huawei
SoftX3000, it needs this optional field and drops the calls with "Session Timer Check Message Failed", then you may be able to revert back the commit that took away the Require: timer option which is an optional field by:
Perhaps this is the issue? According to the wiki that issue requires a patch to the FreeSWITCH source, check the wiki link above. -Steve On 3 May 2013 10:13, Steven Ayre <steveayre@gmail.com> wrote:
1.3.0.23 is their software version, not the SIP protocol version. Both will be using SIP v2.
Some different devices do have different interpretations of that standard though, which can lead to interop problems between different device types.
I suggest you contact your carrier to ask why they're sending 500 - they may be able to advise you what is causing this error.
-Steve
On 3 May 2013 09:54, Deon Vermeulen <vermeulen.deon@gmail.com> wrote:
Hi All
Due to time constraints I'm posting here for the hope for a quick response.
I'm currently trying to setup a Trunk to our upstream Carrier. The issues we are facing is that inbound calls from them are working 100%. Outbound calls to them are returned with a 500 error.
The only immediate differences we could pickup was the SIP versions.
They have a Huawei MSOFTX3000 running SIP version 1.3.0.23. I'm running freeSWITCH 1.5.1b+git~20130414T025052Z~969eae39d9
Is there any possibility someone could help me figure out what compatibility issues between the SIP versions could cause, especially for out bound calls to the Carrier?
Thank you very much
Kind Regards Deon Vermeulen
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.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
Hi Steven I just want to give an update. The problem is resolved without having to do any patches or funny configurations. Some Technician other then the 2 I was working with sent me the error info and I immediately figured what it was. **0.105506817 SE2300-SBC0 SIP/8/debug:<Error:***>Sip get intercom signal query address by ip[192.168.0.250-->10.222.0.200] route failed.* The problems was that I was listening on port 6090 and they on 5060. With the invite I send them the return port was not allowed on their SBC. I changed my port to 5060 and calls started flowing. I guess the timer issue could have been resolved in the latest version? Thanks again for helping. Kind Regards Deon
Steven Ayre <mailto:steveayre@gmail.com> May 3, 2013 10:16 AM Spotted this on the sofia configuration page: http://wiki.freeswitch.org/wiki/Sofia_Configuration_Files#session-timeout
Perhaps this is the issue? According to the wiki that issue requires a patch to the FreeSWITCH source, check the wiki link above.
-Steve
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.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 Steven Ayre <mailto:steveayre@gmail.com> May 3, 2013 10:13 AM 1.3.0.23 is their software version, not the SIP protocol version. Both will be using SIP v2.
Some different devices do have different interpretations of that standard though, which can lead to interop problems between different device types.
I suggest you contact your carrier to ask why they're sending 500 - they may be able to advise you what is causing this error.
-Steve
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.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 Deon Vermeulen <mailto:vermeulen.deon@gmail.com> May 3, 2013 9:54 AM Hi All
Due to time constraints I'm posting here for the hope for a quick response.
I'm currently trying to setup a Trunk to our upstream Carrier. The issues we are facing is that inbound calls from them are working 100%. Outbound calls to them are returned with a 500 error.
The only immediate differences we could pickup was the SIP versions.
They have a Huawei MSOFTX3000 running SIP version 1.3.0.23. I'm running freeSWITCH 1.5.1b+git~20130414T025052Z~969eae39d9
Is there any possibility someone could help me figure out what compatibility issues between the SIP versions could cause, especially for out bound calls to the Carrier?
Thank you very much
Kind Regards Deon Vermeulen
participants (2)
-
Deon Vermeulen
-
Steven Ayre