List Info

Thread: Re: ReceiveCall always failed withREGISTER_FAILED_NOT_AUTHORIZED




Re: ReceiveCall always failed withREGISTER_FAILED_NOT_AUTHORIZED
country flaguser name
Czech Republic
2007-03-23 09:17:38
>yes, with realm = etc.tario.ru all works fine in
ReceiveCall, but X-Lite works and with realm = sipnet.ru
(this name recomended by >service provider).
>
>how X-Lite understands, what realm instead of sipnet.ru
it is necessary to use etc.tario.ru?
>
>from x-lite log:
>[07-03-23]10:17:00.350 | Debug | RESIPUM |
"Adding credential: realm=sipnet.ru user=xpg934" |


x-lite uses realm=etc.tario.ru internally too, just look
further in the log and you will see the response to 401. Or
use ethereal to capture traffic to sip proxy, it will be
stripped of the x-lite junk. It just autodetects
etc.tario.ru from 401 response. Sipxtapi (sipxtacklib)
doesn't do it, you have to provide proper realm.

Jaroslav Libak
_______________________________________________
sipxtapi-dev mailing list
sipxtapi-devlist.sipfoundry.org
List Archive: http
://list.sipfoundry.org/archive/sipxtapi-dev/

Re: ReceiveCall always failedwithREGISTER_FAILED_NOT_AUTHORIZED
country flaguser name
Russian Federation
2007-03-23 09:28:31
> x-lite uses realm=etc.tario.ru internally too, just
look further in the log and you will see the response to
401. Or use ethereal to capture traffic to sip proxy, it
will be stripped of the x-lite junk. It just autodetects
etc.tario.ru from 401 response. Sipxtapi (sipxtacklib)
doesn't do it, you have to provide proper realm.

Thank you.

There is an opportunity to process incoming SIP-messages
manually? Can be any hook?

_______________________________________________
sipxtapi-dev mailing list
sipxtapi-devlist.sipfoundry.org
List Archive: http
://list.sipfoundry.org/archive/sipxtapi-dev/

[1-2]

about | contact  Other archives ( Real Estate discussion Medical topics )