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.

Using Grandstream GXP2100 as an external extension - Help!

Discussion in '3CX Phone System - General' started by nilu, Jun 16, 2011.

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

    Joined:
    Apr 2, 2008
    Messages:
    3
    Likes Received:
    0
    I'm having a lot of problems setting up the Granstream GXP2100 as an external extension (without using a local Proxy Server). The phone is not even registering.

    If anyone has got this phone or similar working, would they be kind enough to post the config settings.

    I've used the blog guide "Configuring External Extensions with 3CX PhoneSystem" for the basic config but there are still a lot of obscure (to me) settings that I may have not set or misconfigured!

    Running latest firmware for the Grandstream (v1.0.1.66) and the 3CX running fine at external location.

    Using Draytek 2820 routers at both ends. Mapping etc believed to be correct on 3CX side. No special mapping at Grandstream end. Fixed IP addresses at both locations.

    Sorry, know it's a lot to ask but sure someone has it working - "Kevin" who wrote the blog must have done ;)

    Thanks
    Nilu Pattnaik
    London, UK
     
  2. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    11,127
    Likes Received:
    330
    Re: Using Grandstream GXP2100 as an external extension - Hel

    But, is a registration attempt showing up in the 3CX server log? If it does, then what does it show? Any clues?

    If it doesn't, then first run the 3CX firewall checker and make sure that all that passes. If all tests do pass, then I would suspect that the phone is not "pointed" to the correct IP / port.

    Get the registration working first, then, deal with any audio issues that may crop up.
     
  3. nilu

    Joined:
    Apr 2, 2008
    Messages:
    3
    Likes Received:
    0
    Re: Using Grandstream GXP2100 as an external extension - Hel

    Unfortunately, I haven’t got the phone to register yet!

    I’m pretty sure that is talking to the 3CX system (see log below), however, it doesn’t show up in the 3CX log (even in verbose mode).... which is worrying!

    These were the basic Grandstream settings I was interested in my original post, to get it to subscribe.
    Can’t deal with the other issues until that happens.

    I am trying to find a Grandstream document on the log format shown below. Hope I’ve interpreted it correctly.

    Any suggestions please or recommended settings for the GXP2100 in this configuration.

    Thanks
    Nilu

    ----------------------------------------------------------------------------------

    LOG FROM GRANSTREAM GXP2100

    GXP2100
    Internal – 192.168.1.228
    Public – 94.195.194.xxx

    3CX v10
    Internal – 192.168.1.4
    Public – 195.137.0.yyy

    06-18-2011 15:02:39 Local7.Debug
    192.168.1.228 GXP2100_PHONE:[00:0b:82:2b:26:70][1.0.1.66]
    SIPStack::snd_message: Sending message:REGISTER sip:195.137.0.yyy SIP/2.0 Via: SIP/2.0/UDP 94.195.194.xxx:52420;branch=z9hG4bK866183570;rport From: <sip:228@195.137.0.yyy>;tag=110592672 To: <sip:228@195.137.0 (log didn’t complete)


    06-18-2011 15:02:40 Local7.Debug
    192.168.1.228 GXP2100_PHONE:[00:0b:82:2b:26:70][1.0.1.66]
    SIPStack::receiveMessage: Received message: (273)SIP/2.0 400 Bad Request Via: SIP/2.0/UDP 94.195.194.xxx:52420;branch=z9hG4bK866183570;rport=52420 From: <sip:228@195.137.0.yyy>;tag=110592672 To: <sip:228@195. (log didn’t complete)
     
  4. GSsupport

    Joined:
    Jan 31, 2011
    Messages:
    17
    Likes Received:
    0
    Re: Using Grandstream GXP2100 as an external extension - Hel

    Hi Nilu,

    Can you please tell us how you are resolving NAT? (STUN, port forwarding)

    You can also open a ticket to Grandstream to get more assistance
    http://www.grandstream.com/support/submit-a-ticket

    Best regards,
     
Thread Status:
Not open for further replies.