[Asterisk-Users] PRI Cause Code Help

[Eric Knudson]

Trevor,

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).

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?

Eric




On Fri, 18 Mar 2005 08:28:27 -0800, Trevor Peirce <tpeirce at digitalcon.ca> wrote:
> Peter Svensson wrote:
> 
> >The two issues are only somewhat related. The RELEASE COMPLETE as an reply
> >to a SETUP after having sent a CALL PROCEEDING is probably not allowed by
> >the state transitions listen in q.931.
> >
> >
> I'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.
> 
> >The in-band announcement is more related to whether we have sent a
> >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.
> >
> >
> Are 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.
> 
> 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 at 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
>