On Sep 18, 2006, at 10:44 AM, Anton wrote:
> And more
>
> What I do send over SS7
>
> *CLI> --- SS7 Up ---
> -- Resetting CICs 1 to 30
> -- Executing [0060@ss7_test:1]
> Dial("SIP/111-081de268", "ZAP/r3/60") in new stack
> -- Called r3/60
> -- Zap/1-1 is proceeding passing it to SIP/111-081de268
> -- Zap/1-1 answered SIP/111-081de26
>
> and somehow I do receive on the other end an extra "0"
Ok, this is a bug I think I introduced this last week while I was
working on ANSI support. I'll see if I can reproduce it today and put
the fix in svn.
>
> --- SS7 Up ---
> -- Resetting CICs 1 to 30
> [Sep 18 20:38:36] DEBUG[29244]: chan_zap.c:8339 ss7_linkset:
> Got Reset for CICs 1 to 30: Acknowledging
> [Sep 18 20:38:36] DEBUG[29244]: chan_zap.c:8344 ss7_linkset:
> Got GRA from CIC 1 to 30.
> [Sep 18 20:39:05] DEBUG[29244]: chan_zap.c:8348 ss7_linkset:
> Got IAM for CIC 1 and number 600
>
> also I'm still very very confuzed regarding GRA - it should
> not send Group Reset for whole group - since there is a
> signalling timeslot in between! (16)
This is probably because of how you configured your CICs. Please post
your zaptel.conf and zapata.conf. I think I have an idea for what you
did wrong.
Matthew Fredrickson
>
> and still - no audio while it's over chan_ss7 - libss7
>
> regards
> anton.
>
> On 18 September 2006 18:05, Anton wrote:
>> Got debug - was not cofigured logger.conf properly.
>>
>> [Sep 18 18:02:08] DEBUG[6238]: chan_zap.c:8339
>> ss7_linkset: Got Reset for CICs 1 to 15: Acknowledging
>> [Sep 18 18:02:08] DEBUG[6238]: chan_zap.c:8339
>> ss7_linkset: Got Reset for CICs 17 to 31: Acknowledging
>>
>> On 18 September 2006 17:26, Anton wrote:
>>> Just compiled the libss7 and interlinked it with
>>> chan_ss7 for testing. Following issues arised:
>>>
>>> Most major - No audio. Channel occupied and so on - but
>>> I hear nothing.
>>>
>>> Unable to properly assign a linkset with single
>>> signalling channel (say we have only schannel 16 on
>>> first span and no signalling channel on the second
>>> span) seems libss7 somehow not properly counting cic's?
>>> The following should not happen since 16 is setup as
>>> schan
>>>
>>> Sep 18 17:06:21 NOTICE[17607]: chan_ss7.c:2090
>>> handle_GRS_send_hwblock: Got GROUP RESET message,
>>> opc=0xd06, dpc=0xd06, sls=0x0, cic=1, range=29.
>>> Sep 18 17:06:21 NOTICE[17607]: chan_ss7.c:2121
>>> handle_GRS_send_hwblock: Got GRS concerning unequipped
>>> CIC 16, discarding.
>>> Sep 18 17:06:21 WARNING[17607]: chan_ss7.c:3594
>>> monitor_main: MTP is now UP on link 'l1'.
>>> Sep 18 17:06:21 WARNING[17607]: chan_ss7.c:3601
>>> monitor_main: MTP is now INSERVICE for linkset 'test1'.
>>>
>>> lib ss7 lacking verbosity in comparision with chan_ss7
>>> wich provides quite good feedback, showing what is
>>> happening.
>>>
>>> very few command options. Not found how to see the
>>> status of the ss7 link. How is it alligned, what is the
>>> sigchannel, which cics are occupied is possible to find
>>> only by zap show channels - which is not enough at all.
>>>
>>> No current state of the CIC
>>>
>>> Regards,
>>> Anton.
>>> _______________________________________________
>>> --Bandwidth and Colocation provided by Easynews.com --
>>>
>>> asterisk-ss7 mailing list
>>> To UNSUBSCRIBE or update options visit:
>>>
>>> http://lists.digium.com/mailman/listinfo/asterisk-ss7
>>
>> _______________________________________________
>> --Bandwidth and Colocation provided by Easynews.com --
>>
>> asterisk-ss7 mailing list
>> To UNSUBSCRIBE or update options visit:
>> http://lists.digium.com/mailman/listinfo/asterisk-ss7
> _______________________________________________
> --Bandwidth and Colocation provided by Easynews.com --
>
> asterisk-ss7 mailing list
> To UNSUBSCRIBE or update options visit:
> http://lists.digium.com/mailman/listinfo/asterisk-ss7
|