Yate server > Other Yate server issues

Yate MGCP not signalling disconnect on called party disconnect

(1/3) > >>

andrew867:
Hi!

I have an Adit CMG router card configured and working with Yate via MGCPCA (FXS ports are connected locally and through T1 to another channel bank). Using the overlapped.php script I can dial out through the FXS ports but when the called party disconnects Yate does not send a disconnect to the MGCP gateway, it holds the line active and plays 'tone/congestion'.

Is there something I can add to regex route so it will send a disconnect to MGCP instead of holding the line active and playing tones?

Edit:

I think it has something to do with call-ended-target in analog.conf, but I'm unsure how I can change the parameters to allow it to signal a disconnect to the underlying channel driver from the analog module.

marian:
Please post a log with message sniffer enabled.
Please make sure analog channel debug level is 10.

andrew867:
I mis-dialed at first, but the second attempt was successful. It looks like the mgcpca never gets a disconnect from analog to signal the FXS port to drop voltage on disconnect.

andrew867:
Yate should send a Notify with 'osi' as the contents on a far-end disconnect, as per the RFC:

https://tools.ietf.org/html/rfc3660#section-2.4

Other additions that would be great is to signal via MGCP ringback signal (Notify rg) instead of using generated tones, as well as off hook tone (Notify ot) when the line is out-of-service.

marian:
Yate does send a DLCX when the call is terminated.
I'm not sure what the gateway should do. I suppose it should terminate the connection.
The gateway already notified the line on hook event.

Ringback may be set by driver if not provided by called party.
Just set ringback=yes in the line group section.

There is no support in the analog module for disconnect notification.

Navigation

[0] Message Index

[#] Next page