asterisk users - Feb 2015 - 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

On 2/20/15 3:20 PM, thufir wrote:
> 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?
I don't think so.  But you should also see the SIP messages on the 
console (sip set debug on) without having to look at the log file. Maybe 
something in your logger.conf is messed up.
>
>
>
> -Thufir
>
>

-- 
Technical Support
http://www.cellroute.net

On Fri, 20 Feb 2015 17:11:53 -0500, Andres wrote:
> I don't think so.  But you should also see the SIP messages on the
> console (sip set debug on) without having to look at the log file. Maybe
> something in your logger.conf is messed up.

that worked :)

tleilax*CLI> 
tleilax*CLI> 
[Feb 20 21:06:19] 
<--- SIP read from UDP:192.168.1.3:44226 --->
OPTIONS sip:345 at tleilax SIP/2.0
Via: SIP/2.0/UDP 127.0.1.1:44226;branch=z9hG4bK.508a6d72;rport;alias
From: sip:sipsak at 127.0.1.1:44226;tag=2a099edc
To: sip:345 at tleilax
Call-ID: 705273564 at 127.0.1.1
CSeq: 1 OPTIONS
Contact: sip:sipsak at 127.0.1.1:44226
Content-Length: 0
Max-Forwards: 0
User-Agent: sipsak 0.9.6
Accept: text/plain

<------------->
[Feb 20 21:06:19] --- (11 headers 0 lines) ---
[Feb 20 21:06:19] Looking for 345 in trunkinbound (domain tleilax)
[Feb 20 21:06:19] 
<--- Transmitting (NAT) to 192.168.1.3:44226 --->
SIP/2.0 200 OK
Via: SIP/2.0/UDP 
127.0.1.1:44226;branch=z9hG4bK.508a6d72;alias;received=192.168.1.3;rport=44226
From: sip:sipsak at 127.0.1.1:44226;tag=2a099edc
To: sip:345 at tleilax;tag=as5d21da5c
Call-ID: 705273564 at 127.0.1.1
CSeq: 1 OPTIONS
Server: Asterisk PBX 1.8.29.0-vici
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, 
PUBLISH, MESSAGE
Supported: replaces, timer
Contact: <sip:192.168.1.2:5060>
Accept: application/sdp
Content-Length: 0


<------------>
[Feb 20 21:06:19] Scheduling destruction of SIP dialog 
'705273564 at 127.0.1.1' in 32000 ms (Method: OPTIONS)
[Feb 20 21:06:38] Really destroying SIP dialog '1876256264 at 127.0.1.1'
Method: OPTIONS
[Feb 20 21:06:51] Really destroying SIP dialog '705273564 at 127.0.1.1' 
Method: OPTIONS
tleilax*CLI> exit
tleilax:~ # 



I would've liked to see the "hi" message, but it's good to see
that
result server side.





-Thufir