Debug method of SV9100

[phadobas]

I have a 9100 with the intermittent problem of failed outgoing calls. The user dials 9 + 10-digit phone number and it either works right away, works after about 5 seconds delay, or gives a busy tone after about 30 seconds delay. This thing is using SIP trunks. I have 10 trunks and they are not all busy at the time when the call fails. Incoming calls always work, even if outgoing calls fail sometimes. What's frustrating is I'm not familiar with debug tools, so I don't even really know if it's a system problem, router/firewall problem or ISP or carrier issue. I'm just shooting in the dark when I try to fix it, but nothing worked or even improved so far.

So I see that it has a maintenance/debug screen (in WebPro) where you can turn on some log messages. That's great but where are those messages going???

I've seen also in PC Pro that there is a debug console but i've never been able to make it connect to the phone system.

How do you set those up? Or is there any other tools for debug? Like how do you even see if a trunk is in use or idle, a station is in use or idle, etc?

 

[PFD45]

Not sure if this applies to the 9100 but it's something.

1) Open a new Hyper Terminal session and connect to the SV8100 on port 5963
2) Log into the SV8100 with monimoni and password hihi
3) In hyper Terminal go to Transfer, Capture Text and select the Browse button
4) Browse to the Desktop and provide a name for the file.
5) Click on Save and then Start.
6) Open up a Web Pro connection to the SV8100 and from the” Home” page select Maintenance Debug
7) Turn on CAPS call Control and ISDN.
8) Also enable Wire Shark and then recreate the error.
9) Once the error occurs please identify this one of the following methods……
a. Pressing Enter in the HyperTerminal session multiple times
b. Pressing the Help key 12 times quickly from the phone re-creating the error.
c. Immediately stop the HyperTerminal session as stated in step 10.
10) In Hyper Terminal go to Transfer, Capture Text, Stop.
11) Go back to WebPro and disable the trace options set in step 7.
12) Attach the .txt and WS capture file to the call record. You MUST also provide a detailed description of EXACTLY what the trace contains and which method from step 9 was used to identify the error. You must include all relevant information including caller id received, number dialed, display information, equipment involved (E.g. headset, cordless phone, PGD adapter etc).