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.

Multi-Cell Multiple registrations per account

Discussion in '3CX Phone System - General' started by MNimand, Jun 26, 2012.

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

    Joined:
    Jun 26, 2012
    Messages:
    5
    Likes Received:
    0
    Hi There,

    I'm missing SIP Server support for multiple registrations per account.

    I have a multi-cell system, with wireless DECT phone - I have 40 bases, and everytime the phones makes handover to a new base, they are registering from a new IP - however, I'm not able to get this working corretly in 3CX.

    Is there any hotfix for this issue?

    Regards,
    Mikkel
     
  2. lneblett

    lneblett Well-Known Member

    Joined:
    Sep 7, 2010
    Messages:
    2,086
    Likes Received:
    64
    Out of curiosity, what make of DECT system?
     
  3. MNimand

    Joined:
    Jun 26, 2012
    Messages:
    5
    Likes Received:
    0
    Hi,

    It is similiar to this Samsung system
    http://www.samsungbusiness.com/business/pages/content/dect.aspx

    I know for sure this system does support multiple registrations per account. And it is tested with several other PBX's... I just prefer using 3CX as PBX :)
     
  4. lneblett

    lneblett Well-Known Member

    Joined:
    Sep 7, 2010
    Messages:
    2,086
    Likes Received:
    64
    Looks interesting and i know that some of us have been asking about roaming DECT, but as far I have seen, you are the 1st to have actually used. I looked at the site, but the info is not very detailed, so am unable to even suggest possible fixes.

    From what I gather, the issue is that when the DECT handheld roams from one base station to another, there is a new IP that is now engaged which represents the base station IP to which the DECT handheld is at that time currently associated. I assume that there would be some kind of reinvite sent by that base to 3CX telling it what the new IP is, but I am guessing.
     
  5. SY

    SY Well-Known Member
    3CX Support

    Joined:
    Jan 26, 2007
    Messages:
    1,825
    Likes Received:
    2
    It works out of the box.
    Could you please provide more information about
    ?

    Thanks
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  6. MNimand

    Joined:
    Jun 26, 2012
    Messages:
    5
    Likes Received:
    0
    This is excactly the problem - let me see if I can get some more details about how the bases and phones will reregister.

    Strange. I enabled the option in the bases, and it works after first registration. If I then will power cycle the phone, it will in most cases register from another base, and then, calls doesn't work. To resolve it, I have to deregister the handset and reregister it, and then it works again - until it is rebooted or roaming.

    Br
    Mikkel
     
  7. MNimand

    Joined:
    Jun 26, 2012
    Messages:
    5
    Likes Received:
    0
    Ok - here is some more information. I got my handset registered first time at base 192.168.11.153 - I was now able to make calls with no problems.
    Then I tried to power cycle and make a new call, but this time without succcess. As you can see from the log below the extension is first registered on 192.168.11.153, then after first power cycle it is registered from 192.168.11.152, then .154, and so on .. Until it randomly registers at .153 again.

    Every time i rebooted the phone I tried to make a call, but nothing is logged in the Service Activity log in 3CX.

    3CX Server Activity log
    10:45:43.513 [CM503008]: Call(22): Call is terminated
    10:45:40.858 [CM505003]: Provider:[Generic VoIP Provider -] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [VoipProvider] PBX contact: [sip:96322511@3CXIP:5060]
    10:45:40.858 [CM503002]: Call(22): Alerting sip:96322511@publicsipserver:5060
    10:45:40.399 [CM503025]: Call(22): Calling VoIPline:96322440@(Ln.10000@Generic VoIP Provider -)@[Dev:sip:96322511@publicsipserver:5060]
    10:45:40.351 [CM503004]: Call(22): Route 1: VoIPline:96322440@(Ln.10000@Generic VoIP Provider -)@[Dev:sip:96322511@publicsipserver:5060]
    10:45:40.351 [CM503010]: Making route(s) to <sip:2440@3CXIP>
    10:45:40.350 [CM505001]: Ext.2513: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [IPDECT/02.34 (MAC=00087B08421C; SER= 00000; HW=255)] PBX contact: [sip:2513@3CXIP:5060]
    10:45:40.349 [CM503001]: Call(22): Incoming call from Ext.2513 to <sip:2440@3CXIP>
    10:45:33.921 [CM504001]: Ext.2513: new contact is registered. Contact(s): [sip:2513@192.168.11.153:5060/2513]
    10:45:26.690 [CM504002]: Ext.2513: a contact is unregistered. Contact(s): []
    10:45:03.661 [CM504002]: Ext.2513: a contact is unregistered. Contact(s): [sip:2513@192.168.11.122:5060/2513]
    10:45:03.462 [CM504001]: Ext.2513: new contact is registered. Contact(s): [sip:2513@192.168.11.122:5060/2513,sip:2513@192.168.11.188:5060/2513]
    10:44:56.448 [CM504001]: Ext.2513: new contact is registered. Contact(s): [sip:2513@192.168.11.188:5060/2513]
    10:44:37.889 [CM504002]: Ext.2513: a contact is unregistered. Contact(s): []
    10:44:16.636 [CM504001]: Ext.2513: new contact is registered. Contact(s): [sip:2513@192.168.11.148:5060/2513]
    10:44:11.113 [CM504002]: Ext.2513: a contact is unregistered. Contact(s): []
    10:43:13.975 [CM504001]: Ext.2513: new contact is registered. Contact(s): [sip:2513@192.168.11.148:5060/2513]
    10:43:08.107 [CM504002]: Ext.2513: a contact is unregistered. Contact(s): []
    10:42:48.892 [CM504001]: Ext.2513: new contact is registered. Contact(s): [sip:2513@192.168.11.152:5060/2513]
    10:42:43.226 [CM504002]: Ext.2513: a contact is unregistered. Contact(s): []
    10:41:51.364 [CM504001]: Ext.2513: new contact is registered. Contact(s): [sip:2513@192.168.11.154:5060/2513]
    10:41:45.339 [CM504002]: Ext.2513: a contact is unregistered. Contact(s): []
    10:39:52.521 [CM504001]: Ext.2513: new contact is registered. Contact(s): [sip:2513@192.168.11.152:5060/2513]
    10:39:45.757 [CM504002]: Ext.2513: a contact is unregistered. Contact(s): []
    10:39:38.577 [CM503008]: Call(21): Call is terminated
    10:39:34.343 [CM503007]: Call(21): Device joined: sip:96322511@publicsipserver:5060
    10:39:34.342 [CM503007]: Call(21): Device joined: sip:2513@192.168.11.153:5060
    10:39:30.821 [CM505003]: Provider:[Generic VoIP Provider -] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [DanDial] PBX contact: [sip:96322511@3CXIP:5060]
    10:39:30.821 [CM503002]: Call(21): Alerting sip:96322511@publicsipserver:5060
    10:39:29.890 [CM503025]: Call(21): Calling VoIPline:96322440@(Ln.10000@Generic VoIP Provider -)@[Dev:sip:96322511@publicsipserver:5060]
    10:39:29.842 [CM503004]: Call(21): Route 1: VoIPline:96322440@(Ln.10000@Generic VoIP Provider -)@[Dev:sip:96322511@publicsipserver:5060]
    10:39:29.841 [CM503010]: Making route(s) to <sip:2440@3CXIP>
    10:39:29.841 [CM505001]: Ext.2513: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [IPDECT/02.34 (MAC=00087B08421C; SER= 00000; HW=255)] PBX contact: [sip:2513@3CXIP:5060]


    Finally I found out this was caused by out CheckPoint firewall which didn't allowed this direction from one registration to another.

    Sorry to bother you guy - but thanks for your interest, and for confirming that Roaming Dect is working excellent on 3CX

    Br
    Mikkel
     
  8. edgarness

    Joined:
    Jun 27, 2012
    Messages:
    2
    Likes Received:
    0
    what make of DECT system?[​IMG]
     
  9. MNimand

    Joined:
    Jun 26, 2012
    Messages:
    5
    Likes Received:
    0
    The system is a RTX8630
    http://www.rtx.dk/RTX8630-2563.aspx

    But it is only sold through branded companies, e.g. Samsung.
     
  10. KME_RTX

    Joined:
    Oct 5, 2012
    Messages:
    1
    Likes Received:
    0
    If the 3CX server supports multiple SIP registrations on the same account a special setting must be activated in the base station

    The SIP registration should not be moved when the handset is roaming, which firmware version is installed in the base stations?



    Br
    RTX
     
Thread Status:
Not open for further replies.