TA7108: Packet capture protocols

[handwritten]

We have a couple of TA710X units, and the learning curve is very steep. We're trying to use packet capture to help us get to the bottom of an issue, but there's no documentation on how to send the .pcap to a remote machine. The built-in help states:

Code: [Select]

URL where to send the packet capture. The URL should follow this format:
protocol://[user[:password]@]hostname[:port]/[path/]filename

The brackets [] indicate an optional parameter.

The filename may only be composed of alphanumerical and '-._%$' characters as well as macros. The macros used in this field are replaced by the unit's MAC address or date/time of when the capture was started.

The supported macros are:

%mac% - the MAC address of the unit.
%date% - the date if the capture start in format YYYYMMDD.
%time% - the time if the capture start in format hhmmss.
The supproted transfer protocols are:

HTTP
HTTPS
FILE
Examples of valid URLs:

http://httpserver.com:69/folder/capture.pcap
http://guest@httpserver.com/capture_%mac%_%date%_%time%.pcap
https://username:password@httpserver.com/capture.pcap
file://capture.pcap
The protocol default port is used if none is specified.
This seems odd to me - we're used to using TFTP/FTP for this kind of thing. Has anyone done this successfully? What utility did you use?

[ZuluAlpha]

If you export to file it will be available to download over in the Management > File tab. I only know that because that's how they backup their configs. Doesn't help you send it really but hopefully can get it to a device that can send.

What issue are you having?

[handwritten]

Ahh - I see under Management > Backup and Restore, it seems possible to send any file over TFTP. However, the packet capture does not allow saving a file locally.

The issue we're having is simple - we can't make calls from a SIP endpoint connected to the device. We tried sending debug logs (aka diagnostic traces) via Syslog, but we can't figure out why the calls are failing from those logs.

[handwritten]

Here's a debug output (with sensitive info redacted) from the failed call in question (from DN 929 to 511 using the 'Automatic Call' function).

I will happily buy a beer for anyone who can offer tips! In some places it looks like a 404 error, but the called party exists on the server.

[ZuluAlpha]

In Network > Interfaces in the "Link" Column the drop down has info like eth1, eth1.1, eth1.15 (I'm only using 15 as an example here). If you've added the voice VLAN (say VLAN 15)you also have to adjust this drop down to the eth1.15 to give that interface access to the voice network.

That one got me for a while.

[ZuluAlpha]

Tech Electronics made a guide here:

http://mitelforums.com/forum/index.php/topic,10306.msg46169.html#msg46169

It was how I got mine working.

[handwritten]

Thanks for the tips Zulu! I will look at that config guide. (I'm not using VLANs on this device but it's good to know about the subinterfaces).