On Fri, 18 Mar 2005, Eric Knudson wrote: > Yeah, I thought the root problem was that the telco was expecting you > to include some PI , not that the messages were disallowed(order of > DISCONNECT vs RELEASE COMPLETE), though it appears that sending a > release complete would be valid based on the clearing procedure > detailed in fig. A.2/Q.931 (sheet 6 of 7).
Interesting. How do you reach that conclusion? The only fork that can be taken in that sheet without first receiving a RELEASE or DISCONNECT is the one that begins by sending a DISCONNECT. > Since the telco is saying that you're not including a PI and that > seems to be the problem, then it means that they're expecting you to > tie up a channel for a few seconds and play a message back to the > caller. I would look for a way that you can manipulate the outgoing > disconnect cause code and see if you can find something that works. > Don't know how relevant this is, but are you configured for user side > or network side signaling? I think a full pri log and an exceprt from the dialplan may be helpful. Peter _______________________________________________ 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