can't get my phones to dial out via patton gateway

[asinshesq]

Hi. I'm new to 3cx and to voip more generally so I am probably doing something stupid. Here's the story:

1. I have two yealink voip phones on my lan and they can call one another through 3cx.

2. I am trying to add a patton 4112 gateway (with two fxo ports) to the system in order to allow my phones to dial via my analog phone service.

3. I gave the patton 4112 a static ip on my lan and 3cx can communicate with it.

4. I used the add PSTN gateway button on 3cx to add the patton 4112 to my system and I then took the config file 3cx generated and uploaded that to the patton 4112...that all seemed to go well.

5. During the process of adding the gateway I created an outbound rule saying use the gateway if the number starts with 9 (and I had it strip one digit so it wouldn't send the 9 out to my phone service).

But when I try dialing 9 and a number on my voip phones it fails and the phone displays a message saying it encountered a server error.

Note that I only have one outside line so I only have a rj11 cable going from fx0 0/0 to the phone line (nothing from fxo 0/1). After this failed, I tried disabling port fxo 0/1 but that didn't help either.

I looked into the log and it looks like I'm getting most of the way there but something goes wrong. Here's the log of a call:

18-Apr-2014 18:46:16.934 Leg L:8.1[Extn] is terminated: Cause: BYE from PBX
18-Apr-2014 18:46:16.881 Leg L:8.3[Line:10000>>12125673738] is terminated: Cause: 502 Bad Gateway/INVITE from 192.168.1.202:5062
18-Apr-2014 18:46:16.881 [CM503020]: Call(C:8): Normal call termination. Call originator: Extn:10. Reason: Server Failure
18-Apr-2014 18:46:16.881 L:8.1[Extn] failed to reach Line:10000>>12125583738, reason Server Failure
18-Apr-2014 18:46:16.881 Call to T:Line:10000>>12125673738@[Dev:sip:[email protected]:5062] from L:8.1[Extn] failed, cause: Cause: 502 Bad Gateway/INVITE from 192.168.1.202:5062
18-Apr-2014 18:46:16.880 [CM503003]: Call(C:8): Call to <sip:[email protected]:5062> has failed; Cause: 502 Bad Gateway/INVITE from 192.168.1.202:5062
18-Apr-2014 18:46:16.661 Leg L:8.2[Line:10000>>12125673738] is terminated: Cause: 487 Request Terminated/INVITE from 192.168.1.202:5060
18-Apr-2014 18:46:16.661 [CM503025]: Call(C:8): Calling T:Line:10000>>12125673738@[Dev:sip:[email protected]:5062] for L:8.1[Extn]
18-Apr-2014 18:46:16.654 Call to T:Line:10000>>12125673738@[Dev:sip:[email protected]:5060,Dev:sip:[email protected]:5062] from L:8.1[Extn] failed, cause: Cause: 487 Request Terminated/INVITE from 192.168.1.202:5060
18-Apr-2014 18:46:16.654 [CM503003]: Call(C:8): Call to <sip:[email protected]:5060> has failed; Cause: 487 Request Terminated/INVITE from 192.168.1.202:5060
18-Apr-2014 18:46:15.339 [CM503025]: Call(C:8): Calling T:Line:10000>>12125673738@[Dev:sip:[email protected]:5060,Dev:sip:[email protected]:5062] for L:8.1[Extn]
18-Apr-2014 18:46:15.293 [CM503027]: Call(C:8): From: Extn:10 ("Kitchen" <sip:[email protected]:5060>) to T:Line:10000>>12125673738@[Dev:sip:[email protected]:5060,Dev:sip:[email protected]:5062]
18-Apr-2014 18:46:15.293 [CM503004]: Call(C:8): Route 1: from L:8.1[Extn] to T:Line:10000>>12125673738@[Dev:sip:[email protected]:5060,Dev:sip:[email protected]:5062]
18-Apr-2014 18:46:15.293 Line limit check: Current # of calls for line Lc:10001(@PSTN Gateway (patton 4112)[<sip:[email protected]:5062>]) is 0; limit is 1
18-Apr-2014 18:46:15.293 Line limit check: Current # of calls for line Lc:10000(@PSTN Gateway (patton 4112)[<sip:[email protected]:5060>]) is 0; limit is 1
18-Apr-2014 18:46:15.293 Call(C:8): Call from Extn:10 to 912125673738 matches outbound rule 'Rule for PSTN Gateway (patton 4112)'
18-Apr-2014 18:46:15.291 [CM503001]: Call(C:8): Incoming call from Extn:10 to <sip:[email protected]:5060>

Any suggestions? Thanks!

 

[asinshesq]

Here's another data point: Incoming calls route through the gateway to the phones perfectly so at least that part of things is working. I also note from the log above that the final entry before termination is a 502 bad gateway. What's that telling me...is the patton defective?

 

[bardissi]

I ran into this exact same issue this week.

Go to the patton website and download the newest firmware for the patton.

Then go to the web console and upload it and reboot.
(you dont need to unzip)

That will fix it.

 

[asinshesq]

Thanks. That seemed like the answer, but I downloaded the march 2014 version of the firmware, uploaded it to the patton 4112, let it rebbot and then tried it again and same result: incoming calls get routed fine but when I dial an outgoing call using my '9' outgoing rule the phone says I encountered a server error and the log says 502 bad gateway. Any other thoughts? Is this likely to be my configuration or bad hardware?

Here's the latest log for when I try to dial out (I think it's the same as before but just in case...):

