Version 4.2

At this time we have found the YATE client 4.2.0-2 to not work well enough with OnSIP that we can recommend it as a product.

The issue is that the phone indicates that it can support G.711 ULAW and G.711 ALAW but when a call connects using ULAW, the phone will not transmit or decode audio.

We tested this using the latest YATE client and calling welcome@junctionnetworks.com. Our system will default to G.711 ULAW when it can, however when called by the YATE client, we experienced dead air.

We have contacted YATE to notify them of this development.

Here is the list of codecs supported directly from a YATE invite header.

v=0
o=yate 1356034544 1356034544 IN IP4 38.104.167.182
s=SIP Call
c=IN IP4 38.104.167.182
t=0 0
m=audio 21734 RTP/AVP 0 8 11 98 97 102 103 104 105 106 101
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:11 L16/8000
a=rtpmap:98 iLBC/8000
a=fmtp:98 mode=20
a=rtpmap:97 iLBC/8000
a=fmtp:97 mode=30
a=rtpmap:102 SPEEX/8000
a=rtpmap:103 SPEEX/16000
a=rtpmap:104 SPEEX/32000
a=rtpmap:105 iSAC/16000
a=rtpmap:106 iSAC/32000
a=rtpmap:101 telephone-event/8000
a=ptime:30

Version 3.1

Unfortunately at this time the standalone Yate client is not fully compatible with our service. To register a client with OnSIP, we ask that the Authorization Username be independently configurable.

The Yate client supplants the authorization user name with the AOR username. This means that only users who have the same authentication and AOR usernames will register with OnSIP. The inability to configure an authentication username is extremely limiting and is effectively incompatible with OnSIP.

Here is a trace of the registration attempt (the problem is bolded):

U 2011/02/03 10:08:43.001907 173.210.1.18:1515 -> 66.227.100.25:5060
REGISTER sip:example.onsip.com SIP/2.0.
Contact: <sip:hiro@173.210.1.18:1515>.
Expires: 600.
To: <sip:hiro@example.onsip.com>.
Call-ID: 987987334@example.onsip.com.
Via: SIP/2.0/UDP 173.210.1.18:1515;rport;branch=z9hG4bK108375482.
From: <sip:hiro@example.onsip.com>;tag=202550399.
CSeq: 11 REGISTER.
User-Agent: YATE/3.1.0.
Max-Forwards: 70.
Allow: ACK, INVITE, BYE, CANCEL, OPTIONS, INFO.
Content-Length: 0.
.

U 2011/02/03 10:08:43.002251 66.227.100.25:5060 -> 173.210.1.18:1515
SIP/2.0 401 Unauthorized.
To: <sip:hiro@example.onsip.com>;tag=75d09fb22ceadb40012c6e771a69dc74.fd4b.
Call-ID: 987987334@example.onsip.com.
Via: SIP/2.0/UDP 173.210.1.18:1515;received=173.210.1.18;rport=1515;branch=z9hG4bK108375482.
From: <sip:hiro@example.onsip.com>;tag=202550399.
CSeq: 11 REGISTER.
WWW-Authenticate: Digest realm="jnctn.net",
nonce="4d4ac51900011b24cd56468e9ce54a9b95cbb9e90aa18873", qop="auth".
Server: OpenSIPS (1.5.3-notls (x86_64/linux)).
Content-Length: 0.
.

U 2011/02/03 10:08:43.009277 173.210.1.18:1515 -> 66.227.100.25:5060
REGISTER sip:example.onsip.com SIP/2.0.
Contact: <sip:hiro@173.210.1.18:1515>.
Expires: 600.
To: <sip:hiro@example.onsip.com>.
Call-ID: 987987334@example.onsip.com.
Via: SIP/2.0/UDP 173.210.1.18:1515;rport;branch=z9hG4bK1738076217.
From: <sip:hiro@example.onsip.com>;tag=202550399.
User-Agent: YATE/3.1.0.
Max-Forwards: 70.
Allow: ACK, INVITE, BYE, CANCEL, OPTIONS, INFO.
CSeq: 12 REGISTER.
Authorization: Digest username="hiro", realm="jnctn.net",
nonce="4d4ac51900011b24cd56468e9ce54a9b95cbb9e90aa18873", uri="sip:example.onsip.com",
response="a36923be1b1a6eee2a65416a87a3744e", algorithm=MD5.
Content-Length: 0.
.

U 2011/02/03 10:08:43.010083 66.227.100.25:5060 -> 173.210.1.18:1515
SIP/2.0 403 Forbidden.
To: <sip:hiro@example.onsip.com>;tag=75d09fb22ceadb40012c6e771a69dc74.bb9c.
Call-ID: 987987334@example.onsip.com.
Via: SIP/2.0/UDP 173.210.1.18:1515;received=173.210.1.18;rport=1515;branch=z9hG4bK1738076217.
From: <sip:hiro@example.onsip.com>;tag=202550399.
CSeq: 12 REGISTER.
Server: OpenSIPS (1.5.3-notls (x86_64/linux)).
Content-Length: 0.

---

 

See our top business VoIP phone recommendations for 2017