Libss7 bug in reset CIC state

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello guys,
I've got a problem with my libss7 installation (Attila version) using "ss7
reset group" command.
I've 2 boxes, both of them with libss7, connected with a single link. If the
cics involved in the reset group command are in IDLE state there's no
problem, the GRS and GRA are succesfully processed on both machines.

But if in the range there're some cic blocked there are two different
behaviours:
- if the machine that is sending the group reset command is the same that
has blocked the cics, these cics will assume on that machine the IDLE state,
but on the other machine the cics will remain in Remotely Blocked state
- if the machine that is sending the group reset command is not the one that
has blocked the cics, the destination machine experience a Segmentation
Fault

Has anybody the same behaviour? I would like to modify the source code, can
you point me in the right direction?
Thank you so much

Enrico Mario
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-ss7/attachments/20091020/27700692/attachment.htm 


[Index of Archives]     [Asterisk App Development]     [PJ SIP]     [Gnu Gatekeeper]     [IETF Sipping]     [Info Cyrus]     [ALSA User]     [Fedora Linux Users]     [Linux SCTP]     [DCCP]     [Gimp]     [Yosemite Backpacking]     [Deep Creek Hot Springs]     [Yosemite Campsites]     [ISDN Cause Codes]     [Asterisk Books]

  Powered by Linux