18-Apr-2014 21:03:43.558 Leg L:21.1[Extn] is terminated: Cause: BYE from PBX
18-Apr-2014 21:03:43.505 Leg L:21.3[Line:10000>>13141231234] is terminated: Cause: 502 Bad Gateway/INVITE from 192.168.1.202:5062
18-Apr-2014 21:03:43.505 [CM503020]: Call(C:21): Normal call termination. Call originator: Extn:10. Reason: Server Failure
18-Apr-2014 21:03:43.505 L:21.1[Extn] failed to reach Line:10000>>13141231234, reason Server Failure
18-Apr-2014 21:03:43.505 Call to T:Line:10000>>13141231234@[Dev:sip:[email protected]:5062] from L:21.1[Extn] failed, cause: Cause: 502 Bad Gateway/INVITE from 192.168.1.202:5062
18-Apr-2014 21:03:43.504 [CM503003]: Call(C:21): Call to <sip:[email protected]:5062> has failed; Cause: 502 Bad Gateway/INVITE from 192.168.1.202:5062
18-Apr-2014 21:03:43.287 Leg L:21.2[Line:10000>>13141231234] is terminated: Cause: 487 Request Terminated/INVITE from 192.168.1.202:5060
18-Apr-2014 21:03:43.287 [CM503025]: Call(C:21): Calling T:Line:10000>>13141231234@[Dev:sip:[email protected]:5062] for L:21.1[Extn]
18-Apr-2014 21:03:43.274 Call to T:Line:10000>>13141231234@[Dev:sip:[email protected]:5060,Dev:sip:[email protected]:5062] from L:21.1[Extn] failed, cause: Cause: 487 Request Terminated/INVITE from 192.168.1.202:5060
18-Apr-2014 21:03:43.274 [CM503003]: Call(C:21): Call to <sip:[email protected]:5060> has failed; Cause: 487 Request Terminated/INVITE from 192.168.1.202:5060
18-Apr-2014 21:03:41.974 [CM503025]: Call(C:21): Calling T:Line:10000>>13141231234@[Dev:sip:[email protected]:5060,Dev:sip:[email protected]:5062] for L:21.1[Extn]
18-Apr-2014 21:03:41.926 [CM503027]: Call(C:21): From: Extn:10 ("Kitchen" <sip:[email protected]:5060>) to T:Line:10000>>13141231234@[Dev:sip:[email protected]:5060,Dev:sip:[email protected]:5062]
18-Apr-2014 21:03:41.926 [CM503004]: Call(C:21): Route 1: from L:21.1[Extn] to T:Line:10000>>13141231234@[Dev:sip:[email protected]:5060,Dev:sip:[email protected]:5062]
18-Apr-2014 21:03:41.926 Line limit check: Current # of calls for line Lc:10001(@PSTN Gateway (patton 4112)[<sip:[email protected]:5062>]) is 0; limit is 1
18-Apr-2014 21:03:41.926 Line limit check: Current # of calls for line Lc:10000(@PSTN Gateway (patton 4112)[<sip:[email protected]:5060>]) is 0; limit is 1
18-Apr-2014 21:03:41.926 Call(C:21): Call from Extn:10 to 913141231234 matches outbound rule 'Rule for PSTN Gateway (patton 4112)'
18-Apr-2014 21:03:41.923 [CM503001]: Call(C:21): Incoming call from Extn:10 to <sip:[email protected]:5060>

 

