No outbound calls on Patton 4114

Status
Not open for further replies.

optimus1337

Customer
Advanced Certified
Joined
Dec 19, 2015
Messages
6
Reaction score
0
I was having an issue with my phones taking up to 15 seconds before it would actually start to ring, in my frustration I decided to remove the PSTN gateway and start over on that front. What I have ended up with is the ability to receive calls but not make them.

The event log in 3CX only shows Call or Registration to #######@(Ln.90001@Patton SN4114/JO/EUI) has failed. [ V4 192.168.70.31:5060 UDP target domain=unspecified mFlowKey=1032 ] replied: 504 Server Time-out; from IP:192.168.70.31:5060.

Iv'e updated both 3CX and the Patton box to the latest software\firmware available, I've created and recreated the gateway in 3CX multiple times. My outbound rule is pretty simple, all calls on any extensions are allowed to go out.

Any help would be appreciated!
 
In your previous posts, the gateway was using IP 192.168.1.5

Calling T:Line:90001>>4507630325@[Dev:sip:[email protected]:5061]

I don't see that IP in this log. Where is the call routing?

That destination (IP) should be in the Trunk settings in 3CX. If its isn't going to the correct destination, there will never be a reply, hence the time-out.
 
Thanks for your reply.

I'm not sure what previous posts you are talking about, Iv'e only ever posted on these boards one other time and it was in someone else's thread regarding the slow outgoing calls and I didn't provide an IP. The IP given in my log is the correct one for my gateway.
 
If you have checked all the IPs and they are correct in the Management Console in the Gateway settings, I would recommend resetting the GW, generating a new Config file from the Management Console and loading it into the GW again.
 
optimus1337

Sorry, it was the post regarding the slow Patton gateway, saw your reply in there and made the incorrect assumption that the issues were both yours.
 
I did a factory reset on the Patton GW and deleted and recreated all of the settings in 3CX and it still doesn't work.

My company is moving to a new location and I just found out that my primary phone number wasn't properly transferred so it isn't active at the new location. I do have two new numbers that are active. I disconnected the primary line and now when I call out I get a prompt telling me that the number I have dialed is not in service. I assume this isn't coming from 3CX or the GW.

I should mention that this was working before I installed the most recent SP on 3CX, however, that was when my gateway had multiple ports defined in 3CX, now I only have the option to define one port. It is my understanding, from looking at the tutorial on configuring the Patton 4114, that I should only be seeing one port with the latest release of 3CX.
 
I had this happen once (on 12.5) and as crazy as it sounds, it was resolved by power cycling the phones. Also be sure your phones have the correct firmware and the Patton gateway has new firmware.

Patton Tech Support was very helpful with some issues we had with some of the newer templates included in 3CX.

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

I wish you success resolving this issue.

--John
 
I was finally able to get it resolved, a tech from Patton was able to remote in and fix it. Unfortunately, I have no clue what he did. I just wish I knew why the config generated by 3CX didn't work.

Thanks to all of you for helping out.
 
optimus1337 said:
I disconnected the primary line and now when I call out I get a prompt telling me that the number I have dialed is not in service. I assume this isn't coming from 3CX or the GW.

If this is still happening then you should speak to your PSTN provider. If you have confirmed that the number you are calling is working at a new location, then it may be a number porting issue. This can happen when you keep the same number but move (port) to another provider, or even to a different central office, with the same provider.
 
optimus1337 said:
I was finally able to get it resolved, a tech from Patton was able to remote in and fix it. Unfortunately, I have no clue what he did. I just wish I knew why the config generated by 3CX didn't work.

Thanks to all of you for helping out.

Make sure to backup the Patton's running configuration to a text file in case you need to load the configuration again or the device dies and you get a replacement.
 
Status
Not open for further replies.