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.

2 simultaneous incoming calls on PSTN gateway?

Discussion in '3CX Phone System - General' started by beaterku, Feb 4, 2011.

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

    Joined:
    Dec 16, 2010
    Messages:
    42
    Likes Received:
    0
    Hello all, I am getting close to working out all of the small nuances in my 3CX setup. My setus is as follows:

    I have 2 PSTN lines coming in through a grandstream gateway.
    The first gateway port, 10001, forwards calls to ring group L1. Ring group L1 consists of ext. 102,102,102,104
    The seccond gateway port, 10002, forwards calls to ring group L2. Ring group L2 consists of ext. 102,102,102,104
    If no one answers in L1, it forwards to a DR to the caller can leave a voicemail with any of the extensions.
    If no one answers in L2, it forwards to a DR to the caller can leave a voicemail with any of the extensions.

    My theory behind the 2 identical ring groups was to help simplify the forwarding within the 3CX. I may be wrong here. My last hurdle is the somewhat rare occasion when I have 2 simultaneous calls coming in at the same time. As of now, which ever line was first (we are talking miliseconds here) gets forwarded on to a ring group and the other line gets forwarded immediately to the DR. My thinking was to have 2 separate ring groups to handle each line independently. Then I got to thinking, well if one ring group is ringing all extensions, technically all extensions are busy so I tried to set up one of my phones with 2 extensions (102 & 202) and changes my setup to the following:

    The first gateway port, 10001, forwards calls to ring group L1. Ring group L1 consists of ext. 102,102,102,104
    The seccond gateway port, 10002, forwards calls to ring group L2. Ring group L2 consists of ext. 202
    If no one answers in L1, it forwards to a DR to the caller can leave a voicemail with any of the extensions.
    If no one answers in L2, it forwards to a DR to the caller can leave a voicemail with any of the extensions.

    This still does not allow both simultaneous calls to be forwards to the phone with extensions 102 & 202.

    Am I thinking about this all wrong?

    EDIT: Below is the log of the situation in question

    Code:
    10:32:54.067  [CM503003]: Call(111): Call to sip:202@192.xxx.x.141has failed; Cause: 487 Request Terminated; from IP:192.xxx.x.150:5061
    10:32:54.036  [CM503003]: Call(111): Call to sip:101@192.xxx.x.141has failed; Cause: 487 Request Terminated; from IP:192.xxx.x.151:5060
    10:32:54.036  [CM503003]: Call(111): Call to sip:103@192.xxx.x.141has failed; Cause: 487 Request Terminated; from IP:192.xxx.x.152:5060
    10:32:54.036  [CM503003]: Call(111): Call to sip:104@192.xxx.x.141has failed; Cause: 487 Request Terminated; from IP:192.xxx.x.153:5060
    10:32:54.036  [CM503003]: Call(111): Call to sip:102@192.xxx.x.141has failed; Cause: 487 Request Terminated; from IP:192.xxx.x.150:5060
    10:32:53.926  [CM503008]: Call(111): Call is terminated
    10:32:53.880  Currently active calls - 1: [111]
    10:32:46.922  [CM503008]: Call(112): Call is terminated
    10:32:41.992  [CM503007]: Call(112): Device joined: sip:802@127.0.0.1:40600;rinstance=20b68472642f4c60
    10:32:41.992  [CM503007]: Call(112): Device joined: sip:10002@192.xxx.x.142:5062;transport=udp
    10:32:41.992  [CM505001]: Ext.802: Device info: Device Identified: [Man: 3CX Ltd.;Mod: 3CX IVR;Rev: General] Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CX IVR] PBX contact: [sip:802@127.0.0.1:5060]
    10:32:41.992  [CM503002]: Call(112): Alerting sip:802@127.0.0.1:40600;rinstance=20b68472642f4c60
    10:32:41.836  [CM503025]: Call(112): Calling Ext:Ext.802@[Dev:sip:802@127.0.0.1:40600;rinstance=20b68472642f4c60]
    10:32:41.789  [CM503005]: Call(112): Forwarding: Ext:Ext.802@[Dev:sip:802@127.0.0.1:40600;rinstance=20b68472642f4c60]
    10:32:41.789  [CM503016]: Call(112): Attempt to reach <sip:805@192.xxx.x.141:5060> failed. Reason: Not Registered
    10:32:41.789  [CM503017]: Call(112): Target is not registered: RingAll805:202
    10:32:41.789  [CM503010]: Making route(s) to <sip:805@192.xxx.x.141:5060>
    10:32:41.789  [CM505002]: Gateway:[Grandstream_GXW4104] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Grandstream GXW4104 (HW 1.0, Ch:6) 1.3.4.10] PBX contact: [sip:10002@192.xxx.x.141:5060]
    10:32:41.774  [CM503001]: Call(112): Incoming call from 913xxxxx93@(Ln.10002@Grandstream_GXW4104) to <sip:805@192.xxx.x.141:5060>
    10:32:41.774  [CM503012]: Inbound office hours rule (unnamed) for 10002 forwards to DN:805
    10:32:41.087  [CM505001]: Ext.202: Device info: Device Identified: [Man: Cisco;Mod: SPA Series;Rev: General] Capabilities:[reinvite, replaces, unable-no-sdp, no-recvonly] UserAgent: [Cisco/SPA504G-7.4.6] PBX contact: [sip:202@192.xxx.x.141:5060]
    10:32:41.087  [CM503002]: Call(111): Alerting sip:202@192.xxx.x.150:5061
    10:32:41.087  [CM505001]: Ext.102: Device info: Device Identified: [Man: Cisco;Mod: SPA Series;Rev: General] Capabilities:[reinvite, replaces, unable-no-sdp, no-recvonly] UserAgent: [Cisco/SPA504G-7.4.6] PBX contact: [sip:102@192.xxx.x.141:5060]
    10:32:41.087  [CM503002]: Call(111): Alerting sip:102@192.xxx.x.150:5060
    10:32:41.025  [CM505001]: Ext.104: Device info: Device Identified: [Man: Cisco;Mod: SPA Series;Rev: General] Capabilities:[reinvite, replaces, unable-no-sdp, no-recvonly] UserAgent: [Cisco/SPA504G-7.4.6] PBX contact: [sip:104@192.xxx.x.141:5060]
    10:32:41.025  [CM503002]: Call(111): Alerting sip:104@192.xxx.x.153:5060
    10:32:41.025  [CM505001]: Ext.101: Device info: Device Identified: [Man: Cisco;Mod: SPA Series;Rev: General] Capabilities:[reinvite, replaces, unable-no-sdp, no-recvonly] UserAgent: [Cisco/SPA504G-7.4.6] PBX contact: [sip:101@192.xxx.x.141:5060]
    10:32:41.025  [CM503002]: Call(111): Alerting sip:101@192.xxx.x.151:5060
    10:32:41.009  [CM505001]: Ext.103: Device info: Device Identified: [Man: Cisco;Mod: SPA Series;Rev: General] Capabilities:[reinvite, replaces, unable-no-sdp, no-recvonly] UserAgent: [Cisco/SPA504G-7.4.6] PBX contact: [sip:103@192.xxx.x.141:5060]
    10:32:41.009  [CM503002]: Call(111): Alerting sip:103@192.xxx.x.152:5060
    10:32:40.947  [CM503025]: Call(111): Calling RingAll800:102Ext.102101Ext.101103Ext.103104Ext.104202Ext.202@[Dev:sip:202@192.xxx.x.150:5061]
    10:32:40.947  [CM503025]: Call(111): Calling RingAll800:102Ext.102101Ext.101103Ext.103104Ext.104202Ext.202@[Dev:sip:104@192.xxx.x.153:5060]
    10:32:40.947  [CM503025]: Call(111): Calling RingAll800:102Ext.102101Ext.101103Ext.103104Ext.104202Ext.202@[Dev:sip:103@192.xxx.x.152:5060]
    10:32:40.931  [CM503025]: Call(111): Calling RingAll800:102Ext.102101Ext.101103Ext.103104Ext.104202Ext.202@[Dev:sip:101@192.xxx.x.151:5060]
    10:32:40.931  [CM503025]: Call(111): Calling RingAll800:102Ext.102101Ext.101103Ext.103104Ext.104202Ext.202@[Dev:sip:102@192.xxx.x.150:5060]
    10:32:40.885  [CM503004]: Call(111): Route 1: RingAll800:102Ext.102101Ext.101103Ext.103104Ext.104202Ext.202@[Dev:sip:102@192.xxx.x.150:5060,Dev:sip:101@192.xxx.x.151:5060,Dev:sip:103@192.xxx.x.152:5060,Dev:sip:104@192.xxx.x.153:5060,Dev:sip:202@192.xxx.x.150:5061]
    10:32:40.885  [CM503010]: Making route(s) to <sip:800@192.xxx.x.141:5060>
    10:32:40.885  [CM505002]: Gateway:[Grandstream_GXW4104] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Grandstream GXW4104 (HW 1.0, Ch:5) 1.3.4.10] PBX contact: [sip:10001@192.xxx.x.141:5060]
    10:32:40.869  [CM503001]: Call(111): Incoming call from 913xxxxx51@(Ln.10001@Grandstream_GXW4104) to <sip:800@192.xxx.x.141:5060>
    10:32:40.869  [CM503012]: Inbound office hours rule (unnamed) for 10001 forwards to DN:800
    
     
  2. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    11,095
    Likes Received:
    327
    If a set extension (or key appearance) were in the process of ringing, it won't be able to receive a second call, at the same time until it stopped ringing.

    Are you using single line sets or multi-line? If you have multi-line phones, have you tried just one ring group with, )as an example) Ext 201 as key one, and ext 202 as key 2 on all sets. Put the persons actual extension, 101,102,103,104,etc., on a key farther up the set. Put the new extensions only into the ring group. Set the extensions to allow more than one call at a time (use the set status for busy, not the PBX status). Set the ring group to ring sequentially so that both 201 and 202 won't ring simultaneously on one call.

    Haven't set that up myself, just an idea you may want to consider, or, perhaps someone else has a suggestion that they have used.
     
  3. abc123

    abc123 Active Member

    Joined:
    Nov 9, 2009
    Messages:
    712
    Likes Received:
    1
    You made a mistake or two.

    Firstly in your logs you have ext 202 in both ring groups still. So the first group is 101, 102,103,104 and 202 and the second group is 202. 202 is busy being rung by the first call so is not available in the second ring group.

    if a phone is ringing (either from another group/queue or direct) or is busy it is not part of the ring group for that period of time. As the second group is only one extension it has no others so rolls over to your next rule (the DA).

    But your setup wont achieve what you want. You need a queue (and possibly only one but that is up to you). The queue answers the call (even can have a welcome prompt) and then rings the extensions.

    So set up Q1 with 101,102,103,104 in it. Make sure all extensions are logged into the queue (do it on the admin page for the extension). Set the first line to ring the Q1. Set the second line to ring Q1. Now it will work as you want it AND your users will queue up until you can get to them.

    Please take not of the ring timeout (top) and max wait time (bottom). The ring timeout means how long it will ring the extension before moving on. Even with a ring all - set this to a low (20 sec) value. The reason is that if a phone is busy it is not able to ring in this queue. Even when it hangs up it is not going to ring as 3cx saw it was not available. But at the end of the ring timeout 3cx tries them all again and this time it is available to ring.

    The max wait time is how long the caller waits in the queue before you move them on (destination if no answer). Be careful as the default is 30minutes!!!. We normally leave them from 30 seconds to 2 minutes depending on the queue. Then we forward to a digital assistant which asks if the want to keep waiting (press 1 or do nothing) which sends them back to the queue, or press 2 to leave a voicemail.

    That will work for you.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
Thread Status:
Not open for further replies.