Mantis Bugtracker

Viewing Issue Simple Details Jump to Notes ] View Advanced ] Issue History ] Print ]
ID Category Severity Reproducibility Date Submitted Last Update
0000305 [Yate - Yet Another Telephony Engine] module minor always 2012-06-03 07:05 2012-06-03 14:47
Reporter jice View Status public  
Assigned To
Priority normal Resolution open  
Status new   Product Version SVN
Summary 0000305: ISUP: support for sending correct messages when the call is not yet in state Accepted
Description When setting "accept_call=false" and getting an incoming call on an ISUP channel, the 'ringing', 'progress' and 'answer' events would not trigger the sending of any message to the ISUP peer.
Additional Information When ACM was not previously sent, it is expected that a 'ringing' or 'progress' event triggers the sending of ACM with appropriate indicators.
Similarly it is expected that a 'answer' event triggers the sending of a CON message.

Attached is a patch to handle these cases.
Tags No tags attached.
Attached Files ? file icon acm_con_patch.diff [^] (1,513 bytes) 2012-06-03 07:05

- Relationships

-  Notes
(0000457)
shimaore (reporter)
2012-06-03 14:47

Call flow in RFC3398 section 8.1.1

- Issue History
Date Modified Username Field Change
2012-06-03 07:05 jice New Issue
2012-06-03 07:05 jice File Added: acm_con_patch.diff
2012-06-03 14:47 shimaore Note Added: 0000457


Copyright © 2000 - 2008 Mantis Group
Powered by Mantis Bugtracker