Toggle sidebar Toggle sidebar

Extension won't ring when it's in two Ring Groups

Status
Not open for further replies.

commvisi

Joined
Aug 28, 2009
Messages
17
Reaction score
0
Hi,

We are running 3CX v8.0.9532.468

I have two Ring Groups setup, 'Support' as 801 and 'Everyone' as 800.
My Voip Trunk is setup to connect to Ring Group 801 - 'Support'.

The 'Support' ring group is setup to Ring All for 10 seconds with a Destination if no Answer to the 'Everyone' Ring Group.
The 'Everyone' ring group is setup to Ring All.
'Support' has extensions 203, 204, 205, and 206 as members.
'Everyone' has all extensions between 201 and 220 as members.

The problem I have is after 10 seconds of ringing the 'Support' group, when it starts ringing the 'Everyone' group, extensions 203 - 206 no longer ring even though they are members of the 'Everyone' group.

Basically I am trying to set it up so 3CX rings 4 extensions for the first 10 seconds, then ring extension 201 - 220 (including the frist four it originally tried) after that.

Thanks,
Troy.
 
commvisi said:
Hi,

We are running 3CX v8.0.9532.468

I have two Ring Groups setup, 'Support' as 801 and 'Everyone' as 800.
My Voip Trunk is setup to connect to Ring Group 801 - 'Support'.

The 'Support' ring group is setup to Ring All for 10 seconds with a Destination if no Answer to the 'Everyone' Ring Group.
The 'Everyone' ring group is setup to Ring All.
'Support' has extensions 203, 204, 205, and 206 as members.
'Everyone' has all extensions between 201 and 220 as members.

The problem I have is after 10 seconds of ringing the 'Support' group, when it starts ringing the 'Everyone' group, extensions 203 - 206 no longer ring even though they are members of the 'Everyone' group.

Basically I am trying to set it up so 3CX rings 4 extensions for the first 10 seconds, then ring extension 201 - 220 (including the frist four it originally tried) after that.

Thanks,
Troy.
Click to expand...


I tried the scenario you gave me above just in case there was a bug with it but couldnt find anything that looked like a bug. ( Although it found me a very minor one in the Call Assistant )
Do those 2 Phones have Sidecars with blf configured on them? Can you try and Decreasing their registration time to maybe 60 seconds and see what happens?
Also
 
