Re-registering itself a few times a minute?

Discussion in 'Windows' started by Pentangle, Dec 13, 2007.

  1. Pentangle

    Pentangle Member

    Joined:
    Dec 6, 2007
    Messages:
    261
    Likes Received:
    0
    Hi,

    This new client appears to be losing the server and re-registering itself sometimes several times a minute.

    For instance:

    14:00:38.171 ExtnCfg::updateContact [CM504001]: Ext.1001: new contact is registered. Contact(s): [sip:1001@192.168.20.108:5070;rinstance=03310518a808fc19]
    14:00:38.046 ExtnCfg::updateContact [CM504002]: Ext.1001: a contact is unregistered. Contact(s): []
    14:00:21.203 ExtnCfg::updateContact [CM504002]: Ext.1001: a contact is unregistered. Contact(s): []
    13:58:57.625 FaxCfg::updateContact [CM504008]: Fax Service: registered as sip:888@3CXPhoneSystem with contact sip:888@169.254.216.115:5100;user=phone
    13:58:57.031 FaxCfg::updateContact [CM504010]: Fax Service: unregistered contact sip:888:5100;user=phone
    13:58:36.953 ExtnCfg::updateContact [CM504001]: Ext.1001: new contact is registered. Contact(s): [sip:1001@192.168.20.108:5070;rinstance=d82d843f940bff01]
    13:58:36.828 ExtnCfg::updateContact [CM504002]: Ext.1001: a contact is unregistered. Contact(s): []
    13:56:36.000 ExtnCfg::updateContact [CM504001]: Ext.1001: new contact is registered. Contact(s): [sip:1001@192.168.20.108:5070;rinstance=7115f41254677938]
    13:56:35.890 ExtnCfg::updateContact [CM504002]: Ext.1001: a contact is unregistered. Contact(s): []


    (also I have no idea why the fax service has registered itself against an APIPA address in the middle of that log, but that's a question for another time!)
     
  2. Costas3CX

    Costas3CX New Member

    Joined:
    Jan 23, 2007
    Messages:
    217
    Likes Received:
    0
    Hello there

    It is actually hardcoded to re-register every 2 minutes. We are going to create a parameter to have this registration period user defined very soon though.
     
  3. Pentangle

    Pentangle Member

    Joined:
    Dec 6, 2007
    Messages:
    261
    Likes Received:
    0
    OK - why though? because currently it looks like it's de-registering itself first, which means my client has a (small) period of non-connectivity.

    Should it not check to see whether it's registered before it tries registering?, and surely it shouldn't de-register itself unless the client's not in use? (otherwise you might drop a call?)
     

Share This Page