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 to come up with some way
to get Asterisk to reach the UA through it.
On 08/04/2011 12:59 PM, Baybal Ni wrote:
> 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 behaviour?
>
> --
> _____________________________________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
> New to Asterisk? Join us for a live introductory webinar every Thurs:
> http://www.asterisk.org/hello
>
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
> http://lists.digium.com/mailman/listinfo/asterisk-users
--
Alex Balashov - Principal
Evariste Systems LLC
260 Peachtree Street NW
Suite 2200
Atlanta, GA 30303
Tel: +1-678-954-0670
Fax: +1-404-961-1892
Web: http://www.evaristesys.com/