I have the same issue, see my post in V8 Beta Forum for ore detail (http://www.3cx.com/forums/ring-groups-11853.html)

Ext 100 - 102 are Reception, 100-112 is Everyone. Reception phones ring, But when it times out and goes to second ring group, some phones in group 1 will not ring. Its not always the same phone, Ext 100 is fine, never effected. All Phones are Linksys SPA922, all phones have Identical config (apart from extn details).

Regards

Mark
 
HI,

Thanks for the reply. My problem seems very similar to Mark's issue. The Phones in the 801 group don’t have sidecars or BLF configured, and reducing the registration has not fixed the problem.

From the Log it looks like to original 3 extensions in Ring Group 801 respond with '487 Request Terminated;' when the call is forwarded to Ring Group 800 (which also includes these extensions).

Regards,
Troy.


Code: 
13:03:32.428  [CM503008]: Call(73): Call is terminated
13:03:30.679  [CM503007]: Call(73): Device joined: sip:[email protected]:40600;rinstance=b625c98240ed5b94
13:03:30.679  [CM503007]: Call(73): Device joined: sip:[email protected]:5060
13:03:30.663  [CM505001]: Ext.999: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CX Voice Mail Menu] PBX contact: [sip:[email protected]:5060]
13:03:30.663  [CM503002]: Call(73): Alerting sip:[email protected]:40600;rinstance=b625c98240ed5b94
13:03:30.554  [CM503003]: Call(73): Call to sip:[email protected]:5060 has failed; Cause: 487 Request Terminated; from IP:10.4.1.51:54222
13:03:30.444  [CM503003]: Call(73): Call to sip:[email protected] has failed; Cause: 487 Request Terminated; from IP:10.4.1.36:5060
13:03:30.444  [CM503025]: Call(73): Calling Ext:Ext.999@[Dev:sip:[email protected]:40600;rinstance=b625c98240ed5b94]
13:03:30.429  [CM503005]: Call(73): Forwarding: Ext:Ext.999@[Dev:sip:[email protected]:40600;rinstance=b625c98240ed5b94]
13:03:30.429  [CM503003]: Call(73): Call to sip:[email protected] has failed; Cause: 487 Request Terminated; from IP:10.4.1.10:1024
13:03:20.445  [CM505001]: Ext.206: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CXVoipPhone 4.0.9530.0] PBX contact: [sip:[email protected]:5060]
13:03:20.445  [CM503002]: Call(73): Alerting sip:[email protected]:54222;rinstance=5e833706bbca24c8
13:03:20.367  [CM505001]: Ext.204: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Cisco/SPA525G-7.2.5] PBX contact: [sip:[email protected]:5060]
13:03:20.367  [CM503002]: Call(73): Alerting sip:[email protected]:5060
13:03:20.367  [CM505001]: Ext.203: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [snom820/8.2.11] PBX contact: [sip:[email protected]:5060]
13:03:20.367  [CM503002]: Call(73): Alerting sip:[email protected]:1024;line=zkjodeb1
13:03:20.336  [CM503003]: Call(73): Call to sip:[email protected] has failed; Cause: 487 Request Terminated; from IP:10.4.1.4:2054
13:03:20.336  [CM503003]: Call(73): Call to sip:[email protected] has failed; Cause: 487 Request Cancelled; from IP:10.4.1.9:5060
13:03:20.320  [CM503003]: Call(73): Call to sip:[email protected] has failed; Cause: 487 Request Terminated; from IP:10.4.1.42:2052
13:03:20.320  [CM503025]: Call(73): Calling RingAll800:201202203Ext.203204Ext.204205Ext.205206Ext.206303@[Dev:sip:[email protected]:54222;rinstance=5e833706bbca24c8]
13:03:20.305  [CM503025]: Call(73): Calling RingAll800:201202203Ext.203204Ext.204205Ext.205206Ext.206303@[Dev:sip:[email protected]:5060]
13:03:20.289  [CM503025]: Call(73): Calling RingAll800:201202203Ext.203204Ext.204205Ext.205206Ext.206303@[Dev:sip:[email protected]:1024;line=zkjodeb1]
13:03:20.289  [CM503005]: Call(73): Forwarding: RingAll800:201202203Ext.203204Ext.204205Ext.205206Ext.206303@[Dev:sip:[email protected]:1024;line=zkjodeb1,Dev:sip:[email protected]:5060,Dev:sip:[email protected]:54222;rinstance=5e833706bbca24c8]
13:03:10.447  [CM505001]: Ext.202: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, unable-no-sdp, no-recvonly] UserAgent: [PolycomSoundPointIP-SPIP_550-UA/3.1.1.0137] PBX contact: [sip:[email protected]:5060]
13:03:10.447  [CM503002]: Call(73): Alerting sip:[email protected]:5060
13:03:10.353  [CM505001]: Ext.201: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [snom360/7.3.14] PBX contact: [sip:[email protected]:5060]
13:03:10.353  [CM503002]: Call(73): Alerting sip:[email protected]:2052;line=vi0cxt5t
13:03:10.306  [CM505001]: Ext.303: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [snom360/6.5.15] PBX contact: [sip:[email protected]:5060]
13:03:10.306  [CM503002]: Call(73): Alerting sip:[email protected]:2054;line=kr4lp4nz
13:03:10.228  [CM503025]: Call(73): Calling RingAll801:201Ext.201303Ext.303202Ext.202@[Dev:sip:[email protected]:5060]
13:03:10.212  [CM503025]: Call(73): Calling RingAll801:201Ext.201303Ext.303202Ext.202@[Dev:sip:[email protected]:2054;line=kr4lp4nz]
13:03:10.212  [CM503025]: Call(73): Calling RingAll801:201Ext.201303Ext.303202Ext.202@[Dev:sip:[email protected]:2052;line=vi0cxt5t]
13:03:10.165  [CM503004]: Call(73): Route 1: RingAll801:201Ext.201303Ext.303202Ext.202@[Dev:sip:[email protected]:2052;line=vi0cxt5t,Dev:sip:[email protected]:2054;line=kr4lp4nz,Dev:sip:[email protected]:5060]
13:03:10.165  [CM503010]: Making route(s) to <sip:[email protected]:5060>
13:03:10.165  [CM505002]: Gateway:[Patton 4FXO] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Patton SN4114 JO EUI 00A0BA04C766 R5.4 2009-07-20 H323 SIP FXS FXO M5T SIP Stack/4.0.28.28] PBX contact: [sip:[email protected]:5060]
13:03:10.150  [CM503001]: Call(73): Incoming call from anonymous@(Ln.10002@Patton 4FXO) to <sip:[email protected]:5060>
13:03:10.150  [CM503012]: Inbound office hours rule (unnamed) for 10002 forwards to DN:801
 
I think that all phones respond with '487 Request Terminated; when they stop ringing, but I have noticed with the install we have that the effected phones report '487 Request Terminated after the second ring group has started, then they remain idle until the ring group times out and goes to another, then the extensions in reception will start again, and others is the workshop will stop (if that makes sense)

I think an extension to this problem is that if an extension is busy when the ring group is started, it won't ring until it is idle when another ring group starts. Eg if ext 100 is on the phone and another call comes in, other phones in the ring group will ring, but even if ext 100 ends the current call it will not ring until another ring group is started.

If anyone knows a way to rectify the last issue, it may solve both issues.

Regards

Mark
 
The problem seems to be in a too-short of a delay in switching contexts from one ring group to another so the phones that were in the first ring group dont get rang in the second one. To solve this I had ring group 1 time out to a digital receptionist with a 1 second timeout to ring group 2 and it worked fine. If there was a small after terminating the calls from ring group 1 before switching contexts to ring group 2 I think that might solve this.
 
Thanks KerryG,

I tried to create another ring group with no extensions but the software will not allow it, but your method of a digital receptionist would work better. Thanks for you input, I'll give it a go.

Regards Mark
 
We are experiencing the same issue. Does anyone know whether there is a patch for it.

thanks.
bc
 
You can try installing the newest PBX Available.

You currently have 9524.
The newest version is v8.10116 (Approx. 40Mb) and should have this fixed.
 
Hi,

We upgraded to 10116 and the problem is fixed.


Troy.
 
Status
Not open for further replies.

Latest Posts

Forum statistics

Threads
111,881
Messages
589,535
Members
164,739
Latest member
wmlcon
3CX Logo Footer Copyright © Sitemap Privacy
Top Bottom