On 08/04/2011 01:45 PM, Baybal Ni wrote:
I see 401, but asterisk has my proxy in its trunk list. Can this be
caused by anything else?
Some sort of failure to match the proxy to the sip.conf peer.
Is there any way to do it without using path extension?
We do it by having the proxy rewrite
Hello,
I have a following setup: UA opensips REGISTER asterisk
userdb, where opensips forwards register requests.
For some reasons Asterisk 1.6.2.18 doesn't want to accept REGISTER
forwarded through opensips.
Here is SIP trace http://pastebin.com/ebV62r7b .
What can possibly cause this
It doesn't consider the OpenSIPS host an authorised peer, so it's simply
issuing the usual 401 challenge.
Also, Asterisk doesn't currently support the Path extension, and you
can't use Record-Route in REGISTERs. If you want your proxy to stay in
the loop of subsequent traffic, you will need
I see 401, but asterisk has my proxy in its trunk list. Can this be
caused by anything else?
Is there any way to do it without using path extension?
On 4 August 2011 10:19, Alex Balashov abalas...@evaristesys.com wrote:
It doesn't consider the OpenSIPS host an authorised peer, so it's simply
