forward on busy when rung via ringgroup

Discussion in '3CX Phone System - General' started by nickywicky, Mar 29, 2010.

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

    Joined:
    Jan 20, 2010
    Messages:
    3
    Likes Received:
    0
    I wonder if someone can give me some configuration tips for a problem I am having.
    I am using the free version, and had plenty of fun in the last few months getting it going.
    I bought some cheap Cisco 7940's and have got them all up and going.

    However, the 7940's have two extensions and are having trouble with the forwarding on busy from one extension to the other.

    On an incoming call the call comes to extension 100 (which doesn't have anything on it).
    Extension 100 will then forward all calls to ringgroup 800.
    (This is so I can forward based on callerids as well to other extensions).
    Now the problem is when the first extion of a 7940 is busy, the call doesn't get forwarded to the second extension, even though forwarding on busy is enabled.

    e.g. say a Cisco 7940 is on extensions 115 and 116, and call forwarding on busy is set from 115 to 116. This all works if you just dial 115, but if 115 is being dialed from a ringgroup it doesn't.

    I can get around this by including 116 in the ringgroup, but this means the cisco thinks it is getting this call twice most of the time. (two lines ring, missed calls goes up by two each time etc..)

    Nick
     
  2. nickywicky

    Joined:
    Jan 20, 2010
    Messages:
    3
    Likes Received:
    0
    oh and here's a server status log... I make a call from 115 to another extension to busy it out.. and 116 never gets rung...
    Code:
    13:29:50.938  [CM503008]: Call(94): Call is terminated
    13:29:45.828  [CM503008]: Call(95): Call is terminated
    13:29:39.705  [CM505001]: Ext.145: Device info: Device Identified: [Man: Cisco;Mod: 7940;Rev: General] Capabilities:[reinvite, replaces, unable-no-sdp, no-recvonly] UserAgent: [Cisco-CP7940G/8.0] PBX contact: [sip:145@10.55.1.13:5060]
    13:29:39.705  [CM503002]: Call(95): Alerting sip:145@10.55.1.185:5061;transport=udp
    13:29:39.697  [CM505001]: Ext.130: Device info: Device Identified: [Man: Cisco;Mod: 7940;Rev: General] Capabilities:[reinvite, replaces, unable-no-sdp, no-recvonly] UserAgent: [Cisco-CP7940G/8.0] PBX contact: [sip:130@10.55.1.13:5060]
    13:29:39.696  [CM503002]: Call(95): Alerting sip:130@10.55.1.180:5061;transport=udp
    13:29:39.667  [CM505001]: Ext.101: Device info: Device Identified: [Man: Counterpath;Mod: eyeBeam;Rev: General] Capabilities:[reinvite, no-replaces, unable-no-sdp, recvonly] UserAgent: [eyeBeam release 1102q stamp 51814] PBX contact: [sip:101@10.55.1.13:5060]
    13:29:39.666  [CM503002]: Call(95): Alerting sip:101@10.55.1.16:17393;rinstance=8ee6477aefea908e
    13:29:39.470  [CM505001]: Ext.200: Device info: Device Identified: [Man: Linksys;Mod: SPA Series;Rev: General] Capabilities:[reinvite, no-replaces, able-no-sdp, recvonly] UserAgent: [Linksys/SPA3102-5.1.10(GW)] PBX contact: [sip:200@10.55.1.13:5060]
    13:29:39.470  [CM503002]: Call(95): Alerting sip:200@10.55.1.181:5060
    13:29:39.435  [CM503025]: Call(95): Calling RingAll800:200Ext.200120Ext.120121Ext.121101Ext.101201Ext.201162Ext.162115130Ext.130145Ext.145@[Dev:sip:145@10.55.1.185:5061;transport=udp]
    13:29:39.423  [CM503025]: Call(95): Calling RingAll800:200Ext.200120Ext.120121Ext.121101Ext.101201Ext.201162Ext.162115130Ext.130145Ext.145@[Dev:sip:130@10.55.1.180:5061;transport=udp]
    13:29:39.413  [CM503025]: Call(95): Calling RingAll800:200Ext.200120Ext.120121Ext.121101Ext.101201Ext.201162Ext.162115130Ext.130145Ext.145@[Dev:sip:201@10.55.1.182:5060]
    13:29:39.403  [CM503025]: Call(95): Calling RingAll800:200Ext.200120Ext.120121Ext.121101Ext.101201Ext.201162Ext.162115130Ext.130145Ext.145@[Dev:sip:101@10.55.1.16:17393;rinstance=8ee6477aefea908e]
    13:29:39.393  [CM503025]: Call(95): Calling RingAll800:200Ext.200120Ext.120121Ext.121101Ext.101201Ext.201162Ext.162115130Ext.130145Ext.145@[Dev:sip:200@10.55.1.181:5060]
    13:29:39.376  [CM503004]: Call(95): Route 1: RingAll800:200Ext.200120Ext.120121Ext.121101Ext.101201Ext.201162Ext.162115130Ext.130145Ext.145@[Dev:sip:200@10.55.1.181:5060,Dev:sip:101@10.55.1.16:17393;rinstance=8ee6477aefea908e,Dev:sip:201@10.55.1.182:5060,Dev:sip:130@10.55.1.180:5061;transport=udp,Dev:sip:145@10.55.1.185:5061;transport=udp]
    13:29:39.367  [CM503010]: Making route(s) to <sip:100@10.55.1.13:5060>
    13:29:39.365  [CM505003]: Provider:[kiwilink] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [NZ PBX] PBX contact: [sip:095340009@203.109.246.245:5060]
    13:29:39.360  [CM503001]: Call(95): Incoming call from 021549898@(Ln.10004@kiwilink) to <sip:100@10.55.1.13:5060>
    13:29:39.341  [CM503012]: Inbound office hours rule (unnamed) for 10004 forwards to DN:100
    13:29:32.002  [CM503007]: Call(94): Device joined: sip:110@10.55.1.13:13066;rinstance=87920ecd79147250
    13:29:31.997  [CM503007]: Call(94): Device joined: sip:115@10.55.1.186:5061;transport=udp
    13:29:31.684  [CM505001]: Ext.110: Device info: Device Identified: [Man: Counterpath;Mod: eyeBeam;Rev: General] Capabilities:[reinvite, no-replaces, unable-no-sdp, recvonly] UserAgent: [eyeBeam release 1102q stamp 51814] PBX contact: [sip:110@10.55.1.13:5060]
    13:29:31.683  [CM503002]: Call(94): Alerting sip:110@10.55.1.13:13066;rinstance=87920ecd79147250
    13:29:31.227  [CM503025]: Call(94): Calling Ext:Ext.110@[Dev:sip:110@10.55.1.13:13066;rinstance=87920ecd79147250]
    13:29:31.187  [CM503004]: Call(94): Route 1: Ext:Ext.110@[Dev:sip:110@10.55.1.13:13066;rinstance=87920ecd79147250]
    13:29:31.186  [CM503010]: Making route(s) to <sip:110@10.55.1.13;user=phone>
    13:29:31.180  [CM505001]: Ext.115: Device info: Device Identified: [Man: Cisco;Mod: 7940;Rev: General] Capabilities:[reinvite, replaces, unable-no-sdp, no-recvonly] UserAgent: [Cisco-CP7940G/8.0] PBX contact: [sip:115@10.55.1.13:5060]
    13:29:31.175  [CM503001]: Call(94): Incoming call from Ext.115 to <sip:110@10.55.1.13;user=phone>
     
  3. nickywicky

    Joined:
    Jan 20, 2010
    Messages:
    3
    Likes Received:
    0
    ok, I can answer my own question now... :).


    The answer is......

    ALLOWUSEBUSYOPTIONFORGROUP 0 When set to "1" this will enable multiple calls to members of a Ring Group when the extensions of the Ring Group members have a Busy Detection Mechanism set to 'Use Phone status'.


    So I set it to 1..
     
  4. mfm

    mfm Active Member

    Joined:
    Mar 4, 2010
    Messages:
    641
    Likes Received:
    2
    Yes that is the correct setting for ring groups. Glad you discovered it. Also all extensions concerned must be set to "use phone status".
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
Thread Status:
Not open for further replies.