[asterisk-ss7] Libss7

Kaloyan Kovachev kkovachev at varna.net
Wed Nov 23 09:07:02 CST 2022 

As i said - master clock problem: your Yeastar provides the master clock 
and both Digium and Siemens are slaves

change you system.conf
form "span=1,1,0,ccs,hdb3"
to "span=1,0,0,ccs,hdb3"



На 2022-11-23 16:33, Laura Maurizi написа:

> If I make a loop on the Digium,  I have to set slc= 0 and the channels 
> are OK. If I connect the trunk to the Digium I loose synchronization, 
> but if I connect to the trunk to a yeastar the synchronization is 
> restored.
> 
> El mié, 23 nov 2022 a las 9:36, Krzysztof Drewicz 
> (<krzysztofdrewicz at gmail.com>) escribió:
> 
> Hello,
> 
> 1st check the cables, if you make a loop on your connection - does it 
> clear alarm, both - loop in your Digium Card - should affect the green 
> light indicator, then psychical loop towards your partner - he also 
> should acknowledge on clearing the alerts.
> Those are baby steps - then - you check the clock, then - you must 
> agree on SS7/C7 connection details, starting from time slots as "0" is 
> considered "1" on some systems.
> 
> Anyway - this technology is rather obsolete now and even finding a good 
> signalization analyzer or even a E1/T1 connection analyzer (low level 
> link - layer 2 i would say) is hard to find and rather expensive.
> 
> You must be aware that - 4 electrical lines in cables are being used 
> and every single one of them needs to be good (this is not ethernet, 
> you can't mix pairs...)
> 
> śr., 23 lis 2022 o 13:28 Storer, Darren <darren.storer at gmail.com> 
> napisał(a):
> 
> Definitely check whether signalling is actually on TS16 - quite often 
> it can be on TS1 when working with Siemens EWSD.
> 
> Regards
> 
> Darren
> 
> On Mon, 21 Nov 2022 at 13:44, Kaloyan Kovachev <kkovachev at varna.net> 
> wrote: Your link is misaligned. Check the configuration on the other 
> side - it
> should provide the master clock according to your system.conf
> 
> На 2022-11-19 04:20, Laura Maurizi написа:
> 
>> Thanks for your time. I have put sigchan after the group definition,
>> but the result was the same. I notice in the logs (before and after 
>> the
>> modification you suggested) the following message:
>> Huh?! chan_dahdi.c: [11] Huh?! Got FISU in link state 1. I've searched
>> the web but I couldn't find the meaning of this message.
>> 
>> El vie, 18 nov 2022 a las 8:40, Kaloyan Kovachev
>> (<kkovachev at varna.net>) escribió:
>> 
>>> Hello,
>>> put sigchan after the group definition:
>>> 
>>> group=1
>>> cicbeginswith=1
>>> channel => 1-15
>>> cicbeginswith=17
>>> channel => 17-31
>>> sigchan=16
>>> 
>>> for now remove the slc line and check the configuration on the other
>>> side: if it is configured to use different slc, then add it before
>>> sigchan
>>> 
>>> На 2022-11-18 05:20, Laura Maurizi написа:
>>> 
>>>> I have a Digium TE122 whith one span connected to Siemens switch. As
>>>> I
>>>> got the message "ERROR[20309] chan_dahdi.c: [1] Received message for
>>>> slc 0x1, but we are 0x0.  Dropping" I changed slc to 1 in
>>>> chan_dahdi.conf. But now I get this message; "ERROR[20309]
>>>> chan_dahdi.c: [1] Q707 T1 timer expired 2nd time on link SLC: 0 PC:
>>>> 10". The operating system is debian 11, asterisk version is 16.29.0,
>>>> dahdi version is dahdi-2.11.1.0.20170917~dfsg-7.4.
>>>> This is the result I get with ss7 show linkset 1:
>>>> SS7 flags: 0x9
>>>> SS7 linkset 1 status: Down
>>>> SS7 calling nai: -1
>>>> SS7 called nai: -1
>>>> SS7 nationalprefix: 0
>>>> SS7 internationalprefix: 00
>>>> SS7 unknownprefix:
>>>> SS7 networkroutedprefix:
>>>> SS7 subscriberprefix:
>>>> Switch type: ITU
>>>> Our point code: 20
>>>> SLS shift: 0
>>>> numlinks: 1
>>>> numsps: 1
>>>> ---------------------------------
>>>> Adjacent SP PC: 10 STATE: DOWN
>>>> TRA:      T19: not running T21: not running
>>>> Routes:
>>>> DPC       State        T6       T10
>>>> Link ADJ_PC:SLC: 10:1 NetMngSLS: 0
>>>> State:      INSERVICE,  DOWN
>>>> STD Test:  failed
>>>> Got, sent :
>>>> Inhibit:
>>>> Changeover: NO
>>>> Tx buffer:  0
>>>> Tx queue:   0
>>>> Retrans pos 0
>>>> CO buffer:  0
>>>> CB buffer:  0
>>>> Last FSN:   0
>>>> MTP3timers: Q707_T1(1s)
>>>> 
>>>> This is the message I get in the log:
>>>> [Nov 10 06:39:05] ERROR[20525] chan_dahdi.c: [1] Q707 T1 timer
>>>> expired
>>>> 2nd time on link SLC: 1 PC: 10
>>>> [Nov 10 06:39:05] VERBOSE[20525] chan_dahdi.c: [1] Len = 20 [ 91 87
>>>> 11
>>>> 81 0a 00 05 00 11 a0 32 35 36 34 32 38 36 32 38 38 ]
>>>> [Nov 10 06:39:05] VERBOSE[20525] chan_dahdi.c: [1] FSN: 7 FIB 1
>>>> [Nov 10 06:39:05] VERBOSE[20525] chan_dahdi.c: [1] BSN: 17 BIB 1
>>>> [Nov 10 06:39:05] VERBOSE[20525] chan_dahdi.c: [1] >[10:1] MSU
>>>> [Nov 10 06:39:05] VERBOSE[20525] chan_dahdi.c: [1] [ 91 87 11 ]
>>>> [Nov 10 06:39:05] VERBOSE[20525] chan_dahdi.c: [1] Network 
>>>> Indicator:
>>>> 2
>>>> Priority: 0 User Part: STD_TEST (1)
>>>> [Nov 10 06:39:05] VERBOSE[20525] chan_dahdi.c: [1] [ 81 ]
>>>> [Nov 10 06:39:05] VERBOSE[20525] chan_dahdi.c: [1] OPC 20 DPC 10 SLS
>>>> 0
>>>> [Nov 10 06:39:05] VERBOSE[20525] chan_dahdi.c: [1] [ 0a 00 05 00 ]
>>>> [Nov 10 06:39:05] VERBOSE[20525] chan_dahdi.c: [1] H0: 1 H1: 1
>>>> [Nov 10 06:39:05] VERBOSE[20525] chan_dahdi.c: [1] [ 11 a0 32 35 36
>>>> 34
>>>> 32 38 36 32 38 38 ]
>>>> [Nov 10 06:39:05] VERBOSE[20525] chan_dahdi.c: [1]
>>>> [Nov 10 06:39:05] VERBOSE[20525] chan_dahdi.c: [1] Len = 3 [ 91 87 
>>>> 00
>>>> ]
>>>> [Nov 10 06:39:05] VERBOSE[20525] chan_dahdi.c: [1] FSN: 7 FIB 1
>>>> [Nov 10 06:39:05] VERBOSE[20525] chan_dahdi.c: [1] BSN: 17 BIB 1
>>>> [Nov 10 06:39:05] VERBOSE[20525] chan_dahdi.c: [1] >[10:1] FISU
>>>> [Nov 10 06:39:05] VERBOSE[20525] chan_dahdi.c: [1]
>>>> [Nov 10 06:39:09] VERBOSE[20525] chan_dahdi.c: [1] Len = 20 [ 91 88
>>>> 11
>>>> 81 0a 00 05 00 11 a0 32 35 36 34 32 38 36 32 38 38 ]
>>>> [Nov 10 06:39:09] VERBOSE[20525] chan_dahdi.c: [1] FSN: 8 FIB 1
>>>> [Nov 10 06:39:09] VERBOSE[20525] chan_dahdi.c: [1] BSN: 17 BIB 1
>>>> [Nov 10 06:39:09] VERBOSE[20525] chan_dahdi.c: [1] >[10:1] MSU
>>>> [Nov 10 06:39:09] VERBOSE[20525] chan_dahdi.c: [1] [ 91 88 11 ]
>>>> [Nov 10 06:39:09] VERBOSE[20525] chan_dahdi.c: [1] Network 
>>>> Indicator:
>>>> 2
>>>> Priority: 0 User Part: STD_TEST (1)
>>>> [Nov 10 06:39:09] VERBOSE[20525] chan_dahdi.c: [1] [ 81 ]
>>>> [Nov 10 06:39:09] VERBOSE[20525] chan_dahdi.c: [1] OPC 20 DPC 10 SLS
>>>> 0
>>>> [Nov 10 06:39:09] VERBOSE[20525] chan_dahdi.c: [1] [ 0a 00 05 00 ]
>>>> [Nov 10 06:39:09] VERBOSE[20525] chan_dahdi.c: [1] H0: 1 H1: 1
>>>> [Nov 10 06:39:09] VERBOSE[20525] chan_dahdi.c: [1] [ 11 a0 32 35 36
>>>> 34
>>>> 32 38 36 32 38 38 ]
>>>> [Nov 10 06:39:09] VERBOSE[20525] chan_dahdi.c: [1]
>>>> [Nov 10 06:39:12] VERBOSE[20525] chan_dahdi.c: [1] Len = 14 [ 88 92
>>>> 0b
>>>> 85 14 80 02 10 01 00 17 01 01 0e ]
>>>> [Nov 10 06:39:12] VERBOSE[20525] chan_dahdi.c: [1] FSN: 18 FIB 1
>>>> [Nov 10 06:39:12] VERBOSE[20525] chan_dahdi.c: [1] BSN: 8 BIB 1
>>>> [Nov 10 06:39:12] VERBOSE[20525] chan_dahdi.c: [1] <[10:1] MSU
>>>> [Nov 10 06:39:12] VERBOSE[20525] chan_dahdi.c: [1] [ 88 92 0b ]
>>>> [Nov 10 06:39:12] VERBOSE[20525] chan_dahdi.c: [1] Network 
>>>> Indicator:
>>>> 2
>>>> Priority: 0 User Part: ISUP (5)
>>>> [Nov 10 06:39:12] VERBOSE[20525] chan_dahdi.c: [1] [ 85 ]
>>>> [Nov 10 06:39:12] VERBOSE[20525] chan_dahdi.c: [1] OPC 10 DPC 20 SLS
>>>> 1
>>>> [Nov 10 06:39:12] VERBOSE[20525] chan_dahdi.c: [1] [ 14 80 02 10 ]
>>>> [Nov 10 06:39:12] VERBOSE[20525] chan_dahdi.c: [1] CIC: 1
>>>> [Nov 10 06:39:12] VERBOSE[20525] chan_dahdi.c: [1] [ 01 00 ]
>>>> [Nov 10 06:39:12] VERBOSE[20525] chan_dahdi.c: [1] Message Type:
>>>> GRS(0x17)
>>>> [Nov 10 06:39:12] VERBOSE[20525] chan_dahdi.c: [1] [ 17 ]
>>>> [Nov 10 06:39:12] VERBOSE[20525] chan_dahdi.c: [1] --VARIABLE LENGTH
>>>> PARMS[1]--
>>>> [Nov 10 06:39:12] VERBOSE[20525] chan_dahdi.c: [1] Range and status:
>>>> [Nov 10 06:39:12] VERBOSE[20525] chan_dahdi.c: [1] Range: 14
>>>> [Nov 10 06:39:12] VERBOSE[20525] chan_dahdi.c: [1] [ 01 0e ]
>>>> [Nov 10 06:39:12] VERBOSE[20525] chan_dahdi.c: [1]
>>>> [Nov 10 06:39:12] ERROR[20525] chan_dahdi.c: [1] Got ISUP message on
>>>> link while MTP3 state is not UP!
>>>> 
>>>> I attatch the configuration files.
>>>> Thanks in advance.
> 
> --
> _____________________________________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
> 
> asterisk-ss7 mailing list
> To UNSUBSCRIBE or update options visit:
> http://lists.digium.com/mailman/listinfo/asterisk-ss7 --
> _____________________________________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
> 
> asterisk-ss7 mailing list
> To UNSUBSCRIBE or update options visit:
> http://lists.digium.com/mailman/listinfo/asterisk-ss7
  --
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-ss7 mailing list
To UNSUBSCRIBE or update options visit:
    http://lists.digium.com/mailman/listinfo/asterisk-ss7

More information about the asterisk-ss7 mailing list