Dropped Calls

Status
Not open for further replies.

mobilesoundz

Joined
Oct 24, 2008
Messages
19
Reaction score
0
I am pretty new to this so after a little advise, it appears recently we have been getting dropped calls. We used to get these on the old version after 20 seconds but now it appears the call rings on the handset and before i can answer, it drops i ave looked at the server log but do not know what to try can any one give me suggestions, the log is below:
16:06:22.390 [CM503003]: Call(2): Call to sip:[email protected] has failed; Cause: 487 Request Cancelled; from IP:192.168.0.20:5060
16:06:22.343 [CM503003]: Call(2): Call to sip:[email protected] has failed; Cause: 487 Request Cancelled; from IP:192.168.0.20:5060
16:06:21.937 [CM503008]: Call(2): Call is terminated
16:06:19.640 [CM505001]: Ext.14: Device info: Device Identified: [Man: Siemens;Mod: C475;Rev: General] Capabilities:[reinvite, no-replaces, able-no-sdp, recvonly] UserAgent: [C475 IP/022270000000] PBX contact: [sip:[email protected]:5060]
16:06:19.640 [CM503002]: Call(2): Alerting sip:[email protected]:5060
16:06:19.312 [CM503025]: Call(2): Calling RingAll80:14Ext.1410Ext.1011Ext.1115Ext.15@[Dev:sip:[email protected]:5060]
16:06:19.296 [CM503025]: Call(2): Calling RingAll80:14Ext.1410Ext.1011Ext.1115Ext.15@[Dev:sip:[email protected]:5060]
16:06:19.265 [CM503004]: Call(2): Route 1: RingAll80:14Ext.1410Ext.1011Ext.1115Ext.15@[Dev:sip:[email protected]:5060,Dev:sip:[email protected]:5060]
16:06:19.265 [CM503010]: Making route(s) to <sip:[email protected]:5060>
16:06:19.265 [CM505003]: Provider:[grrr] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [MSSGW] PBX contact: [sip:[email protected]:5060]
16:06:19.250 [CM503001]: Call(2): Incoming call from 0800371104@(Ln.10002@grrr) to <sip:[email protected]:5060>
16:06:19.093 [CM503012]: Inbound office hours rule (unnamed) for 10002 forwards to DN:80
16:00:09.875 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 96.9.132.83:3478 over Transport 192.168.0.1:5060
15:40:09.765 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 96.9.132.83:3478 over Transport 192.168.0.1:5060
15:20:09.625 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 96.9.132.83:3478 over Transport 192.168.0.1:5060
15:00:09.484 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 96.9.132.83:3478 over Transport 192.168.0.1:5060
14:40:09.421 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 96.9.132.83:3478 over Transport 192.168.0.1:5060
14:20:09.296 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 96.9.132.83:3478 over Transport 192.168.0.1:5060
14:00:09.062 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 96.9.132.83:3478 over Transport 192.168.0.1:5060
13:40:09.015 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 96.9.132.83:3478 over Transport 192.168.0.1:5060
13:20:08.875 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 96.9.132.83:3478 over Transport 192.168.0.1:5060
13:00:08.671 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 96.9.132.83:3478 over Transport 192.168.0.1:5060
12:40:08.546 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 96.9.132.83:3478 over Transport 192.168.0.1:5060
12:20:08.406 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 96.9.132.83:3478 over Transport 192.168.0.1:5060
12:00:08.234 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 96.9.132.83:3478 over Transport 192.168.0.1:5060
11:40:08.171 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 96.9.132.83:3478 over Transport 192.168.0.1:5060
11:20:08.062 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 96.9.132.83:3478 over Transport 192.168.0.1:5060
11:00:07.828 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 96.9.132.83:3478 over Transport 192.168.0.1:5060
10:40:07.734 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 96.9.132.83:3478 over Transport 192.168.0.1:5060

Many thanks Mobilesoundz
 
mobilesoundz said:
16:06:22.343 [CM503003]: Call(2): Call to sip:[email protected] has failed; Cause: 487 Request Cancelled; from IP:192.168.0.20:5060
16:06:21.937 [CM503008]: Call(2): Call is terminated

It looks like the set, at IP 192.168.0.20, is causing the call to drop. Have you tried substituting another phone for that extension, to see if it is a hardware or configuration issue with that particular phone?

The ringgroup contains other extensions that don't appear to be registered (the call is not being sent to them in this log). What happens if the other extensions ring at the same time? Do they continue to ring? What if Ext 14 is not registered?
 
Status
Not open for further replies.

Latest Posts

Members Online Now

Forum statistics

Threads
111,861
Messages
589,440
Members
164,701
Latest member
yarusemiKK