[asterisk-dev] Libpri Hangup sends RELEASE COMPLETE with Invalid call reference value always.

[Richard Mudgett]

> Hi,
> 
> 
> I'm using the latest stable version of libpri 1.4.11.5 ( also
> reproducible on 1.4.11.4 ), 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 ).