[asterisk-dev] [Code Review] Post trunk-resurrection fixes to libss7.

[rmudgett]

-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviewboard.asterisk.org/r/2150/#review7291
-----------------------------------------------------------



/trunk/isup.c
<https://reviewboard.asterisk.org/r/2150/#comment14080>

    isup_init_call() should now be made static and removed from the libss7 API.



/trunk/isup.c
<https://reviewboard.asterisk.org/r/2150/#comment14079>

    This needs to be done by a new API call.  A new call structure can be created for other reasons than to send an IAM: GRS, RSC, BLO, UBL, etc.
    
    isup_iam() should clear the ISUP_PENDING_IAM flag because IAM is no longer pending.


- rmudgett


On Oct. 5, 2012, 9:47 a.m., KNK wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviewboard.asterisk.org/r/2150/
> -----------------------------------------------------------
> 
> (Updated Oct. 5, 2012, 9:47 a.m.)
> 
> 
> Review request for Asterisk Developers.
> 
> 
> Summary
> -------
> 
> Dual seizure - check for IAM pending in addition to IAM sent
> ISUP_RSC - we should still respond to RSC
> 
> 
> This addresses bug SS7-27.
>     https://issues.asterisk.org/jira/browse/SS7-27
> 
> 
> Diffs
> -----
> 
>   /trunk/isup.c 320 
>   /trunk/libss7.h 320 
>   /trunk/ss7linktest.c 320 
> 
> Diff: https://reviewboard.asterisk.org/r/2150/diff
> 
> 
> Testing
> -------
> 
> compiles
> 
> 
> Thanks,
> 
> KNK
> 
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-dev/attachments/20121017/15469c28/attachment.htm>