> And you are right. But questions: > > how do i see if SLC=0 and SLC=1 ... SLC=n is / is not working? > module show like chan_dahdi.so Module Description Use Count chan_dahdi.so DAHDI Telephony w/PRI & SS7 78 1 modules loaded Ah, i just see the warrnings (if i have many calls): > module show like chan_dahdi.so Module Description Use Count chan_dahdi.so DAHDI Telephony w/PRI & SS7 184 1 modules loaded It goes like that: WARNING[10402] chan_dahdi.c: MTP2 link down (SLC 1) WARNING[10402] chan_dahdi.c: MTP2 link down (SLC 0) ERROR[10402] chan_dahdi.c: Alarm on link! WARNING[13065] app_dial.c: Unable to forward voice frame WARNING[13113] app_dial.c: Unable to forward voice frame WARNING[10790] chan_dahdi.c: MTP2 link down (SLC 0) WARNING[10790] chan_dahdi.c: Duplicate IAM requested on CIC 69 WARNING[10790] chan_dahdi.c: Duplicate IAM requested on CIC 71 WARNING[10790] chan_dahdi.c: Duplicate IAM requested on CIC 77 WARNING[10790] chan_dahdi.c: Duplicate IAM requested on CIC 89 So this is not very big traffic, but i think that zaptel/dahdi interface is not fast enough to send/receive low-level SS7 messages. i set: mtp2=16 mtp2=47 So, mtp2 layer should be handled in kernel? I've tested Sangoma cards, but hardhdlc looks like not working with ss7 signaling. any hints? Maybe i should use diffrent approach, like having two E1 spans with ss7 and two E1 links to DSS1 (EuroISDN), right now i've got one card for SS7 (4 spans) and one card for DSS1 (also 4 spans)? -- Krzysztof Drewicz +48 504 17 55 77
|