Problem:4128:Extensions Calling Themselves?

Status
Not open for further replies.

darrellchapman

Joined
Nov 26, 2007
Messages
268
Reaction score
0
Has anyone ever seen this? Every once in a while an extension will call itself. Their phone will literally ring, but nothing on the other end. I verified that the extension is calling itself from the server status (below). I don't think the Deskphones or VoIP Client is at fault here since their status shows "not connected - ready" and they can send/receive calls just fine. There's something in the server that's causing this. See pictures below:

ServerStatus.png

VoIPClientStatus.png


Here's the server logs of one of those instances:
Code:
14:17:21.804 Call::Terminate [CM503008]: Call(95): Call is terminated
14:17:21.757 Call::Terminate [CM503008]: Call(95): Call is terminated
14:17:05.225 CallCtrl::onLegConnected [CM503007]: Call(95): Device joined: sip:[email protected]:5070;rinstance=290e5d4b790dda20
14:17:04.929 CallCtrl::onLegConnected [CM503007]: Call(95): Device joined: sip:
14:17:04.913 CallCtrl::onRerouteReq [CM503005]: Call(95): Forwarding: IVR:RecordMessage@[Dev]
14:16:54.928 Extension::printEndpointInfo [CM505001]: Ext.201: Device info: Device Identified: [Man: GrandStream;Mod: GXP-2000;Rev: General] Capabilities:[reinvite, no-replaces, unable-no-sdp, recvonly] UserAgent: [Grandstream GXP2000 1.1.5.15] Transport: [sip:192.168.180.25:5060]
14:16:54.928 CallCtrl::onAnsweredCall [CM503002]: Call(95): Alerting sip:[email protected]:5060;transport=udp
14:16:54.756 CallCtrl::onSelectRouteReq [CM503004]: Call(95): Calling: Ext:201@[Dev:sip:[email protected]:5060;transport=udp]
14:16:54.756 CallCtrl::onSelectRouteReq [CM503010]: Making route(s) to [sip:[email protected]:5060]
14:16:54.756 Extension::printEndpointInfo [CM505001]: Ext.203: Device info: Device Identified: [Man: 3CX Ltd.;Mod: 3CX VoIP Client;Rev: 1] Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CX Phone v0.1] Transport: [sip:192.168.180.25:5060]
14:16:54.741 CallCtrl::onIncomingCall [CM503001]: Call(95): Incoming call from Ext.203 to [sip:[email protected]:5060]
 
It appears as though this problem has been corrected with the new VoIP Client (build 4316).
 
That is a strange problem - well im glad its fixed in for you now.
 
Darrell,
I experienced something somewhat similar to what you're describing, let me describe:
From time to time, one of my extensions, or occasionally a line is not properly refreshed on the status page although the extension or the line is in "normal" operational condition. The extension or line shows in yellow. Subsequently when I use it, it continues to behave in a bizarre way, including per the description that you gave.
In your case, do you know what triggers this behavior; is it totally out of the blue moon, or as a result of some dialing action?
How does it go away? Do you need to reset 3CX? Disconnect the line and reconnect?
Halea
 
The only common denominator about my issue was that it only did it on users running the 3CX VoIP Client in headset mode. I didn't determine this fact until after I had posted this problem (otherwise I would have posted to the VoIP Client forum). Upgrading to the latest VoIP Client (build 4316) and latest 3CX server services (build 4287) seemed to have solved the problem.

Are your clients running the 3CX VoIP Client too?
 
In my case it's with hard phones. Since my extensions and lines continue to run just fine when this happens, and I have to say it's not frequent, I don't worry too much. I guess these problems are distinct from each other.
Halea
 
Are you running windows 2k3? Im using XP and have never seen this problem occur.

Also have you though about add a autorestart to the computer at night when the system's not being used?
 
Status
Not open for further replies.

Latest Posts

Forum statistics

Threads
111,893
Messages
589,598
Members
164,763
Latest member
Techmansam