Calls going stright to voice mail

[yerfdog]

Hi All.

After getting my 7965 to register on 3CX i have a new problem.

I can call out from the 7965 fine. If someone was to call me internally it goes stright to voice mail. I have turned of the voice mail for the users but it always go to voice mail.

Everything is setup the same as the 7941 and 7940 ectension and there is no problem on them.. Only on the 7965's

My voice mail box is set to 666.

I was trying to call from 107 ----- 101

Please could someone take a look at the logs.

Any help would be great.

Thanks

Mike

INVITE sip:[email protected];user=phone SIP/2.0
Via: SIP/2.0/UDP 192.168.0.28:5060;branch=z9hG4bK431199d5
Max-Forwards: 70
Contact: <sip:[email protected]:5060;transport=udp>
To: <sip:[email protected];user=phone>
From: "107"<sip:[email protected]>;tag=0016c8fd658e000c9d6c72ab-abd812a0
Call-ID: [email protected]
CSeq: 102 INVITE
Expires: 180
Accept: application/sdp
Allow: ACK, BYE, CANCEL, INVITE, NOTIFY, OPTIONS, REFER, REGISTER, UPDATE, SUBSCRIBE
Date: Wed, 22 Mar 2006 GMT
Proxy-Authorization: Digest username="107",realm="3CXPhoneSystem",uri="sip:[email protected];user=phone",response="15d20229b0fd02643f139a555b6e5896",nonce="414d535c053ca18b75:2a6f2d4684f3af21dd0757e532848a50",algorithm=MD5
Supported: replaces, join, norefersub
User-Agent: Cisco-CP7941G/8.0
Allow-Events: kpml, dialog
Content-Length: 0
Remote-Party-ID: "107" <sip:[email protected]>;party=calling;id-type=subscriber;privacy=off;screen=yes

<br>
16:51:23.746|.\CallCtrl.cpp(346)|Log2||CallCtrl:nIncomingCall:[CM503001]: Call(24): Incoming call from Ext.107 to <sip:[email protected];user=phone><br>
16:51:23.751|.\Extension.cpp(1407)|Log3||Extension:rintEndpointInfo:[CM505001]: Ext.107: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Cisco-CP7941G/8.0] PBX contact: [sip:[email protected]:5060]<br>
16:51:23.751|.\CallLeg.cpp(1194)|Log5||CallLeg::setRemoteSdp:Remote SDP is set for legC:24.1<br>
16:51:23.753|.\SLServer.cpp(861)|Log5|MediaServer|MediaServerReporting::SetRemoteParty:[MS210000] C:24.1:Offer received. RTP connection: 192.168.0.28:22854(22855)<br>
16:51:23.753|.\CallCtrl.cpp(529)|Log3||CallCtrl:nSelectRouteReq:[CM503010]: Making route(s) to <sip:[email protected];user=phone><br>
16:51:23.754|.\CallCtrl.cpp(708)|Log2||CallCtrl:nSelectRouteReq:[CM503004]: Call(24): Route 1: Ext:Ext.101@[Dev:sip:[email protected]:5060;transport=udp]<br>
16:51:23.797|.\SLServer.cpp(861)|Log5|MediaServer|MediaServerReporting::SetRemoteParty:[MS210006] C:24.2:Offer provided. Connection(by pass mode): 192.168.0.28:22854(22855)<br>
16:51:23.799|.\Target.cpp(441)|Log2||Target::makeOneInvite:[CM503025]: Call(24): Calling Ext:Ext.101@[Dev:sip:[email protected]:5060;transport=udp]<br>
16:51:42.115|.\Call.cpp(42)|Log3||??:Currently active calls - 1: [24]<br>
16:51:55.833|.\CallLeg.cpp(326)|Log2||CallLeg:nFailure:[CM503003]: Call(24): Call to sip:[email protected] has failed; Cause: 408 Request Timeout; internal<br>
16:51:55.837|.\CallCtrl.cpp(840)|Log2||CallCtrl:nRerouteReq:[CM503005]: Call(24): Forwarding: Ext:Ext.666@[Dev:sip:[email protected]:40600;rinstance=661c21fb8beaf794]<br>
16:51:55.887|.\SLServer.cpp(861)|Log5|MediaServer|MediaServerReporting::SetRemoteParty:[MS210004] C:24.3:Offer provided. Connection(proxy mode): 127.0.0.1:7098(7099)<br>
16:51:55.889|.\Target.cpp(441)|Log2||Target::makeOneInvite:[CM503025]: Call(24): Calling Ext:Ext.666@[Dev:sip:[email protected]:40600;rinstance=661c21fb8beaf794]<br>
16:51:56.095|.\CallLeg.cpp(315)|Log3||CallLeg:nAnswer:[CM503002]: Call(24): Alerting sip:[email protected]:40600;rinstance=661c21fb8beaf794<br>
16:51:56.095|.\Extension.cpp(1407)|Log3||Extension:rintEndpointInfo:[CM505001]: Ext.666: Device info: Device Identified: [Man: 3CX Ltd.;Mod: Voice Mail Menu;Rev: General] Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CX Voice Mail Menu] PBX contact: [sip:[email protected]:5060]<br>
16:51:56.098|.\CallLeg.cpp(1194)|Log5||CallLeg::setRemoteSdp:Remote SDP is set for legC:24.3<br>
16:51:56.099|.\SLServer.cpp(861)|Log5|MediaServer|MediaServerReporting::SetRemoteParty:[MS210001] C:24.3:Answer received. RTP connection[unsecure]: 127.0.0.1:40628(40629)<br>
16:51:56.102|.\SLServer.cpp(861)|Log5|MediaServer|MediaServerReporting::SetRemoteParty:[MS210005] C:24.1:Answer provided. Connection(proxy mode):192.168.0.249:7094(7095)<br>
16:51:56.104|.\CallCtrl.cpp(885)|Log2||CallCtrl:nLegConnected:[CM503007]: Call(24): Device joined: sip:[email protected]:5060;transport=udp<br>
16:51:56.106|.\CallCtrl.cpp(885)|Log2||CallCtrl:nLegConnected:[CM503007]: Call(24): Device joined: sip:[email protected]:40600;rinstance=661c21fb8beaf794<br>
16:51:56.583|.\CallLeg.cpp(594)|Log5||CallLeg:nConfirmed:Session 874 of leg C:24.1 is confirmed<br>
16:51:59.457|.\Call.cpp(1396)|Log2||Call::Terminate:[CM503008]: Call(24): Call is terminated<br>

 

[leejor]

16:51:55.833|.\CallLeg.cpp(326)|Log2||CallLeg:nFailure:[CM503003]: Call(24): Call to sip:[email protected] has failed; Cause: 408 Request Timeout; internal<br>

This indicates that Ext 101 has failed to respond to the INVITE from 3CX within the allotted time, so the call went to voicemail.
If the set is registering properly (check the log), then you need to figure out (using Wireshark), if the set "gets the message" at all, gets the message but responds to an incorrect destination, or, isn't responding at all.

 

[yerfdog]

Thats the thing, I dont see any SIP traffic from that phone in wireshark. I can see all other SIP traffic?

Very strange?

Any ideas?

 

[leejor]

As I haven't used that particular set, I'm afraid I'm not the one to help diagnose it. You could start from scratch and go over all of the settings again. Try provisioning with some very basic settings. Be sure to verify the network settings.