3CX with Patton 4114 - 4 x FXO

Status
Not open for further replies.

bob21

Joined
Mar 17, 2008
Messages
1
Reaction score
0
Hi

I have 3CX free version running under Win2k, reloaded under new download yesterday, interfaced to a Patton 4114. 3 x extensions - 2 x IP phones, 1 x ATA. As far as I can tell all extensions are configured in the same way.

Extn to Extn calls are all fine - so all phones registered to 3CX correctly and no network issues

Making an external call on an IP phone the call connects with no problem - so the Patton seems to be registered / configured correctly to the 3CX

However, making a call via the ATA extension results in no connection - busy tone

Firewall should not be an issue as the calls are to a regular PSTN line - not a SIP provider.

Have had this problem for a week or so - hence the uninstall / reboot / install new download.

Only port 0 has an external line connected for testing.

Call from ATA Log is :-

13:57:07.390 Call::Terminate [CM503008]: Call(3): Call is terminated
13:57:07.328 Call::RouteFailed [CM503014]: Call(3): Attempt to reach [sip:[email protected]] failed. Reason: Unsupported Media Type
13:57:07.312 CallLeg::onFailure [CM503003]: Call(3): Call to sip:[email protected]:5060 has failed; Cause: 415 Unsupported Media Type; from IP:192.168.1.99:5060
13:57:07.171 CallLeg::onFailure [CM503003]: Call(3): Call to sip:[email protected]:5066 has failed; Cause: 415 Unsupported Media Type; from IP:192.168.1.99:5066
13:57:07.000 CallLeg::onFailure [CM503003]: Call(3): Call to sip:[email protected]:5064 has failed; Cause: 415 Unsupported Media Type; from IP:192.168.1.99:5064
13:57:06.859 CallLeg::onFailure [CM503003]: Call(3): Call to sip:[email protected]:5062 has failed; Cause: 415 Unsupported Media Type; from IP:192.168.1.99:5062
13:57:06.718 CallCtrl::onSelectRouteReq [CM503004]: Call(3): Calling: PSTNline:10002@[Dev:sip:[email protected]:5062, Dev:sip:[email protected]:5064, Dev:sip:[email protected]:5066, Dev:sip:[email protected]:5060]
13:57:06.625 CallCtrl::onIncomingCall [CM503001]: Call(3): Incoming call from Ext.104 to [sip:[email protected]]

Call from IP phone log is :-

13:59:46.390 FaxCfg::updateContact [CM504008]: Fax Service: registered as sip:[email protected]:5060 with contact sip:[email protected]:5100;user=phone
13:59:45.437 Call::Terminate [CM503008]: Call(4): Call is terminated
13:59:45.375 Call::Terminate [CM503008]: Call(4): Call is terminated
13:59:45.328 FaxCfg::updateContact [CM504010]: Fax Service: unregistered contact sip:888:5100;user=phone
13:59:26.484 CallCtrl::onLegConnected [CM503007]: Call(4): Device joined: sip:[email protected]:5060
13:59:26.468 CallCtrl::onLegConnected [CM503007]: Call(4): Device joined: sip:[email protected]:5060;transport=udp
13:59:21.578 Line::printEndpointInfo [CM505002]: Gateway:[Patton4FXO] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Patton SN4114 JO EUI MxSF v3.2.8.45 00A0BA038BB4 R4.2 2007-09-19 H323 SIP FXS FXO] Transport: [sip:192.168.1.100:5060]
13:59:21.343 CallLeg::onFailure [CM503003]: Call(4): Call to sip:[email protected]:5066 has failed; Cause: 502 Bad Gateway; from IP:192.168.1.99:5066
13:59:21.171 CallLeg::onFailure [CM503003]: Call(4): Call to sip:[email protected]:5064 has failed; Cause: 502 Bad Gateway; from IP:192.168.1.99:5064
13:59:20.968 CallLeg::onFailure [CM503003]: Call(4): Call to sip:[email protected]:5062 has failed; Cause: 502 Bad Gateway; from IP:192.168.1.99:5062
13:59:20.828 CallCtrl::onSelectRouteReq [CM503004]: Call(4): Calling: PSTNline:10002@[Dev:sip:[email protected]:5062, Dev:sip:[email protected]:5064, Dev:sip:[email protected]:5066, Dev:sip:[email protected]:5060]
13:59:20.703 CallCtrl::onIncomingCall [CM503001]: Call(4): Incoming call from Ext.101 to [sip:[email protected]]

All advice welcome - thanks in advance

Cheers

Bob
 
Status
Not open for further replies.

Forum statistics

Threads
111,893
Messages
589,595
Members
164,760
Latest member
SaschaA_