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.

Remote extension not working

Discussion in '3CX Phone System - General' started by asmith3006, Aug 28, 2016.

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

    Joined:
    Mar 5, 2014
    Messages:
    94
    Likes Received:
    5
    I have a remote extension connected using a direct connection (i.e. not via SBC). I have a different connection which works correctly in another employee's house so I'm fairly certain the port forwarding is correct.

    When I try and dial a number from the extension (6134 on a Yealink W52) I get the following:
    Code:
    28-Aug-2016 14:41:40.263   Leg L:6703.1[Unknown:] is terminated: Cause: BYE from PBX
    28-Aug-2016 14:41:40.212   [CM502001]: Source info: From: "Name"<sip:6134@pbx.mydomain.com>;tag=3292667732; To: <sip:*888@pbx.mydomain.com>
    28-Aug-2016 14:41:40.212   [CM503013]: Call(C:6703): Incoming call rejected, caller is unknown; msg=Ivite-IN Recv Req INVITE from my.home.ip.address:5065 tid=1259108282 Call-ID=1410111468@192.168.10.100:
    INVITE sip:*888@pbx.mydomain.com:5060 SIP/2.0
    Via: SIP/2.0/UDP my.home.ip.address:5065;rport=5065;branch=z9hG4bK1259108282
    Max-Forwards: 70
    Contact: <sip:6134@my.home.ip.address:5065>
    To: <sip:*888@pbx.mydomain.com>
    From: "Name"<sip:6134@pbx.mydomain.com>;tag=3292667732
    Call-ID: 1410111468@192.168.10.100
    CSeq: 2 INVITE
    Expires: 360
    Allow: INVITE, INFO, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, REFER, PUBLISH, UPDATE, MESSAGE
    Content-Type: application/sdp
    Proxy-Authorization: Digest username="6134",realm="3CXPhoneSystem",nonce="414d535c0dd37b1452:733ad725b8d8feb0ad239ca46a39a86b",uri="sip:*888@pbx.mydomain.com:5060",response="bbcdae8f2a3ec4296e20ce0f5d6604b5",algorithm=MD5
    Supported: replaces
    User-Agent: Yealink SIP-W52P 25.73.23.1
    Allow-Events: talk, hold, conference, refer, check-sync
    Content-Length: 306
    The reverse works correctly, if I ring the extension from a phone on the PBX then my remote extension rings and voice works as expected.

    What am I missing?

    Thanks
     
  2. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    11,117
    Likes Received:
    329
    Does my.home.ip.address equal your home public IP, or the private IP of the set?

    Do you have any options set, in the 3CX extension settings (that extension) that would prevent the call?
     
  3. asmith3006

    Joined:
    Mar 5, 2014
    Messages:
    94
    Likes Received:
    5
    Yes, my.home.ip.address relates to the public IP. The LAN address appears a couple of times (192.168.10.100), this is a different range to the main office too so there's no subnet overlap.

    I can't see any options blocking it, I've compared it against a working extension (a different user's home) and they're the same. Do you have anything specific in mind I should check?
     
  4. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    11,117
    Likes Received:
    329
    I question why the local LAN IP , of the set, would appear. That may be throwing things off (the caller is unknown log) As far as 3CX is concerned, the set should be located at publicIP:port. There may be a STUN setting on the set that needs to be tweaked.

    .

    Is the working set, the same type(make/model)? Compare a registration log from both sets...what fields are different.
     
Thread Status:
Not open for further replies.