Perfect, exactly what I needed. Thanks.
On Mon, Feb 27, 2017 at 6:32 AM, Igor Zamocky wrote:
> Hi,
>
> If you are ok with starting debug via external system call, why not to use
> something like this (I used to use something similar, it worked):
>
> exten =>*
Hi,
If you are ok with starting debug via external system call, why not to use
something like this (I used to use something similar, it worked):
exten => _XXX,1,System(/usr/sbin/asterisk -rx ‘sip set debug peer PEER’)
same => n,Set(debug_on=1)
same => n,Dial(SIP/PEER/${EXTEN})
exten =>
While we're at it, check out sngrep. Alex B. mentioned it on another
mailing list a couple days ago.
Screenshots: https://github.com/irontec/sngrep/wiki/Screenshots
Download: https://github.com/irontec/sngrep
Am 18.02.2017 um 05:10 schrieb Markus Weiler:
Hi Derek,
I think Homer
Hi Derek,
I think Homer (http://sipcapture.org/) is the right answer :-)
HEP Agent will send the SIP trace to a remote Server (res_hep).
Markus
Am 18.02.2017 um 00:18 schrieb Tim Pozar:
You can tell it to just capture SIP traffic and not the RTP traffic.
Nice write up of using TCPdump and
On Fri, 17 Feb 2017, Derek Andrew wrote:
I have some troublesome numbers that I would like to capture the SIP
dialogue when I am calling them. When I am about to dial the number, is
there any way to turn on SIP debugging in the dial plan before I make
the call? (and turn it off after the call
Yes, I agree. Tcpdump is one of my favourite programs. I need to enable it
and disable it from the dialplan though.
On Fri, Feb 17, 2017 at 5:18 PM, Tim Pozar wrote:
> You can tell it to just capture SIP traffic and not the RTP traffic.
> Nice write up of using TCPdump and
But how do you turn on the debugging from the dialplan? What would be cool
is:
same => n,TURN ON DEBUGGING
On Fri, Feb 17, 2017 at 5:09 PM, Victor Villarreal
wrote:
> Hi Derek,
>
> SIP debug can be enabled via Asterisk CLI (console) with the command:
>
> asterisk> sip
Hi
I don't know if works, but you can try this:
System(tcpdump -nq -s 0 -i eth0 -w /tmp/sip.pcap port 5060
or udp portrange 1-2 &);
Wait(1);
Dial(SIP/${EXTEN});
System(pkill tcpdump);
Hangup;
Or whitout RTP:
You can tell it to just capture SIP traffic and not the RTP traffic.
Nice write up of using TCPdump and wireshark can be found here:
https://blog.flowroute.com/2014/04/10/how-to-capture-sip-packets/
BTW, I have found this works really well in trying to debug RTP traffic
as well. Wireshark just
Hi Derek,
SIP debug can be enabled via Asterisk CLI (console) with the command:
asterisk> sip set debug on
If you know via what trunk your call goes, you can use the following
command instead:
asterisk> sip set debug ip xxx.xxx.xxx.xxx
Where the xxx is the IP of your trunk (voip to pstn
The SIP trace will be adequate but this is on a remote system with limited
disk space.
I would love to turn on debugging while making the troublesome calls, then
turn it off afterward.
Tcpdump is great, but starting it and stopping it and keeping all that data
would still be an issue.
d
On
Why not capture the packets with something like tcpdump and run it
through Wireshark?
Tim
On 2/17/17 2:43 PM, Derek Andrew wrote:
> I have some troublesome numbers that I would like to capture the SIP
> dialogue when I am calling them. When I am about to dial the number, is
> there any way to
I have some troublesome numbers that I would like to capture the SIP
dialogue when I am calling them. When I am about to dial the number, is
there any way to turn on SIP debugging in the dial plan before I make the
call? (and turn it off after the call is completed?)
--
13 matches
Mail list logo