Hi All,
Many thanks for the info, I am now finding the time to look back into
this again.
I have seen this page, which indicates that dahdi_pcap was pushed into
the dahdi driver from version 2.4.0;
On Thu, Dec 5, 2013 at 9:43 AM, James Bensley jwbens...@gmail.com wrote:
If I re-route traffic away from this box (having never installed DAHDI
before) can I simply shutdown Asterisk, checkout the latest SVN,
compile, reload the kernel module and restart Asterisk?
The dahdi project moved from
Hi All,
I am looking for a way to troubleshoot issues with TDM (E1) trunks
with a provider.
Currently with SIP trunks I am using tcpdump to perform packet
captures between our gateways and the SIP providers IPs, capturing
traffic on all ports, to include both the SIP messages and the RTP
stream.
On Thu, Jun 13, 2013 at 9:23 AM, James Bensley jwbens...@gmail.com wrote:
Hi All,
I am looking for a way to troubleshoot issues with TDM (E1) trunks
with a provider.
Currently with SIP trunks I am using tcpdump to perform packet
captures between our gateways and the SIP providers IPs,
Hi!
Depending which TDM board you are using there might already be tool to
get a pcap trace. E.g. if you have a Sangoma board, the wanpipemon
utility has a -pcap option. I don't know about other boards. Wireshark
already comes with basic support for ISDN protocols, so now work is
needed
In article caawx_pvgza965ljxwrna_tkz2hkhqubokngesssje3bkkve...@mail.gmail.com,
James Bensley jwbens...@gmail.com wrote:
Hi All,
I am looking for a way to troubleshoot issues with TDM (E1) trunks
with a provider.
Currently with SIP trunks I am using tcpdump to perform packet
captures
