Trunk display and SIP trace

Pascal,

I also want to thank you for all the great work you put into this idea, which you made a reality.

Here are two suggestions, which I believe will make it easier to work and troubleshoot the system.

At the status page in the trunk section, an indicator can be added to show the trunk is being used. The indicator can point to the left towards the extensions for incoming calls, and to the right away from the extensions for outgoing calls.

This will allow us to have visual feedback similar to the extensions' display which has a ringing, or off-hook phone during their use.

Something else which I wish I had access to, is a display similar to a packet log. Not necessarily a full packet log with every single packet, but at least the SIP messages which are axchanged between the trunks and their SIP proxies.

This would allow us to troubleshoot the connection between our trunks and the remote SIP proxies, and possibly gather enough information to track down the source of problems. Currently our only recourse is to setup the trunk on an ATA and use a packet sniffer, which does not give us information on the interaction between the trunk and the pbx.

Thanks.

RE: Trunk display and SIP trace

The trunk display works as requested if the trunk name is identical to the SIP server.

Pascal,

if I have account 55555 @ Fwd.pulver.com as a trunk,
does this mean the trunk name the same as the server name, such as fwd.pulver.com , or the same as the registraiopn to that server 55555?

RE: Trunk display and SIP trace

Thanks for the example. In this case the trunk name would be fwd.pulver.com.