Thanks for pointing me in the right direction. I didn't have an "s" extension defined in my default context, so asterisk was returning a 404 error because OpenSIPs doesn't specify an extension in the OPTIONS packet. The "s" is apparently where asterisk dumps anything to a context which doesn't have it's extension properly specified.
OPTIONS sip:asterisk1.mydomain.com:5060 SIP/2.0 Via: SIP/2.0/UDP 10.2.252.191;branch=z9hG4bKa588.184b8a54.0 To: sip:asterisk1.mydomain.com:5060 From: sip:[email protected];tag=df32303fa6e909646461ac9cb721a4cc-1dab CSeq: 10 OPTIONS Call-ID: [email protected] Content-Length: 0 User-Agent: OpenSIPS (1.4.2-notls (x86_64/linux)) Thanks for the assistance! Geoff On Sun, Feb 1, 2009 at 5:38 PM, Alex Balashov <[email protected]> wrote: > Iñaki Baz Castillo wrote: > >> El Domingo, 1 de Febrero de 2009, Alex Balashov escribió: >> >>>> Asterisk only replies 200 for an OPTIONS in case a INVITE with same RURI >>>> would be allowed in that context and for that user. >>>> >>>> This is: if you send an OPTIONS with a RURI that would get a 404 in case >>>> of being an INVITE then you will get also a 404 when using the same RURI >>>> in an OPTIONS. >>> Ah, OK. So he needs to add a valid peer. >> >> And a valid extension in that peer context :) > > Ah, si, tiene mucha razon. > > > -- > Alex Balashov > Evariste Systems > Web : http://www.evaristesys.com/ > Tel : (+1) (678) 954-0670 > Direct : (+1) (678) 954-0671 > Mobile : (+1) (678) 237-1775 > > _______________________________________________ > Users mailing list > [email protected] > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > _______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
