Peter Svensson wrote:
The two issues are only somewhat related. The RELEASE COMPLETE as an replyI've commented out a few lines of code to make sure * sends DISCONNECT but I'm getting identical results. Seems like it doesn't matter if I skip to RELEASE_COMPLETE or not.
to a SETUP after having sent a CALL PROCEEDING is probably not allowed by
the state transitions listen in q.931.
The in-band announcement is more related to whether we have sent aAre you suggesting that * is telling the other side that we are making noise and they shouldn't? My intent here is to have the telco say "I'm sorry the numbern is not in service" instead of tying up one of our lines for the duration of such a message. Likewise with Congestion.... odd part is that Busy works fine, as I mentioned in my original post.
progress information element which states that in-band audio is available. I think Asterisk sends such a progress message almost as soon as possible. However, in this case the problem is a CALL PROCEEDING before the
RELEASE_COMPLETE answering teh SETUP. The fact that the CALL PROCEEDING
also includes a PROGRESS element is incidental.
Thanks for the posts Peter and Eric. Good to know I am going about this in the right direction.
Trevor _______________________________________________ Asterisk-Users mailing list Asterisk-Users@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
