Bria multiple registrations because net topology changes

Discussion in '3CX Phone System - General' started by carolinainnovative, Jul 21, 2010.

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

    Joined:
    May 4, 2009
    Messages:
    369
    Likes Received:
    6
    Running V9 RC2 on Server 2008 -

    One of my extensions is showing as "available" when there is nothing registered...

    Before someone says "you were hacked" (which was one thought that crossed my mind), I checked the Phones tab - and saw it listed several old registrations from the day before (recognized the IP addy from where I was yesterday) and several registered from IP address 0.0.0.0:5060 - including one for extension 100.

    3CX Assistant also shows this ext as available as well, but calling said extension reveals the truth - it is not registered, and 3cx even knows it isn't registered per the logs.

    Code:
    10:06:36.221  [CM503016]: Call(10): Attempt to reach <sip:100@xxxxxx.net> failed. Reason: Not Registered
    10:06:36.220  [CM503017]: Call(10): Target is not registered: Ext:Ext.100
    10:06:36.194  [CM503010]: Making route(s) to <sip:100@xxxxxx.net>
    Thoughts?
     
  2. MichaelB

    MichaelB Member
    3CX Support

    Joined:
    Aug 25, 2009
    Messages:
    401
    Likes Received:
    3
    Re: Possible extension availability bug in RC2?

    Hi, what phone where you using at that moment.
    Also can you send us full logs by any chance.
    Send them to mb@3cx.com
    Thanks and regards.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. carolinainnovative

    Joined:
    May 4, 2009
    Messages:
    369
    Likes Received:
    6
    Re: Possible extension availability bug in RC2?

    Phone - Counterpath bria
    Logs - will do
     
  4. nb

    nb Support Team
    Staff Member 3CX Support

    Joined:
    Jun 7, 2007
    Messages:
    2,110
    Likes Received:
    143
    Re: Possible extension availability bug in RC2?

    Yes - this shows that your phone is behind an unreliable internet connection which is disconnecting link between phone and pbx or phone is freezing and crashing.

    Multiple registration will cause unreliable audio. Because the PBX thinks it has numerous valid contacts for that phone.

    To work around this, set the registration time as low as you can so at least the registrations will expire quickly not in an hour.

    If you disconnect 10 times in 1 hour, you get 10 registrations that each expire in 1 hour each.

    We do not need to see logs for this. If you see multiple registration entries it means that the problem is at phone end
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. carolinainnovative

    Joined:
    May 4, 2009
    Messages:
    369
    Likes Received:
    6
    Re: Possible extension availability bug in RC2?

    Nicky - that doesn't make any sense - seriously. Its been over 24 hours and those registrations are still there. And what of the 0.0.0.0 registrations? It doesn't matter how low I set the re-registration timer - these registrations don't go away.
     
  6. nb

    nb Support Team
    Staff Member 3CX Support

    Joined:
    Jun 7, 2007
    Messages:
    2,110
    Likes Received:
    143
    To me it does not make sense either. You know that a 0.0.0.0 is not normal.
    Then why are you trying to find a bug in 3CX? When the registration attempt is not normal or has something abnormal?

    If it is a local extension, you should see the local address there.
    If it is a remote extension you should see the public address of the remote end
    if it is a tunnel connection you should see 127.0.0.1

    0.0.0.0 means what exactly? Register - contact 0.0.0.0. What should the server do at this point? Send sip to all of its local interfaces? Any on the local machine? This is an illegal contact.

    You should troubleshoot in that direction. The phone is configured incorrectly or it is not behaving accordingly. Try with Xlite and Eyebeam or another phone. See if this occurs. If it does then you have to start seeing what is in between the 3CX and these remote extensions.

    Restart the configuration service to clear all persistent storage and start again. This should clear all these dirty stale registrations.

    Then start wireshark again and send a wireshark capture of this registration request.

    Yes registration time is not the problem here. But now I realized about this contact 0.0.0.0. This should be the emphasis of the post.

    ===

    Now if the pbx does not clear this dirty registration on its own then this is another story - If you send me a register packet showing this, then I can try to reproduce it here.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  7. carolinainnovative

    Joined:
    May 4, 2009
    Messages:
    369
    Likes Received:
    6
    I just have to figure out how to reproduce that dirty registration...
     
  8. nb

    nb Support Team
    Staff Member 3CX Support

    Joined:
    Jun 7, 2007
    Messages:
    2,110
    Likes Received:
    143
    Yes do so. When you do I will need to have a capture of the phone and capture taken from the server. I have a hunch that this is some bug in the phone or you are using some buggy version of it.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
Thread Status:
Not open for further replies.