Unable to dial outbound with Patton 4114

Status
Not open for further replies.

nplummer

Joined
May 14, 2010
Messages
22
Reaction score
0
We have an existing 3CX system which has been running for almost 2 years. We are running Version 10 SP6. We are testing a new Patton 4114 to use with our analog lines. The Patton has been updated to the most current firmware (6.1).

We went through the configuration setup in the management console and exported the config file to the Patton device and imported it. After the Patton came back up we saw that it was registered with the system and ready for testing.

Inbound calls function normally. However, dialing outbound we can see the green light on the Patton (line 1) light up for about 1 second, then the 3CX system gives an audible message of "Cancelled" and hangs up. We have verified that the outbound dialing rules are set correctly and we have rebooted the Patton a few times to make sure it is getting a good load of the config file.

Below is a snippet from our loggs showing a call. Any help would be greatly appreciated.

16:31:46.817 [CM503008]: Call(18869): Call is terminated
16:31:43.770 Session 3389581 of leg C:18869.1 is confirmed
16:31:43.426 [CM503007]: Call(18869): Device joined: sip:[email protected]:40600;rinstance=edd21db396bc9fee
16:31:43.426 [CM503007]: Call(18869): Device joined: sip:[email protected]:5060
16:31:43.410 [MS210003] C:18869.1:Answer provided. Connection(transcoding mode[unsecure]):10.10.1.1:7244(7245)
16:31:43.410 [MS210001] C:18869.3:Answer received. RTP connection[unsecure]: 127.0.0.1:40650(40651)
16:31:43.410 Remote SDP is set for legC:18869.3
16:31:43.410 [CM503002]: Call(18869): Alerting sip:[email protected]:40600;rinstance=edd21db396bc9fee
16:31:43.207 [CM503025]: Call(18869): Calling Unknown:Ext.EndCall@[Dev:sip:[email protected]:40600;rinstance=edd21db396bc9fee]
16:31:43.207 [MS210002] C:18869.3:Offer provided. Connection(transcoding mode): 127.0.0.1:7248(7249)
16:31:43.207 [CM503016]: Call(18869): Attempt to reach <sip:[email protected]> failed. Reason: Request Terminated
16:31:43.207 [CM503003]: Call(18869): Call to sip:[email protected]:5060 has failed; Cause: 487 Request Terminated; from IP:10.10.1.178:5060
16:31:41.785 [CM503025]: Call(18869): Calling PSTNline:5974800@(Ln.10014@Analog Lines)@[Dev:sip:[email protected]:5060]
16:31:41.785 [MS210002] C:18869.2:Offer provided. Connection(transcoding mode): 10.10.1.1:7246(7247)
16:31:41.738 [CM503004]: Call(18869): Route 1: PSTNline:5974800@(Ln.10014@Analog Lines)@[Dev:sip:[email protected]:5060]
16:31:41.738 [CM503010]: Making route(s) to <sip:[email protected]>
16:31:41.738 [MS210000] C:18869.1:Offer received. RTP connection: 10.10.1.177:16002(16003)
16:31:41.738 Remote SDP is set for legC:18869.1
16:31:41.738 [CM505001]: Ext.312: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Panasonic_KX-UT670/01.022 (0080f0de3d3f)] PBX contact: [sip:[email protected]:5060]
16:31:41.738 [CM503001]: Call(18869): Incoming call from Ext.312 to <sip:[email protected]>
16:31:41.723 [CM500002]: Info on incoming INVITE:
INVITE sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 10.10.1.177:5060;branch=z9hG4bKs2e22950cf
Max-Forwards: 70
Contact: <sip:[email protected]:5060>
To: <sip:[email protected]>
From: "Nepal Plummer - 312"<sip:[email protected]>;tag=931388633
Call-ID: [email protected]
CSeq: 2 INVITE
Allow: INVITE, ACK, CANCEL, BYE, INFO, OPTIONS, NOTIFY, REFER
Proxy-Authorization: Digest realm="3CXPhoneSystem",nonce="414d535c05c4c9dd25:c407ae28d729570cf4384c9091861670",algorithm=MD5,uri="sip:[email protected]:5060",username="312",response="dca32efe34e1ed20c5a1d325a6a6f3f7"
Supported: replaces
User-Agent: Panasonic_KX-UT670/01.022 (0080f0de3d3f)



Thank You,

Nepal
Fahillion Technologies
 
Did you make any changes to the outbound rules ie calls to numbers starting with prefix X,X,X,X,X,.. As well as the call coming from extionson 100-110?
 
I contacted Patton and received an updated config file which modified the "low loop-break duration" setting. It was set at 60ms as the minimum and they suggested a modification to 200ms. After making that change to the config file I uploaded it and tested. Both inbound and outbound calls are functioning properly.

Nepal Plummer
Fahillion Technologies
 
Status
Not open for further replies.

Forum statistics

Threads
111,852
Messages
589,385
Members
164,690
Latest member
rick.yamamoto