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.

Call Waiting

Discussion in '3CX Phone System - General' started by layton, Feb 19, 2014.

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

    Joined:
    Jan 18, 2011
    Messages:
    47
    Likes Received:
    3
    OK - I have weird issue.

    Just going live with a new 3CX 2012 SP3 install with Yealink T46G phones (all running firmware 28.71.0.176) where call waiting isn't acting as expected all of the time. If the receptionist is on a call and someone internal calls her extension, she sees a second call coming in & can choose to put the first call on hold & pick up the second call. This of course is the expected (& desired) behavior.

    Where it gets interesting is when an outside call comes in. All outside calls are going to a ring group. If the receptionist is on an active call when another external call comes into the ring group, her phone does not ring the second call at all - only the other extensions in the ring group. This isn't limited to just the receptionist's extension - we are seeing this behavior with all extensions in the ring group(s).

    All extensions have Call Waiting enabled in their forwarding preferences, all extensions are currently showing an Available status, and the ring groups are set to a "Ring All" strategy. I've compared these settings with the settings for our internal 3CX system (also v12 SP3 with the same Yealink T46G phones on the same firmware) - and everything seems to match.

    Here's an example of what I'm seeing in the logs:

    19-Feb-2014 15:15:48.002 L:143.1[Line:10000<<4028809045] forwards call from RingAll:811 to RingAll:812 based on rule
    19-Feb-2014 15:15:48.002 L:143.1[Line:10000<<4028809045] failed to reach RingAll:811, reason Temporarily Unavailable
    19-Feb-2014 15:15:48.002 [CM503026]: Call(C:143): Route 1 to RingAll811[Ext.301,Ext.311] is not active (Busy/Not registered)
    19-Feb-2014 15:15:48.002 L:143.1[Line:10000<<4028809045] target's endpoint Extn:311 is Busy
    19-Feb-2014 15:15:48.002 L:143.1[Line:10000<<4028809045] target's endpoint Extn:301 is Busy
    19-Feb-2014 15:15:48.001 [CM503001]: Call(C:143): Incoming call from Line:10000<<########## to <sip:811@fe80::94f2:c438:a500:6dc5:5060>

    Basically, ring group 811 contains two extensions (301 & 311) that are the primary call handlers. We have a secondary ring group set up (812) that has the primary call handlers (301 & 311) as well as 3 other extensions. So if a call that rings the first ring group isn't answered in 15 seconds, it rolls over to the second ring group. The above logs show that even though both extensions 301 & 311 have their call waiting enabled - 3CX is detecting them as busy and rolling over to the 812 ring group instead of 811. And even then the extensions are not being rang even though they are part of the 812 ring group.

    So what stupidly simple thing am I missing? :)

    Thanks!

    Chad
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  2. layton

    Joined:
    Jan 18, 2011
    Messages:
    47
    Likes Received:
    3
    Don't be confused by my saying 3CX 2012 - should be v12. Not sure where 2012 came from :)
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. CentrexJ

    CentrexJ Member

    Joined:
    May 5, 2009
    Messages:
    458
    Likes Received:
    75
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
    #3 CentrexJ, Feb 19, 2014
    Last edited by a moderator: Feb 20, 2017
  4. layton

    Joined:
    Jan 18, 2011
    Messages:
    47
    Likes Received:
    3
    Perfect - I had completely forgotten about that, and my searches weren't pulling anything up.

    Thanks!

    Chad
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
Thread Status:
Not open for further replies.