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.

3CX v7 - Ring Group - bug? SOLVED

Discussion in '3CX Phone System - General' started by theromans, Jan 15, 2009.

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

    Joined:
    Dec 22, 2008
    Messages:
    15
    Likes Received:
    0
    Hello,
    I have installed 3CX v7 and noticed what I suspect to be a bug:
    I created a Ring Group with "Ring All" strategy and 3 members.
    Each single time I reboot the 3CX server, only one member receive calls from the group although the group still shows all three members to be there.
    I have to go into the web admin interface for my ring group, remove members, re-add, apply, ok to get all members to ring again.
    This is consistent after each reboot!
     
  2. nb

    nb Support Team
    Staff Member 3CX Support

    Joined:
    Jun 7, 2007
    Messages:
    2,153
    Likes Received:
    175
    Re: 3CX v7 - Ring Group - bug?

    Hi

    Could it be that after the restart, the registration period of those 2 phones that are not ringing is set to a very long time? And the one that is ringing registers immediately?

    Because that is what I suspect the problem to be. What is the registration period set on those 2 phones? What phones are they, make and model?

    How do they eventually start to ring then?
    Also what version are you running please?

    Check the logs - you should see that the PBX will try to target all 3 entities. If the extensions are still listed in the ring group, then the PBX will target them for sure. Let us know when you get answers to the above information. Thanks.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. theromans

    Joined:
    Dec 22, 2008
    Messages:
    15
    Likes Received:
    0
    Re: 3CX v7 - Ring Group - bug?

    Thank you very much for your response

    >Could it be that after the restart, the registration period of those 2 phones that are not ringing is set to a very long time? And the one that is ringing registers immediately?
    No they are all set to 60 seconds

    >Because that is what I suspect the problem to be. What is the registration period set on those 2 phones? What phones are they, make and model?
    They are all Perfectone IP-301

    >How do they eventually start to ring then?
    I have to go in the web admin, remove members from group, add members again, then press Apply-Ok

    >Also what version are you running please?
    Latest 3CX v7

    >Check the logs - you should see that the PBX will try to target all 3 entities
    I will check logs

    Thank you!
     
  4. William400

    William400 Well-Known Member

    Joined:
    Aug 21, 2006
    Messages:
    1,005
    Likes Received:
    0
    Re: 3CX v7 - Ring Group - bug?

    HI

    Please advise what the INVITE and routing information show in the Server Status log when the issue appears.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. theromans

    Joined:
    Dec 22, 2008
    Messages:
    15
    Likes Received:
    0
    Re: 3CX v7 - Ring Group - bug?

    Here is the log.
    The issue is persistent each time I reboot: incoming call is handled by Ringall group 100, extensions 102-103-104 belong to group 100.
    After reboot only extension 102 rings although all extensions are registered. See first two calls.
    To make it work I have to go in web admin to group 100, remove extensions, re-add extensions, press apply-ok (nothing else!) and all works fine again. See third call.

    09:56:09.781 [CM504001]: Ext.102: new contact is registered. Contact(s): [sip:102@192.168.1.6:5080/102]
    09:56:09.718 [CM504001]: Ext.103: new contact is registered. Contact(s): [sip:103@192.168.1.4:5080/103]
    09:56:09.593 [CM504001]: Ext.104: new contact is registered. Contact(s): [sip:104@192.168.1.5:5080/104]
    09:55:54.078 [CM504001]: Ext.101: new contact is registered. Contact(s): [sip:101@192.168.1.7:5065/101]
    09:55:14.921 [CM504001]: Ext.102: new contact is registered. Contact(s): [sip:102@192.168.1.6:5080/102]
    09:55:14.859 [CM504001]: Ext.103: new contact is registered. Contact(s): [sip:103@192.168.1.4:5080/103]
    09:55:14.734 [CM504001]: Ext.104: new contact is registered. Contact(s): [sip:104@192.168.1.5:5080/104]
    09:54:59.218 [CM504001]: Ext.101: new contact is registered. Contact(s): [sip:101@192.168.1.7:5065/101]
    09:54:44.093 [CM503008]: Call(8): Call is terminated
    09:54:44.093 [CM503008]: Call(8): Call is terminated
    09:54:28.078 [CM503007]: Call(8): Device joined: sip:102@192.168.1.6:5080
    09:54:28.062 [CM503007]: Call(8): Device joined: sip:0183738099@82.52.135.115:10004
    09:54:22.546 [CM505001]: Ext.104: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [CM5K-PHONE (804324)] Transport: [sip:192.168.1.100:5060]
    09:54:22.546 [CM503002]: Call(8): Alerting sip:104@192.168.1.5:5080
    09:54:22.531 [CM505001]: Ext.103: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [CM5K-PHONE (804324)] Transport: [sip:192.168.1.100:5060]
    09:54:22.531 [CM503002]: Call(8): Alerting sip:103@192.168.1.4:5080
    09:54:22.437 [CM505001]: Ext.102: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [CM5K-PHONE (804324)] Transport: [sip:192.168.1.100:5060]
    09:54:22.421 [CM503002]: Call(8): Alerting sip:102@192.168.1.6:5080
    09:54:21.890 [CM503004]: Call(8): Calling: RingAll100:102Ext.102103Ext.103104Ext.104@[Dev:sip:102@192.168.1.6:5080, Dev:sip:103@192.168.1.4:5080, Dev:sip:104@192.168.1.5:5080]
    09:54:21.875 [CM503010]: Making route(s) to <sip:100@192.168.1.100:5060>
    09:54:21.875 [CM505003]: Provider:[Eutelia] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [] Transport: [sip:192.168.1.100:5060]
    09:54:21.875 [CM503001]: Call(8): Incoming call from 0183738099@(Ln.10000@Eutelia) to <sip:100@192.168.1.100:5060>
    09:54:21.531 [CM503012]: Inbound office hours rule for 10000 forwards to DN:100
    09:54:20.078 [CM504001]: Ext.102: new contact is registered. Contact(s): [sip:102@192.168.1.6:5080/102]
    09:54:20.015 [CM504001]: Ext.103: new contact is registered. Contact(s): [sip:103@192.168.1.4:5080/103]
    09:54:19.890 [CM504001]: Ext.104: new contact is registered. Contact(s): [sip:104@192.168.1.5:5080/104]
    09:54:04.375 [CM504001]: Ext.101: new contact is registered. Contact(s): [sip:101@192.168.1.7:5065/101]
    09:53:25.234 [CM504001]: Ext.102: new contact is registered. Contact(s): [sip:102@192.168.1.6:5080/102]
    09:53:25.171 [CM504001]: Ext.103: new contact is registered. Contact(s): [sip:103@192.168.1.4:5080/103]
    09:53:25.046 [CM504001]: Ext.104: new contact is registered. Contact(s): [sip:104@192.168.1.5:5080/104]
    09:53:09.531 [CM504001]: Ext.101: new contact is registered. Contact(s): [sip:101@192.168.1.7:5065/101]

    09:52:54.953 [CM503008]: Call(7): Call is terminated
    09:52:54.953 [CM503008]: Call(7): Call is terminated
    09:52:40.234 [CM503007]: Call(7): Device joined: sip:102@192.168.1.6:5080
    09:52:40.234 [CM503007]: Call(7): Device joined: sip:0183738099@82.52.135.115:10004
    09:52:33.453 [CM505001]: Ext.102: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [CM5K-PHONE (804324)] Transport: [sip:192.168.1.100:5060]
    09:52:33.437 [CM503002]: Call(7): Alerting sip:102@192.168.1.6:5080
    09:52:32.937 [CM503004]: Call(7): Calling: Ext:Ext.102@[Dev:sip:102@192.168.1.6:5080]
    09:52:32.937 [CM503010]: Making route(s) to <sip:100@192.168.1.100:5060>
    09:52:32.937 [CM505003]: Provider:[Eutelia] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [] Transport: [sip:192.168.1.100:5060]
    09:52:32.937 [CM503001]: Call(7): Incoming call from 0183738099@(Ln.10000@Eutelia) to <sip:100@192.168.1.100:5060>
    09:52:32.703 [CM503012]: Inbound office hours rule for 10000 forwards to DN:100
    09:52:30.375 [CM504001]: Ext.102: new contact is registered. Contact(s): [sip:102@192.168.1.6:5080/102]
    09:52:30.312 [CM504001]: Ext.103: new contact is registered. Contact(s): [sip:103@192.168.1.4:5080/103]
    09:52:30.187 [CM504001]: Ext.104: new contact is registered. Contact(s): [sip:104@192.168.1.5:5080/104]
    09:52:14.656 [CM504001]: Ext.101: new contact is registered. Contact(s): [sip:101@192.168.1.7:5065/101]

    09:52:01.593 [CM503008]: Call(6): Call is terminated
    09:52:01.593 [CM503008]: Call(6): Call is terminated
    09:51:39.984 [CM503007]: Call(6): Device joined: sip:102@192.168.1.6:5080
    09:51:39.984 [CM503007]: Call(6): Device joined: sip:0183738099@82.52.135.115:10004
    09:51:35.515 [CM504001]: Ext.102: new contact is registered. Contact(s): [sip:102@192.168.1.6:5080/102]
    09:51:35.453 [CM504001]: Ext.103: new contact is registered. Contact(s): [sip:103@192.168.1.4:5080/103]
    09:51:35.390 [CM504001]: Ext.104: new contact is registered. Contact(s): [sip:104@192.168.1.5:5080/104]
    09:51:34.234 [CM505001]: Ext.102: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [CM5K-PHONE (804324)] Transport: [sip:192.168.1.100:5060]
    09:51:34.218 [CM503002]: Call(6): Alerting sip:102@192.168.1.6:5080
    09:51:33.656 [CM503004]: Call(6): Calling: Ext:Ext.102@[Dev:sip:102@192.168.1.6:5080]
    09:51:33.656 [CM503010]: Making route(s) to <sip:100@192.168.1.100:5060>
    09:51:33.656 [CM505003]: Provider:[Eutelia] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [] Transport: [sip:192.168.1.100:5060]
    09:51:33.656 [CM503001]: Call(6): Incoming call from 0183738099@(Ln.10000@Eutelia) to <sip:100@192.168.1.100:5060>
    09:51:33.421 [CM503012]: Inbound office hours rule for 10000 forwards to DN:100
    09:51:19.812 [CM504001]: Ext.101: new contact is registered. Contact(s): [sip:101@192.168.1.7:5065/101]
    09:50:40.703 [CM504001]: Ext.102: new contact is registered. Contact(s): [sip:102@192.168.1.6:5080/102]
    09:50:40.640 [CM504001]: Ext.104: new contact is registered. Contact(s): [sip:104@192.168.1.5:5080/104]
    09:50:40.578 [CM504001]: Ext.103: new contact is registered. Contact(s): [sip:103@192.168.1.4:5080/103]
     
  6. nb

    nb Support Team
    Staff Member 3CX Support

    Joined:
    Jun 7, 2007
    Messages:
    2,153
    Likes Received:
    175
    Re: 3CX v7 - Ring Group - bug?

    Can you send a backup of your configuration?

    Send it directly to nb@3cx.com

    Just a plain backup - no audio nor recording files are needed to keep it compact.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  7. nb

    nb Support Team
    Staff Member 3CX Support

    Joined:
    Jun 7, 2007
    Messages:
    2,153
    Likes Received:
    175
    Re: 3CX v7 - Ring Group - bug?

    Hi
    We replicated your problem. But only with your specific backup. We will check this out and let you know.

    Just a note - You don't need to add and remove the extensions. If you press apply on the ring group it is enough. At least for now this will save you some work. Just open the ring group after a restart of the services or machine and click apply in the ring group. The next time the ring group will be contacted, all the extensions will ring for you.

    I will update you with the status of this.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  8. theromans

    Joined:
    Dec 22, 2008
    Messages:
    15
    Likes Received:
    0
    Re: 3CX v7 - Ring Group - bug?

    Hi Nicky,
    And thank you for troubleshooting the issue.

    Build number is 7.0.4249.0.
    Yes it was a fresh install on WinXP SP3 Italian + .Net Framework 3.5.

    As you asked I created a new group and left it default settings (Ring all - 800).
    Then I added same extensions (102-103-104) and called: all extensions rang.
    After reboot still all extension were ringing when calling 800.

    So I removed both groups 100 and 800.
    I created a new group 100 – Ring all – members 102-103-104.

    Called 100: all members rang.
    After reboot ... only extension 102 rang!!
    Argh ...

    What’s wrong with my group 100??
    Is first group in group list having issue?
    Is group 100 having issue?

    Thanks & Regards
     
  9. nb

    nb Support Team
    Staff Member 3CX Support

    Joined:
    Jun 7, 2007
    Messages:
    2,153
    Likes Received:
    175
    Re: 3CX v7 - Ring Group - bug?

    Hi

    The problem is that extension 102 has the same SIP ID as the ring group i.e. 100 so direct sip calling is taking precedence.

    This also explains why you have to apply on the ring group again for the setting to take place.

    When you use non default values for Ring groups, queues or Digital receptionists, make sure that there are no other entries in the extension settings that have these settings perfect case in point is SIP ID. Since at the end of the day you are calling 100@PBXip when you call a ring group, it is treating it as a direct sip call. Change the SIP ID of 102 to something else and your ring group will activate immediately.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  10. theromans

    Joined:
    Dec 22, 2008
    Messages:
    15
    Likes Received:
    0
    Re: 3CX v7 - Ring Group - bug?

    Confirmed, issue sorted out!
    As that was the first default extension I didn't notice it kept default value!
    Thanks a lot!
     
  11. nb

    nb Support Team
    Staff Member 3CX Support

    Joined:
    Jun 7, 2007
    Messages:
    2,153
    Likes Received:
    175
    Re: 3CX v7 - Ring Group - bug?

    we have added validation for this - will be available in 7.1
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  12. SY

    SY Well-Known Member
    3CX Support

    Joined:
    Jan 26, 2007
    Messages:
    1,825
    Likes Received:
    2
    Re: 3CX v7 - Ring Group - bug?

    Could you please mark the headline as "SOLVED" (just append it to the headline)
    It may help everybody who read this forum.
    Thanks :)
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
Thread Status:
Not open for further replies.