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
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.
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
Hello,
I just got off the phone with my PRI provider, and was told that I am
not sending an expected message when I reject a call with a Cause Code
for Unassigned(1) and Congestion (42). Busy works fine though...
Anyhow, they are seeing the RELEASE COMPLETE message with cause code 1,
however
Trevor Peirce wrote:
Anyhow, they are seeing the RELEASE COMPLETE message with cause code
1, however the tech told me they expect a PROGRESS indicator with a
value between 1 and 10.
Okay after printing off a dozen pages and taking up tons of floor space
I think I may have figured this out...
As you have already started to debug this by yourself I would suggest a post
to the dev list as this might be a bug.
I'm not familiar with PRI signalling but I think you won't get any answer
here.
Jens
___
Asterisk-Users mailing list
; PRI Out of band indications.
; Enable this to report Busy and Congestion on a PRI using out-of-band
; notification. Inband indication, as used by Asterisk doesn't seem to ;work
; with all telcos.
; outofband: Signal Busy/Congestion out of band with
;RELEASE/DISCONNECT
; inband:
James Sizemore wrote:
; PRI Out of band indications.
; Enable this to report Busy and Congestion on a PRI using out-of-band
; notification. Inband indication, as used by Asterisk doesn't seem to
;work
; with all telcos.
; outofband: Signal Busy/Congestion out of band with
Trevor,
Nah, I think the response is correct. Take a look at the chart again:
http://www.lkn.ei.tum.de/lehre/kn2/anhangKap4.pdf
look at the incoming setup procedure(1 of 2) (user side).
If you get an incoming SETUP, then you MUST respond with one of the following:
CALL PROCEEDING, or
On Thu, 17 Mar 2005, Trevor Peirce wrote:
Trevor Peirce wrote:
Anyhow, they are seeing the RELEASE COMPLETE message with cause code
1, however the tech told me they expect a PROGRESS indicator with a
value between 1 and 10.
Okay after printing off a dozen pages and taking up tons of
On Thu, 17 Mar 2005, Eric Knudson wrote:
Trevor,
Nah, I think the response is correct. Take a look at the chart again:
http://www.lkn.ei.tum.de/lehre/kn2/anhangKap4.pdf
look at the incoming setup procedure(1 of 2) (user side).
If you get an incoming SETUP, then you MUST respond with
hmm - that seems correct - I remember experiencing some similar
problems(using Cisco IOS gateways, though) which were addressed by
voice call convert-discpi-to-prog
http://tinyurl.com/5xn8n
That command addressed an IOS gateway's tendency to hang up before the
in-band message could be played;
On Thu, 17 Mar 2005, Eric Knudson wrote:
hmm - that seems correct - I remember experiencing some similar
problems(using Cisco IOS gateways, though) which were addressed by
voice call convert-discpi-to-prog
http://tinyurl.com/5xn8n
That command addressed an IOS gateway's tendency to hang
13 matches
Mail list logo
