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 Fri, Feb 17, 2017 at 4:56 PM, Tim
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 tur
.conf the mailbox line shows the common mailbox number (ie "1015")
with the optional context:
[...]
[1015]
type=friend
username=1015
callerid = Tim Pozar <1015>
secret=HACKME
host=dynamic
nat=yes
context=default
canreinvite=no
mailbox=1015
[1078]
type=friend
username=1078
secret=HA
vent)
12 headers, 12 lines
Reliably Transmitting:
INVITE sip:[EMAIL PROTECTED] SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5060;branch=z9hG4bK757f3e87
From: "Tim Pozar" ;tag=as1bd4c20b
To:
Contact:
Call-ID: [EMAIL PROTECTED]
CSeq: 102 INVITE
User-Agent: Asterisk
Date: Thu, 10 Nov 2005 23:44:09 G
Greg Oliver wrote:
Hm, I would have to disagree.
We use MGCP dial-peers and use it on PRIs with 3725s and 2851s
currently.
Our config was fubar'ed. We were using dial-peer "isdn" instead of
"pots". "direct-inward-dial" does not work with "isdn". We were
succussful with something like:
Greg Oliver wrote:
Add direct-inward-dial to your dial peer and it should work fine.
That command is only supported for POTS interfaces. :-( Not PRIs (aka
ISDN in cisco parlance).
Tim
--
1978 45th Ave / San Francisco CA 94116 / USA // POTS: +1 415 665 3790
GPG Fingerprint: 4821 CFDA 06E7 4
I would think I could do this but for some reason I am stymied.
I have a PRI from RCN connected to a cisco 3640 (in my day "cisco" is
all lower case :-)). My config looks something like this on the cisco...
-
voice-card 3
dsp services ds
