Remote extension not working

Status
Not open for further replies.

asmith3006

Joined
Mar 5, 2014
Messages
94
Reaction score
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:[email protected]>;tag=3292667732; To: <sip:*[email protected]>
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 [email protected]:
INVITE sip:*[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP my.home.ip.address:5065;rport=5065;branch=z9hG4bK1259108282
Max-Forwards: 70
Contact: <sip:[email protected]:5065>
To: <sip:*[email protected]>
From: "Name"<sip:[email protected]>;tag=3292667732
Call-ID: [email protected]
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:*[email protected]: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
 
asmith3006 said:

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?
 
leejor said:
asmith3006 said:

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?
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?
 
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.

asmith3006 said:
I have a different connection which works correctly in another employee's house so I'm fairly certain the port forwarding is correct.
.

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

Forum statistics

Threads
111,851
Messages
589,359
Members
164,685
Latest member
Concorde