Displaying 3 results from an estimated 3 matches for "4653e713".
Did you mean:
4653,13
2015 Feb 20
2
sipsak 200 for a user, but 404 for a different user...why?
...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 n...
2015 Feb 20
0
sipsak 200 for a user, but 404 for a different user...why?
...es 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 re...
2015 Feb 20
2
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