Internode (Nodephone) questiton

Discussion in '3CX Phone System - General' started by pearsondan99, Nov 29, 2007.

  1. pearsondan99

    Joined:
    Nov 4, 2007
    Messages:
    18
    Likes Received:
    0
    I m a complete newbie at 3cx so please excuse my ignorance

    I m having a few dramas getting nodephone working with 3cx, I ve put the required firewall rules in for SIP on my netscreen, configured using my account details provided from internode but no joy! line status is still red, this is an extract from the log hopefull may shed some light, would love to hear from anyone who has nodephone up and running and may have some ideas cheers,

    22:08:32.328 ExtLine::Register [CM010002] Line DN='10001' device='Internode' can not be registered. External IP isn't resolved.
    22:08:32.328 ExtLine::Register [CM110001] Use External IP for device line registration DN='10001' device='Internode'
    22:08:32.031 CallMgr::failResolveExtIp [CM200001] Failed to resolve external IP!
    22:08:32.031 StunClient::process [CM215001] STUN failed to resolve external IP using server 64.69.76.23
    22:08:29.015 StunClient::process [CM215001] STUN failed to resolve external IP using server 64.69.76.23
    22:08:25.984 StunClient::process [CM115001] Send initial STUN request to 64.69.76.23
    22:08:25.875 StunClient::process [CM215001] STUN failed to resolve external IP using server 64.69.76.23
    22:08:22.859 StunClient::process [CM215001] STUN failed to resolve external IP using server 64.69.76.23
    22:08:19.828 StunClient::process [CM115001] Send initial STUN request to 64.69.76.23
    22:08:19.734 StunClient::process [CM215001] STUN failed to resolve external IP using server 64.69.76.23
    22:08:16.703 StunClient::process [CM215001] STUN failed to resolve external IP using server 64.69.76.23
    22:08:13.671 StunClient::process [CM115001] Send initial STUN request to 64.69.76.23
    22:08:13.578 StunClient::process [CM215001] STUN failed to resolve external IP using server 64.69.76.23
    22:08:10.546 StunClient::process [CM215001] STUN failed to resolve external IP using server 64.69.76.23
    22:08:07.531 StunClient::process [CM115001] Send initial STUN request to 64.69.76.23
    22:02:24.203 ServRegs::eek:nAdd [CM113002] Registered: Ext.100
     
  2. ecwilson

    ecwilson New Member

    Joined:
    Jul 12, 2007
    Messages:
    118
    Likes Received:
    0
    Is your 3CX box behind some type of fire wall???
    Does your box have a public or private ip???

    ecwilson
     
  3. archie

    archie Well-Known Member
    3CX Staff

    Joined:
    Aug 18, 2006
    Messages:
    1,309
    Likes Received:
    0
    Try to use different STUN servers. The one you're using might be down at that time. It happens sometime.
     
  4. ecwilson

    ecwilson New Member

    Joined:
    Jul 12, 2007
    Messages:
    118
    Likes Received:
    0
    Here is a list of stun server you can use.

    64.69.76.23 & 24 - location us

    69.90.168.13 & 14 - location us

    ecwilson
     
  5. pearsondan99

    Joined:
    Nov 4, 2007
    Messages:
    18
    Likes Received:
    0
    Ok dumb question what part do the STUN servers play in the IP tel solution?

    BTW my 3cx server is behind a firewall (which has a rule created for SIP on 5060) I can see traffic leaving the firewall but nothing coming back, yes the rule is inbound & outbound

    Thanks for your help guys!
     
  6. MajoR_Mess

    Joined:
    Dec 4, 2007
    Messages:
    11
    Likes Received:
    0
    Basically, a STUN server replies with the ip address Internode gave your modem when it connected. The STUN server is also supposed to work out what type of NAT you are running as well.
     

Share This Page