Patton gateway: it's impossible to use a port higher than one

gsanchietti commented 6 years ago

On multiport Patton gateway, on both ISDN and FXO, all calls attempted on the port after the first are routed badly to the isdn/fxo port of the gateway.

The call attempt result is that the call is not made and the answer to NethVoice is "Busy signal, hangup cause 34".

Step to reproduce

Configure a Patton gateway with NethVoice Wizard
Connect a phone line on the Patton's second port
On NethVoice/Freepbx interface create an outgoing route with on the first place of "Trunk Sequence" the trunk of the second port of the Patton gateway
With a phone device configured on the NethVoice try to make an outbound call using the newly outgoing route

A suggest fix maybe use the Sangoma gateway configuration also for Patton model. The Sangoma gateway configuration expects to discriminate the port to use with a prefix and not on trunk authentication.

Reported by Andrea Marchionni

Stell0 commented 6 years ago

nethserver-nethvoice14-14.0.8-1.1.g1e49674.ns7.noarch.rpm

gsanchietti commented 6 years ago

Released: nethserver-nethvoice14-14.0.9-1.ns7.noarch

nethesis / dev

Patton gateway: it's impossible to use a port higher than one #5254