Patton FXS SN4114

[Trent.Rhoden]

Currenty there is a Patton SN4114 connected into our clients 3CX system. The device and extension are registered correctly. We are able to complete calls between the IP and analog phones.

The issue is with the call termination. If the analog side ends the call, the call termination works correctly. If the IP phone ends the call, the analog phone is left with a busy signal and no call termination.

• Patton FXS is using the 3CX template
• Patton is running on R6.11 2018-11-01 H323 SIP FXS FXO
• 3CX version is 15.5.0
• There are no errors in the logs on the 3CX system.

Tests Completed:

• Removed Patton and extension from 3CX system, factory reset Patton and followed 3CX guide to add the devices back in.
• Attempted to set Patton with loop back instead of busy signal on call termination, no change.

Let me know your thoughts.

 

[leejor]

Is this happening on both internal calls, and outside calls? I ask, as you list a Patton FXO, so i'm wondering if it is a PSTN to gateway (non) disconnect issue.

You can check and confirm, in the Activity Log, if a BYE is sent to the Patton FXS, when the far end terminates. If the analogue set remains off hook, then a busy signal may be the standard behaviour, when this happens. Were you expecting it to give dialtone, if they remained off-hook? Personally, i would expect a fast busy (120 ipm), indicating to hang up. This may be changeable in the Patton settings.

 

[Trent.Rhoden]

Very sorry that I did not specify the purpose of the system. This will be an internal only paging system. We have a standard analog phone connected to the FXS for testing purposes but it will end up being connected to a Bogen speaker system.

We originally had it set up directly to the Bogen system and after the paging was complete the user would hang up the phone. The system would continue to send the busy signal across the speaker system for an additional 30 seconds before finally disconnecting and going back to white noise.

It is obviously an issue with the Patton as the busy signal persists with generic analog connected as well.

The end goal would be to have the line go empty once paging is complete so that white noise immediately resumes after page.

I will check the activity log once back in the office.

 

[Trent.Rhoden]

Ran a test call from ext 8361 to 1905 (Paging System) on verbose. Attached is the log.

 

[leejor]

Not sure if there is an option that would allow the Patton to drop the call (sooner) and not go to a busy signal. However, there may be an option to change the busy tone to something else (silence?), when this condition happens. Of course it would affect all sets that use the gateway.

 

[Trent.Rhoden]

Not sure if there is an option that would allow the Patton to drop the call (sooner) and not go to a busy signal. However, there may be an option to change the busy tone to something else (silence?), when this condition happens. Of course it would affect all sets that use the gateway.

This would be the only set affected as this is for the sole purpose of paging. I bet there is a work around, but think that the issue may be the 3CX template. I have submitted a ticket with Patton to check the configuration but am waiting for a reply back on this.

 

[leejor]

It would make sense to play a tone, if an analogue set remained off hook after the other end disconnected. After all, they are still off-hook and there is no other way (other than audibly) to let them know that call has dropped. That is fine under normal circumstances, however when used for paging, it obviously causes an issue. If the tone used was a re-order, and called something unique in the Patton (not just busy tone), and that tone could be changed to something inaudible, then that might be the solution, if nothing else is available.

I'm wondering if the paging unit can sense a current reversal, and act on it, to disconnect. Many ATA's are capable of giving a reversal when the other party hangs up. I'm not sure if the Patton will do this.

 

[eddv123]

You may also want to run some debugging commands from the CLI of the Patton:
https://www.patton.com/support/kb_art.asp?art=446&

From Trinity/putty CLI you can login and run:

enable
configure
debug fxs-signaling
fxs full-detail

Amoung other commands (see guide) that could give you some clues.