Dismiss Notice
We would like to remind you that we’re updating our login process for all 3CX forums whereby you will be able to login with the same credentials you use for the Partner or Customer Portal. Click here to read more.

Inbound call does not go to voicemail

Discussion in '3CX Phone System - General' started by mcbsys, Aug 27, 2010.

Thread Status:
Not open for further replies.
  1. mcbsys

    mcbsys New Member

    Joined:
    Oct 8, 2008
    Messages:
    191
    Likes Received:
    17
    Hi,

    I'm using 3CX 9.13545 with Service Pack 1.

    I have two VoIP providers and a Linksys SPA3102, all configured to route to Ring Group 80. That ring group is configured to ring extensions 10 and 11 simultaneously for 20 seconds, then forward to voicemail for extension 10.

    When I call the voip.ms number or the land line, everything works fine. Notice the transfer to voicemail extension 99 starting at 15:44:04.119:

    Code:
    15:44:18.026  [CM503008]: Call(3): Call is terminated
    15:44:08.184  Currently active calls - 1: [3]
    15:44:04.134  [CM503007]: Call(3): Device joined: sip:99@127.0.0.1:40600;rinstance=58e798bb8aecafff
    15:44:04.134  [CM503007]: Call(3): Device joined: sip:116517@losangeles.voip.ms:5060
    15:44:04.119  [CM505001]: Ext.99: 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:99@127.0.0.1:5060]
    15:44:04.119  [CM503002]: Call(3): Alerting sip:99@127.0.0.1:40600;rinstance=58e798bb8aecafff
    15:44:03.900  [CM503003]: Call(3): Call to sip:11@192.168.1.140 has failed; Cause: 487 Request Terminated; from IP:192.168.1.141:5060
    15:44:03.900  [CM503003]: Call(3): Call to sip:10@192.168.1.140 has failed; Cause: 487 Request Cancelled; from IP:192.168.1.145:5060
    15:44:03.900  [CM503025]: Call(3): Calling Ext:Ext.99@[Dev:sip:99@127.0.0.1:40600;rinstance=58e798bb8aecafff]
    15:44:03.869  [CM503005]: Call(3): Forwarding: Ext:Ext.99@[Dev:sip:99@127.0.0.1:40600;rinstance=58e798bb8aecafff]
    15:43:43.958  [CM505001]: Ext.10: Device info: Device Identified: [Man: Polycom;Mod: SoundPoint IP Series;Rev: General] Capabilities:[reinvite, replaces, unable-no-sdp, no-recvonly] UserAgent: [PolycomSoundPointIP-SPIP_430-UA/3.2.2.0477] PBX contact: [sip:10@192.168.1.140:5060]
    15:43:43.958  [CM503002]: Call(3): Alerting sip:10@192.168.1.145:5060
    15:43:43.818  [CM505001]: Ext.11: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [] PBX contact: [sip:11@192.168.1.140:5060]
    15:43:43.818  [CM503002]: Call(3): Alerting sip:11@192.168.1.141:5060
    15:43:43.755  [CM503025]: Call(3): Calling RingAll80:10Ext.1011Ext.11@[Dev:sip:11@192.168.1.141:5060]
    15:43:43.739  [CM503025]: Call(3): Calling RingAll80:10Ext.1011Ext.11@[Dev:sip:10@192.168.1.145:5060]
    15:43:43.724  [CM503004]: Call(3): Route 1: RingAll80:10Ext.1011Ext.11@[Dev:sip:10@192.168.1.145:5060,Dev:sip:11@192.168.1.141:5060]
    15:43:43.724  [CM503010]: Making route(s) to <sip:80@192.168.1.140:5060>
    15:43:43.724  [CM505003]: Provider:[voip.ms] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [VoIPMS/SERAST] PBX contact: [sip:116517@66.159.193.156:5060]
    15:43:43.692  [CM503001]: Call(3): Incoming call from 7195555555@(Ln.10003@voip.ms) to <sip:80@192.168.1.140:5060>
    15:43:43.552  [CM503012]: Inbound out-of-office hours rule (unnamed) for 10003 forwards to DN:80
    When I call the Callcentric number, 3CX does ring the extensions for 20 seconds, but then it never transfers to voicemail. The caller continues to hear ringing, and if the caller waits long enough, the phone starts ringing again. The following is actually one inbound call, although 3CX reports it as two:

    Code:
    15:27:19.166  [CM503003]: Call(2): Call to sip:10@192.168.1.140 has failed; Cause: 487 Request Cancelled; from IP:192.168.1.145:5060
    15:27:19.150  [CM503003]: Call(2): Call to sip:11@192.168.1.140 has failed; Cause: 487 Request Terminated; from IP:192.168.1.141:5060
    15:27:19.056  [CM503008]: Call(2): Call is terminated
    15:27:10.633  [CM505001]: Ext.10: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [] PBX contact: [sip:10@192.168.1.140:5060]
    15:27:10.633  [CM503002]: Call(2): Alerting sip:10@192.168.1.145:5060
    15:27:10.461  [CM505001]: Ext.11: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [] PBX contact: [sip:11@192.168.1.140:5060]
    15:27:10.461  [CM503002]: Call(2): Alerting sip:11@192.168.1.141:5060
    15:27:10.430  [CM503025]: Call(2): Calling RingAll80:10Ext.1011Ext.11@[Dev:sip:11@192.168.1.141:5060]
    15:27:10.414  [CM503025]: Call(2): Calling RingAll80:10Ext.1011Ext.11@[Dev:sip:10@192.168.1.145:5060]
    15:27:10.383  [CM503004]: Call(2): Route 1: RingAll80:10Ext.1011Ext.11@[Dev:sip:10@192.168.1.145:5060,Dev:sip:11@192.168.1.141:5060]
    15:27:10.383  [CM503010]: Making route(s) to <sip:80@192.168.1.140:5060>
    15:27:10.383  [CM505003]: Provider:[CallCentric - US] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [] PBX contact: [sip:17775551212@66.77.88.99:5060]
    15:27:10.367  [CM503001]: Call(2): Incoming call from 17195555555@(Ln.10000@CallCentric - US) to <sip:80@192.168.1.140:5060>
    15:27:10.226  [CM503012]: Inbound out-of-office hours rule (unnamed) for 10000 forwards to DN:80
    15:26:47.940  [CM503003]: Call(1): Call to sip:10@192.168.1.140 has failed; Cause: 487 Request Cancelled; from IP:192.168.1.145:5060
    15:26:47.940  [CM503003]: Call(1): Call to sip:11@192.168.1.140 has failed; Cause: 487 Request Terminated; from IP:192.168.1.141:5060
    15:26:47.846  [CM503008]: Call(1): Call is terminated
    15:26:35.938  Currently active calls - 1: [1]
    15:26:28.577  [CM505001]: Ext.10: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [] PBX contact: [sip:10@192.168.1.140:5060]
    15:26:28.577  [CM503002]: Call(1): Alerting sip:10@192.168.1.145:5060
    15:26:28.420  [CM505001]: Ext.11: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [] PBX contact: [sip:11@192.168.1.140:5060]
    15:26:28.420  [CM503002]: Call(1): Alerting sip:11@192.168.1.141:5060
    15:26:28.311  [CM503025]: Call(1): Calling RingAll80:10Ext.1011Ext.11@[Dev:sip:11@192.168.1.141:5060]
    15:26:28.295  [CM503025]: Call(1): Calling RingAll80:10Ext.1011Ext.11@[Dev:sip:10@192.168.1.145:5060]
    15:26:28.233  [CM503004]: Call(1): Route 1: RingAll80:10Ext.1011Ext.11@[Dev:sip:10@192.168.1.145:5060,Dev:sip:11@192.168.1.141:5060]
    15:26:28.233  [CM503010]: Making route(s) to <sip:80@192.168.1.140:5060>
    15:26:28.233  [CM505003]: Provider:[CallCentric - US] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [] PBX contact: [sip:17775551212@66.77.88.99:5060]
    15:26:28.217  [CM503001]: Call(1): Incoming call from 17195555555@(Ln.10000@CallCentric - US) to <sip:80@192.168.1.140:5060>
    15:26:27.889  [CM503012]: Inbound out-of-office hours rule (unnamed) for 10000 forwards to DN:80
    It seems strange that during the "good" call from voip.ms, 3CX was able to identify my SIP phone on extension 10 (Polycom SoundPoint), but during the "bad" call from Callcentric, extension 10 was unidentified and thus reported different capabilities. Why does the source of the inbound call affect the ability of 3CX to identify an extension?

    How do I get the unanswered inbound call to go to voicemail?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  2. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    11,127
    Likes Received:
    330
    Strange that there are two incoming call attempts from Callcentric. Wireshark would confirm that they are actually sending a second time and what your response was after the first attempt. I wonder if they are sending the second attempt because of a missing or incorrect response the first time. Have you tried changing the Supports Re-invite and
    Supports Replace in the Callcentric trunk settings?
     
  3. mcbsys

    mcbsys New Member

    Joined:
    Oct 8, 2008
    Messages:
    191
    Likes Received:
    17
    Thanks for the reply. You're right, Wireshark got me on the right path. When the first CallCentric call terminated, CallCentric sent a SIP CANCEL instruction to 3CX, which 3CX obeyed. 23 seconds later, while I'm still listening to the same ring tone on the outbound call, CallCentric sent a second INVITE to 3CX.

    Turns out that if you do not subscribe to CallCentric voicemail, by default it is supposed to answer with an "unavailable" message after 20 seconds. You can adjust the time. However, the generic unavailable message never picked up; it just keep starting the call over and over.

    I signed up for the (free) voicemail. The CallCentric interface changed, but by telling it to Send calls to voice mail after 25 seconds instead of 20, 3CX had time to pick up the call and handle the voicemail.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
    Basaran likes this.
Thread Status:
Not open for further replies.