• V20: 3CX Re-engineered. Get V20 for increased security, better call management, a new admin console and Windows softphone. Learn More.

Outgoing on patton 4114

Status
Not open for further replies.

Resolve

New User
Joined
Sep 19, 2007
Messages
94
Reaction score
0
We've got a patton 4114 connected to 3 analogue lines.

At the moment we can only make 1 outgoing call - otherwise we're busied out:-

0:51:28.293 Call::RouteFailed [CM503014]: Call(80): Attempt to reach [sip:[email protected]:5060] failed. Reason: Busy
10:51:28.293 CallLeg::eek:nFailure [CM503003]: Call(80): Call to sip:[email protected]:5060 has failed; Cause: 486 Busy Here; from IP:192.168.1.3
10:51:28.090 CallLeg::eek:nFailure [CM503003]: Call(80): Call to sip:[email protected]:5060 has failed; Cause: 486 Busy Here; from IP:192.168.1.3
10:51:27.918 CallLeg::eek:nFailure [CM503003]: Call(80): Call to sip:[email protected]:5060 has failed; Cause: 486 Busy Here; from IP:192.168.1.3
10:51:27.762 CallCtrl::eek:nSelectRouteReq [CM503004]: Call(80): Calling: PSTNline:10001@[Dev:sip:[email protected]:5060, Dev:sip:[email protected]:5060, Dev:sip:[email protected]:5060]
10:51:27.700 CallCtrl::eek:nIncomingCall [CM503001]: Call(80): Incoming call from Ext.120 to [sip:[email protected]:5060]


Apart from the one line that really is busy (showing yellow) the other lines show as green.

Any clues ?


Tim
 
Have you checked the ports on the 4114, as it only takes one IP address so I assume each trunk on the gateway is it's own separate port - hence 5060 being busy when line 1 is busy. Try 5061?
 
Pentangle said:
Have you checked the ports on the 4114, as it only takes one IP address so I assume each trunk on the gateway is it's own separate port - hence 5060 being busy when line 1 is busy. Try 5061?

You're correct - it has a seperate port for each..


I don't know how the patton/3cx cycles when a line is busy. On the log it looks to me that it simply tries :5060 3 times whenin fact lines 2-4 are on ports 5062;5064 and 5066.

I *assumed* that 3cx (by the fact that it attempts 3 times) that the port being tried would cycle through each available port.

Tim
 
Resolve said:
Pentangle said:
Have you checked the ports on the 4114, as it only takes one IP address so I assume each trunk on the gateway is it's own separate port - hence 5060 being busy when line 1 is busy. Try 5061?

You're correct - it has a seperate port for each..


I don't know how the patton/3cx cycles when a line is busy. On the log it looks to me that it simply tries :5060 3 times whenin fact lines 2-4 are on ports 5062;5064 and 5066.

I *assumed* that 3cx (by the fact that it attempts 3 times) that the port being tried would cycle through each available port.

Tim

I think programatically, either the Patton or 3CX *could* support the round-robin cycling, but the question really is - "Who's going to own up to being responsible?".

For me, that functionality would be the remit of Patton, so that you can point a SIP device to an IP address and port, and it's then down to the Patton configuration to do it's own round-robining.

I'm off to see a Patton technical specialist on Thursday, so i'll ask the question there.

Cheers,
Mike.
 
I think programatically, either the Patton or 3CX *could* support the round-robin cycling, but the question really is - "Who's going to own up to being responsible?".

For me, that functionality would be the remit of Patton, so that you can point a SIP device to an IP address and port, and it's then down to the Patton configuration to do it's own round-robining.

I'm off to see a Patton technical specialist on Thursday, so i'll ask the question there.

Cheers,
Mike.

I agree - also finding out how the patton actually does anything seems a bit of a intensive task.

I've just seen another post on here where someone has had pretty well the same problem. They took the approach of creating dummy additional gateways.
I might give that a try....


Tim
 
Ok...got it working for now by actually setting up a hunt group on the patton itself. :?:
Fix courtesy of the nice people at Electronic Frontier - Cheers Nick.... :p

Tim
 
Resolve said:
Ok...got it working for now by actually setting up a hunt group on the patton itself. :?:
Fix courtesy of the nice people at Electronic Frontier - Cheers Nick.... :p

Tim

Spoke a bit too soon. Seems now the incoming only comes in on one channel. The web interface on the 4114 is horrible...I'm sure the answer to this is going to be like a hunt group in "reverse"

Tim
 
Status
Not open for further replies.
Get 3CX - Absolutely Free!

Link up your team and customers Phone System Live Chat Video Conferencing

Hosted or Self-managed. Up to 10 users free forever. No credit card. Try risk free.

3CX
A 3CX Account with that email already exists. You will be redirected to the Customer Portal to sign in or reset your password if you've forgotten it.