thufir
2015-Feb-20 19:29 UTC
[asterisk-users] sipsak 200 for a user, but 404 for a different user...why?
On Fri, 20 Feb 2015 08:46:13 -0500, Andres wrote:> A "sip set debug on" will give you more info on why you are getting the > 404. It probably has to do something with your context/dialplan.on tleilax: tleilax*CLI> tleilax*CLI> sip set debug on SIP Debugging enabled tleilax*CLI> on doge: thufir at doge:~$ thufir at doge:~$ sudo sipsak -vv -s sip:devries at tleilax -m "hi" No SRV record: _sip._tcp.tleilax No SRV record: _sip._udp.tleilax using A record: tleilax Max-Forwards set to 0 message received: SIP/2.0 404 Not Found Via: SIP/2.0/UDP 127.0.1.1:56377;branch=z9hG4bK.0edaada3;alias;received=192.168.1.3;rport=56377 From: sip:sipsak at 127.0.1.1:56377;tag=6b540010 To: sip:devries at tleilax;tag=as02b0fdd6 Call-ID: 1800667152 at 127.0.1.1 CSeq: 1 OPTIONS Server: Asterisk PBX 1.8.32.1-vici Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE Supported: replaces, timer Accept: application/sdp Content-Length: 0 ** reply received after 0.844 ms ** SIP/2.0 404 Not Found final received thufir at doge:~$ However, I'm sure you're right that it's the dialplan; I'm looking into it. thanks, Thufir
Andres
2015-Feb-20 20:07 UTC
[asterisk-users] sipsak 200 for a user, but 404 for a different user...why?
On 2/20/15 2:29 PM, thufir wrote:> On Fri, 20 Feb 2015 08:46:13 -0500, Andres wrote: > > >> A "sip set debug on" will give you more info on why you are getting the >> 404. It probably has to do something with your context/dialplan. > > on tleilax: > > tleilax*CLI> > tleilax*CLI> sip set debug on > SIP Debugging enabled > tleilax*CLI>This is showing nothing so I don't think your test message even made it here. I think it looped in the 'doge' server.> > > on doge: > > thufir at doge:~$ > thufir at doge:~$ sudo sipsak -vv -s sip:devries at tleilax -m "hi" > No SRV record: _sip._tcp.tleilax > No SRV record: _sip._udp.tleilax > using A record: tleilax > Max-Forwards set to 0 > > message received: > SIP/2.0 404 Not Found > Via: SIP/2.0/UDP > 127.0.1.1:56377;branch=z9hG4bK.0edaada3;alias;received=192.168.1.3;rport=56377 > From: sip:sipsak at 127.0.1.1:56377;tag=6b540010 > To: sip:devries at tleilax;tag=as02b0fdd6 > Call-ID: 1800667152 at 127.0.1.1 > CSeq: 1 OPTIONS > Server: Asterisk PBX 1.8.32.1-vici > Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, > PUBLISH, MESSAGE > Supported: replaces, timer > Accept: application/sdp > Content-Length: 0 > > > > ** reply received after 0.844 ms ** > SIP/2.0 404 Not Found > final received > thufir at doge:~$ > > > However, I'm sure you're right that it's the dialplan; I'm looking into > it. > > > thanks, > > Thufir > >-- Technical Support http://www.cellroute.net
thufir
2015-Feb-20 20:20 UTC
[asterisk-users] sipsak 200 for a user, but 404 for a different user...why?
On Fri, 20 Feb 2015 15:07:35 -0500, Andres wrote:> This is showing nothing so I don't think your test message even made it > here. I think it looped in the 'doge' server.I was wondering the same thing :) in tleilax, I looked in /var/log/asterisk/messages and see: [Feb 20 15:13:19] VERBOSE[3661] chan_sip.c: [Feb 20 15:13:19] <--- SIP read from UDP:192.168.1.3:38154 ---> OPTIONS sip:345 at tleilax SIP/2.0 Via: SIP/2.0/UDP 127.0.1.1:38154;branch=z9hG4bK.77fd156e;rport;alias From: sip:sipsak at 127.0.1.1:38154;tag=4653e713 To: sip:345 at tleilax Call-ID: 1179903763 at 127.0.1.1 CSeq: 1 OPTIONS Contact: sip:sipsak at 127.0.1.1:38154 Content-Length: 0 Max-Forwards: 0 User-Agent: sipsak 0.9.6 Accept: text/plain it seems to work, in that I get 200 OK, with success reflected, apparently, in the log, provided that its numerical. I just changed it from "piter" to "345" and get success (well, at this at least). This probably has something to do with my dialplan.. Is the message, "hi", logged anywhere? -Thufir