Bug:? Wrong IP sent in Contact Field

Discussion in '3CX Phone System - General' started by abc123, Apr 9, 2011.

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

    abc123 Active Member

    Joined:
    Nov 9, 2009
    Messages:
    712
    Likes Received:
    1
    We have static ips with 1:1 Nat and so have a dedicated ip and and static port forwarding on our 3cx server. All works correctly.

    In the Networking section we have turned off Stun and put in our public ip. In each voip provider we have also turned off stun and put in our public ip.

    When we register the correct public ip is being sent. But when we send an invite the internal ip is being sent.

    Sidenote: I believe the registration contact ip is picked up from the voip provider settings but the invite contact ip is picked up from the STUN tab in the Network settings.

    Can you confirm this is a bug?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  2. nb

    nb Support Team
    Staff Member 3CX Support

    Joined:
    Jun 7, 2007
    Messages:
    2,127
    Likes Received:
    152
    Can you send a generate support info of this? Or a capture?
    What provider are you using?
    Can you try and restart all the services and try again (could be a cache problem where changes were made on the fly and the pbx kept on sending that internal address in the contact.)
    What provider are you using?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. abc123

    abc123 Active Member

    Joined:
    Nov 9, 2009
    Messages:
    712
    Likes Received:
    1
    Sorry for the delay in reply.

    The problem fixed itself.

    We had 3 providers - 2 broadvox and our own sip service we are launching. All 3 did the same. I restarted services with no change, rebooted the server with no change then (possibly on next registration) about 40ish minutes later it changed.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
Thread Status:
Not open for further replies.