[asterisk-dev] Libpri Hangup sends RELEASE COMPLETE with Invalid call reference value always.
virolord at gmail.com
Mon Jan 3 23:02:53 CST 2011
Thanks a lot for clarifying - I'm using FreeSWITCH, I'll check if this can
happen due to FS's code, and update :)
On Tue, Jan 4, 2011 at 12:20 AM, Richard Mudgett <rmudgett at digium.com>wrote:
> > Hi,
> > I'm using the latest stable version of libpri 220.127.116.11 ( also
> > reproducible on 18.104.22.168 ), and am noticing the following Issue in ALL
> > of my hangups ( of all duration - 0, 30, 60 seconds and higher )
> > 1. Say, the user ( leg A ) - Application sends a DISCONNECT to the
> > network ( Leg B ). I'm noticing that libpri destroys the call after
> > receiving a DISCONNECT.
> > 2. Next, A receives RELEASE from Leg B, with a call reference.
> > However, this call reference is not there anymore, and has to be
> > created. It gets created afresh - but as a newcall.
> > So it has c->newcall = 1.
> > 3. The post_handle_931_message function sees this c->newcall = 1, and
> > calls q931_release_complete(ctrl, c, Q931_INVALID_CALL_REFERENCE),
> > which leads to RELEASE COMPLETE always being delivered to LEG B with
> > the message Invalid Call Reference (81).
> > Is this a libpri bug or is there something wrong at my end ? The PRI
> > Q.931 trace of the aforementioned call is at
> > http://pastebin.com/VQ04hhgR ( the relevant lines are highlighted
> > towards the end ).
> From your trace, a pri_destroycall()/q931_destroycall() seems
> to be called right after a call to pri_hangup() that sends the
> DISCONNECT message. Libpri is not going to do this. There
> are two places in Asterisk (v1.8) that will do this. However,
> the code that does it is dealing with a link down situation
> when T309 is not enabled. For the libpri version you mention,
> this will never happen since T309 is always enabled.
> Which version of Asterisk are you using?
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
> asterisk-dev mailing list
> To UNSUBSCRIBE or update options visit:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the asterisk-dev