Patton Trinity FXO incorrect handle of outbound busy line

ltarmak commented 2 years ago

When a FXO port is already in use, in current configuration of the autoprovisioned voice gateway (if nethvoice sends another call) is to return busy with q850 reason 17 (busy), this prevent nethvoice to try next port (if available). It signals that the user is busy, the correct signaling should be congestion.

Steps to reproduce Autoprovision a FXO TRINITY gateway with al least 2 ports and connect them to telephony line Set the 2 port in ascending order to an oubound route Make an outobound call and dont hang up it (it will use the first line) Make another outbound call

Expected behavior The second call should go to the second FXO port

Actual behavior It will return busy signaling instead of using the second FXO port and nethvoice also return busy message to the caller.

Components nethvoice-wizard-restapi-14.13.1-1.4.g8e17081