[bardissi]

re download your config from 3cx and re upload and reboot

 

[asinshesq]

Thanks again! But after I did that the gateway no longer shows up as registered when I click ports/trunks, and neither inbound nor outbound works. Must be missing something simple...

 

[asinshesq]

And, I see the gateway is getting blacklisted for too many failed authentications, which suggests that the credentials don't match. But I left all passwords and other parameters as the defaults when I generated the config file so I would have thought that the 3cx and the 4112 authenticaion details would match. And when I go into the patton reports area and look at startup config I see the same username and password for the ports that I have in the 3cx so things should match. What am I missing now?

 

[asinshesq]

I continue to have the authentication problem. It occurred to me that I could whitelist the ip for the gateway to see if that would work as a temporary fix, so I went into the security blacklist place (it does not say whitelist/blacklist) and I added an entry for allow that ip. I then rebooted and it still didn't work, and when I went back to the security blacklist place I see that allow has been turned back to deny.

Any ideas for fixing the authentication issue or creating a more durable whitelist entry?

 

[bardissi]

delete the gateway out of the 3cx and start from scratch.

go through the wizard and reimport into patton

 

[asinshesq]

Right, I've done that multiple times. I even did a factory reset and re-configure / re-import, but the same result each time. Some bad setting seems to survive the gateway deletion in 3cx and new configuration in the gateway. Really odd.

 

[asinshesq]

Ok, partial success (at least I got back to where I was). It turns out that I flashed to patton 4112 firmware that was too recent. The March 5, 2014 version does not register with 3cx but I flashed back to the January 9, 2015 version and it registers fine. Incoming calls now get routed to my voip phones perfectly (as they did at the beginning of this process). But, I still can't dial out. When I try, the phone gives a message of temporarily unavailable and the server activity log reads as follows:

20-Apr-2014 07:01:49.056 Leg L:6.1[Extn] is terminated: Cause: BYE from PBX
20-Apr-2014 07:01:49.022 [CM503020]: Call(C:6): Normal call termination. Call originator: Extn:10. Reason: Not available
20-Apr-2014 07:01:49.022 L:6.1[Extn] failed to reach Out#:>>Rule{Rule for PSTN Gateway (Patton 4112)}>>913214268797, reason Not Registered
20-Apr-2014 07:01:49.018 [CM503017]: Call(C:6): Target is not registered: Out#:>>Rule{Rule for PSTN Gateway (Patton 4112)}>>913214268797
20-Apr-2014 07:01:49.018 Call(C:6): Call from Extn:10 to 913214268797 matches outbound rule 'Rule for PSTN Gateway (Patton 4112)'
20-Apr-2014 07:01:49.016 [CM503001]: Call(C:6): Incoming call from Extn:10 to <sip:[email protected]:5060>

The log claims the target is not registered, but when I click 'ports/trunks status' it reports that both virtual ports for this gateway are registered (and if they were not registered why would I be receiving incoming calls via the gateway). Any further suggestions?

 

[bardissi]

You could always try to downgrade to an even older firmware to see what happens.

 

[asinshesq]

Will try, but won't be at the location with this equipment for another few weeks. You had said earlier you had the same issue and fixed it by upgrading to more recent firmware than the one you originally had. Any chance you know which version worked for you?

 

[bardissi]

SmartWare 6.5 Build Series 2014-03-05

FYI Patton does offer free support if you want to do down that route

http://www.patton.com/support/

 

[asinshesq]

Just to close this out, the problem was that the patton was ip blacklisted in 3cx. I knew the patton was showing up on the blacklist and kept deleting it from the blacklist, but what I didn't know is that when you delete an entry from the blacklist you need to scroll down and click the ok button. Even though the entry seems to disappear from the blacklist without doing that, the deletion doesn't actually take effect unless you click the ok button.

Patton support was great...they used team viewer and putty to directly access my pc and troubleshoot, and they were the ones that told me the ip blacklist trick.

 

[leejor]

I had a couple of ATA's that, for some reason, would get themselves on the IP Blacklist every so often. I put the entire local IP range (of VoIP devices) on the "whitelist", as I trust all internal devices. This way, in the security settings, you can lower the number of failed authentications it takes before being IP blacklisted, for external devices (hack attempts), yet keep internal devices from ending up on the list.