Troubleshooting C20

[Kelvin Machakaire]

Suddenly my standalone C20 won't place calls displaying the "Cannot connect call" message each time. Network seamingly unchanged. Now trying to figure out the cause.

How do I dump logs to see why the call won't go through? From web browser I went to Diagnostics>Log Files and there is a huge bunch of logs now I'm not sure which one will help. The codec sits on the internet with a public IP.

TC5.1.4

Please assist

[amehla]

hi Kevin,

please make sure, call setup is set to direct.

in case NAT is not used, please make it off.

[Danny De Ridder]

What kind of signalling do you use? SIP or H323?

I would first start to check the status of your signalling protocol in use.

http://10.60.142.199/getxml?location=/Status/Sip

http://10.60.142.199/getxml?location=/Status/h323

Ans get the call history :

http://10.60.142.199/getxml?location=/history

Replace IP addresses above with your codec's address.

To see why call is failing.

You can enable debug when loggin in to the C20 using ssh with user admin.

The current logs can also probably reveal already something.

Danny.

[Kelvin Machakaire]

Thank Danny and Amit!

From call history I picked that the call was failing because of an "Invalid NAT Address". So I just changed the NAT mode to "Off" and the call went through without a problem.

Now wondering why this suddenly happened now when calls have always been going through even when the NAT mode was set to "Auto".

[Ravi Yadav]

Hi Kevin,

Here is what happens if NATTING is DONE,

Auto: The system will determine if the "NAT Address" or the real IP-address should be used

within signalling. This is done to make it possible to place calls to endpoints on the LAN as well as

endpoints on the WAN.

On: The system will signal the configured "NAT Address" in place of its own IP-address within

Q.931 and H.245. The NAT Server Address will be shown in the startup-menu as: "My IP Address:

10.0.2.1".

Off: The system will signal the real IP Address.

now what type of call was that internal netwrok or going external

if Internal call then it will connect fine, however the external call will not connect.

on auto mode it will be fine for both internal and external.

Thanks

Ravi kr.

[Kelvin Machakaire]

Once again the same system won't place calls. When I dial, it continuously displays the "Connecting call" message and then drops the attempt after approximately 2mins. This time I have captured the logs and they are given below.

7

H323

Outgoing

Unknown

h323:41.87.236.22

h323:41.87.236.22

768

12

Unreachable destination

NetworkRejected

18

Q850

2013/04/04 14:42:10

0

Aes-128

From the logs its showing " Unreachable destination" but I'm sure network connectivity to that destination is ok. I just tested using Jabber for Telepresence sitting in the same subnet and the call nicely went through to that same destination. No changes have been made on the codec.

What could be the cause?