Trouble dialing out with Patton 4112

[sl4ppy]

I'm having some difficulty dialing out on my standard analog lines after setting up my 3cx installation with a Patton 4112 2-port FXO.

When I place a call using the 3CXPhone from my PC, it returns "Server Failure".

All my extensions can call each other, and my 4112 receives calls just fine.

My 4112 is completely setup as a PSTN device, and I have a basic outbound rule setup with 9 as the prefix, all extensions specified as valid 'calls from', and 3-11 as number of digits allowable. I have a single route setup with a single strip digit and no prepend.

When I dial 9XXXXXXXXXX from an extension, I immediately received a "Server Failure" message.

3cx server IP is:
10.10.40.4

Patton 4112 FXO IP is:
10.10.40.5

Here is the server log during an attempted call.

20:51:16.878 [CM503008]: Call(3): Call is terminated
20:51:16.815 [CM503020]: Normal call termination. Reason: Server Failure
20:51:16.815 [CM503016]: Call(3): Attempt to reach <sip:[email protected]:5060> failed. Reason: Server Failure
20:51:16.815 [CM503003]: Call(3): Call to sip:[email protected]:5062 has failed; Cause: 502 Bad Gateway; from IP:10.10.40.5:5062
20:51:16.612 [CM503025]: Call(3): Calling PSTNline:xxxxxxxxxx@(Ln.10000@Patton4112-FXO)@[Dev:sip:[email protected]:5062]
20:51:16.612 [MS210006] C:3.3:Offer provided. Connection(by pass mode): 10.10.40.21:40010(40011)
20:51:16.597 [CM503003]: Call(3): Call to sip:[email protected]:5060 has failed; Cause: 487 Request Terminated; from IP:10.10.40.5:5060
20:51:15.097 [CM503025]: Call(3): Calling PSTNline:xxxxxxxxxx@(Ln.10000@Patton4112-FXO)@[Dev:sip:[email protected]:5060]
20:51:15.097 [MS210006] C:3.2:Offer provided. Connection(by pass mode): 10.10.40.21:40010(40011)
20:51:15.066 [CM503004]: Call(3): Route 1: PSTNline:xxxxxxxxxx@(Ln.10000@Patton4112-FXO)@[Dev:sip:[email protected]:5060,Dev:sip:[email protected]:5062]
20:51:15.066 [CM503010]: Making route(s) to <sip:[email protected]:5060>
20:51:15.050 [MS210000] C:3.1:Offer received. RTP connection: 10.10.40.21:40010(40011)
20:51:15.050 Remote SDP is set for legC:3.1
20:51:15.050 [CM505001]: Ext.102: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CXPhone 4.0.10858.0] PBX contact: [sip:[email protected]:5060]
20:51:15.050 [CM503001]: Call(3): Incoming call from Ext.102 to <sip:[email protected]:5060>
20:51:15.035 [CM500002]: Info on incoming INVITE:
INVITE sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 10.10.40.21:3041;branch=z9hG4bK-d8754z-a574d819042b0454-1---d8754z-;rport=3041
Max-Forwards: 70
Contact: <sip:[email protected]:3041;rinstance=85e63f9ed6d6b5b9>
To: <sip:[email protected]:5060>
From: <sip:[email protected]:5060>;tag=ce45f121
Call-ID: YjVlN2QyYTAzMDY1MTE5MTE3NTYzZjE5YzUwNGUyMDA.
CSeq: 2 INVITE
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO
Proxy-Authorization: Digest username="102",realm="3CXPhoneSystem",nonce="414d535c018d3c2286:19a77330c75a85b114c0e55b7f2f2d2d",uri="sip:[email protected]:5060",response="e7e408f70b7054255c9045ab5af065a2",algorithm=MD5
Supported: replaces
User-Agent: 3CXPhone 4.0.10858.0
Content-Length: 0

edit: I completely re-setup the Patton, still trouble, new verbose logs.

 

[sl4ppy]

Desperate for an answer before I am forced to return the 4112. :/

 

[purpleone]

I'm having the same problem with a 4114. I even removed and reinstalled 3CX and defaulted the patton - still no good.

I fixed it before I finished this post. I had to turn off line hunting. When you run the wizard to setup the Patton - leave 'no hunting' selected. I have tested and outgoing calls sill hunt for a free line.

 

[mfm]

Typically this is an indication of a bad line, for whatever reason it might configured incorrectly on the providers side. Grab a normal analog phone and see if you can make calls.

 

[Antares]

We are having this same prob with a Patton 4114. We've confirmed the lines are fine.

 

[leejor]

Is the Patton, perhaps seeing the PSTN lines as being in-use, thereby refusing the call. There is sometimes a voltage threshold setting that gateways uses to make the determination that it should not attempt to place a call or risk interrupting a call already on the line. Usually it doesn't need to be changed from the defaults. Are there any Patton logs that show why the call was rejected?
I see "Request Terminated", Bad Gateway and then Server failure. The Request Terminated seems to indicate that the Patton just doesn't want to, or is unable to handle the call for some reason.

 

[enable]

Check the following settings on the web interface of the Patton (assuming you are in the US). They solved a similar problem for one of my customers:

loop-break-duration min 300 max 1500
disconnect-signal loop-break
disconnect-signal busy-tone

Robert C. Covington
eNable Business Solutions

 

[DrunknMONK]

loop-break-duration min 300 max 1500
disconnect-signal loop-break
disconnect-signal busy-tone

Had the same problem, these worked for me ok in the UK