|
apr10Written by:morten.rokosz
Thu, 10 Apr 2008 07:55:17 GMT  If you are a frequent reader of the forum, you have noticed that from time to time there will be posts about SIP Trunking. We often then ask the poster if the provider is tested by Swyx. This is not just something we say because we can't help... If you are a frequent reader of the forum, you have noticed that from time to time there will be posts about SIP Trunking. We often then ask the poster if the provider is tested by Swyx. This is not just something we say because we can't help... When Swyx, and also partners like us, test SwyxWare and SIP providers we do more than just see if we can dial in and out.  As the picture shows you, there is really a couple of test sheets that we follow. This is important to make sure that the provider works together with SwyxWare. We test all the different kinds of phones, SwyxIt!, SwyxPhone, SIP Phone and the DECT system.
But also important is to test if DTMF is handled in the correct way, so that ECR scripts will work. If the provider supports T.38 we also do tests using SwyxFaxServer. All important data about the test is also written down. The version of each SwyxWare component and the version of the provider softswitch. The reason for all the papers on my desk, is that we are about to start the test for a new SIP provider. Tags: 3 comment(s) so far...
Re: That is so SIP Morten, you are so right, i have tested several SIP providers, and most of them fail on DTMF, and DDI :o) By tla on
Thu, 10 Apr 2008 08:38:00 GMT
|
Re: That is so SIP BTW: the Swyx SIP provider testplan will be available from tpp (at) swyx (dot) com . By tom.wellige on
Thu, 10 Apr 2008 16:06:34 GMT
|
Re: That is so SIP That's the problem with SIP. It does not originate from telephony. Missing things like DTMF, DDI, early media streaming, etc. had been added, of course, thanks to SIP's very easy extensibility, but this flexibility costs interoperability. Often there's more than one way to do things, some features are optional form the standard's point of view, but mandatory to provide a good telephony experience.
When we started Swyx and even before that we mainly did H.323. I remember colleagues traveling to big interoperability events where various vendors tried to connect their products via H.323 to check compatibility. Standards help to agree to a least common denominator. But nothing more. By Martin on
Fri, 11 Apr 2008 10:25:22 GMT
|
|
|