• V20: 3CX Re-engineered. Get V20 for increased security, better call management, a new admin console and Windows softphone. Learn More.

Remote Extension Not Ringing

Status
Not open for further replies.

trinican

Joined
Nov 26, 2012
Messages
4
Reaction score
0
I am new to 3CX and so far I think it is an amazing product. Here is my environment. I have set up a remote extension using a Linksys PAP2 ATA. The remote extension is fully registered with the 3CX system and can originate calls to all other extensions. The problem is that when called from an extension directly off the 3CX system, the phone at the remote end does not ring and the call eventually goes to the voice mail system.

The 3CX system log shows it as a normal call with no answer from the remote side.

Does anyone have any answers or suggestions ?

Regards
 
trinican said:
Does anyone have any answers or suggestions ?

I would suspect one (or a combination) of three possible reasons...

The ATA is registering with the incorrect (local?) IP, and cannot be reached. 3CX log of a call attempt will show what is happening.
The router at the remote end is blocking the call attempt for some reason.
The local port, that the ATA is using (5060?), is already being used by another device on the same network.



Post the 3CX log of a call attempt, what type of router are you using a the remote end ,is this an office where a proxy server is employed? Are there any other SIP devices in use at the remote location?
 
under the extensions tab--->other--->pbx delivers audio, is the box unchecked if so try to check the box and attempt a call.
 
Keep alives is not turned on.

So the ATA registers with a public ip and port (from stun) and an entry is made in the nat table at the remote firewall/modem.

But this only lasts a few minutes and is dropped. So when you then make the invite from 3cx to the remote location the firewall cannot look up the internal ip from the nat table as it has expired. So you need to turn on keep alives on the pap2t
 
Thanks everyone for your responses.. I will try the suggestions and post the outcome tomorrow. Best Regards, Carl
 
I tried all the suggestions posted so far without any luck. Here is the server log of a failed called. Extension 103 is the originator station on the 3CX system directly and is calling remote extension 101 (PAP2 ATA) located on a different network. Does anyone know what error code 401 - Unauthorized/Invite from 207.164.79.1:55290 means in terms of adapter configuration ?

28-Nov-2012 19:34:40.566 Leg L:7.1[Extn] is terminated: Cause: BYE from PBX
28-Nov-2012 19:34:40.541 [CM503020]: Call(C:7): Normal call termination. Call originator: Extn:103. Reason: Terminated
28-Nov-2012 19:34:40.541 L:7.1[Extn] failed to reach Extn:101, reason Not Acceptable HereReason Unknown
28-Nov-2012 19:34:40.541 Leg L:7.2[Extn] is terminated: Cause: 401 Unauthorized/INVITE from 207.164.79.1:55290
28-Nov-2012 19:34:40.541 Call to T:Extn:101@[Dev:sip:[email protected]:55290] from L:7.1[Extn] failed, cause: Cause: 401 Unauthorized/INVITE from 207.164.79.1:55290
28-Nov-2012 19:34:40.540 [CM503003]: Call(C:7): Call to <sip:[email protected]:5060> has failed; Cause: 401 Unauthorized/INVITE from 207.164.79.1:55290
28-Nov-2012 19:34:39.327 [CM503025]: Call(C:7): Calling T:Extn:101@[Dev:sip:[email protected]:55290] for L:7.1[Extn]
28-Nov-2012 19:34:39.138 [CM503027]: Call(C:7): From: Extn:103 ("PC" <sip:[email protected]:5060>) to T:Extn:101@[Dev:sip:[email protected]:55290]
28-Nov-2012 19:34:39.138 [CM503004]: Call(C:7): Route 1: from L:7.1[Extn] to T:Extn:101@[Dev:sip:[email protected]:55290]
28-Nov-2012 19:34:39.132 [CM503001]: Call(C:7): Incoming call from Extn:103 to <sip:[email protected]:5060>
28-Nov-2012 19:34:39.123 NAT/ALG check:L:7.1[Extn] REQUEST 'INVITE' - basic check passed. No information for extended checks
 
Thanks Leejor. The ip 24.246.68.217 is the public IP address of the 3CX system (Local LAN address 192.168.1.4) and the address 207.164.79.1 is the public IP address of the remote extension (Local LAN address 192.168.1.100 system extension 101).

STUN is turned ON and there is no double NATing here.

The saga continues !!!
 
trinican said:
Thanks Leejor. The ip 24.246.68.217 is the public IP address of the 3CX system (Local LAN address 192.168.1.4) and the address 207.164.79.1 is the public IP address of the remote extension (Local LAN address 192.168.1.100 system extension 101).

STUN is turned ON and there is no double NATing here.

The saga continues !!!

It would appear something is intercepting the invite to the PAP and rejecting it - 401 Not Authorized. That is a very specific sip message, so something that end knows sip.

So either you have something on your firewall/router that handles sip, or has sip alg turned on (Turn it off) or you have a weird setting on your PAP that wants authentication for inbound calls too.

Check the firewall/router and also the PAP. Let us know models of firewalls and any PAP settings too.
 
What make/model router is located at the remote end? Is it one the you have access to it (options)?
 
Status
Not open for further replies.

Getting Started - Admin

Latest Posts

Forum statistics

Threads
141,632
Messages
748,964
Members
144,750
Latest member
TECHXNEPAL
Get 3CX - Absolutely Free!

Link up your team and customers Phone System Live Chat Video Conferencing

Hosted or Self-managed. Up to 10 users free forever. No credit card. Try risk free.

3CX
A 3CX Account with that email already exists. You will be redirected to the Customer Portal to sign in or reset your password if you've forgotten it.