getting the right status from pjsua_acc_add

YT
Yosi Taguri
Fri, Mar 14, 2014 4:27 PM

Hi,
I noticed that when I try to use a URI with a port that the server doesn't
support I get an error similar to this:

00:20:06.651    pjsua_acc.c  .Account sip:XXXXXX@YYYYYYYY:ZZZZZ;transport=tls
added with id 0

00:20:06.651    pjsua_acc.c  .Acc 0: setting registration..

00:20:06.651    pjsua_acc.c  ..Unable to generate suitable Contact header
for registration: Unsupported transport (PJSIP_EUNSUPTRANSPORT)
[status=171060]

00:20:06.652    pjsua_acc.c  ..Unable to create registration: Unsupported
transport (PJSIP_EUNSUPTRANSPORT) [status=171060]

and pjsua_acc_add would still return PJ_SUCCESS.

I created a patch to return the right status from pjsua_acc_add. it is
attached.

--

Yosi Taguri | Founder & CTO | Yalo | http://yaloapp.com
http://ahhhpah.com| Mobile: +972-54-4816020 | Google Voice US
Mobile: +1 (415) 935-1126 |
Email: yosi@taguri.com

Hi, I noticed that when I try to use a URI with a port that the server doesn't support I get an error similar to this: 00:20:06.651 pjsua_acc.c .Account sip:XXXXXX@YYYYYYYY:ZZZZZ;transport=tls added with id 0 00:20:06.651 pjsua_acc.c .Acc 0: setting registration.. 00:20:06.651 pjsua_acc.c ..Unable to generate suitable Contact header for registration: Unsupported transport (PJSIP_EUNSUPTRANSPORT) [status=171060] 00:20:06.652 pjsua_acc.c ..Unable to create registration: Unsupported transport (PJSIP_EUNSUPTRANSPORT) [status=171060] and pjsua_acc_add would still return PJ_SUCCESS. I created a patch to return the right status from pjsua_acc_add. it is attached. -- Yosi Taguri | Founder & CTO | Yalo | http://yaloapp.com <http://ahhhpah.com>| Mobile: +972-54-4816020 | Google Voice US Mobile: +1 (415) 935-1126 | Email: yosi@taguri.com