still waiting, actually i've not been able to even run my Asterisk server
with an SS7 E1 link for once.........can any one help me in this regard
plz.....all conf & probs are described in the previous message to this list
On 9/18/06, umar tarar <umar.tarar@xxxxxxxxx> wrote:
>
> i am in urgent need to solve this problem
>
> what happens is:
> a- with the LED green on the Quad-E1 Digium-TE411P card & crc4 enabled in
> zaptel.conf, when we try to run Asterisk it simply shows some error
> related to zaptel & quits back to the LINUX prompt
>
> b- with the LED green & crc4 disabled in zaptel.conf, the asterisk
> initially runs successfully, but then starts showing these errors in
> chan_ss7 module relating to CRC
> ----------------------------(the CLI log): ------------------------------
> Asterisk Ready.
> *CLI> Sep 14 03:05:39 WARNING[5295]: mtp.c:760 timeout_sltm_t1: No SLTA
> received within Q.707 timer T1, trying again on link 'l1'.
> Sep 14 03:05:48 ERROR[5295]: mtp.c:765 timeout_sltm_t1: No SLTA received
> within Q.707 timer T1, faulting link on link 'l1'.
> Sep 14 03:05:48 WARNING[5295]: chan_ss7.c:3598 monitor_main: MTP is now
> DOWN on link 'l1'.
> Sep 14 03:05:48 NOTICE[5295]: mtp.c:471 mtp_changeover: MTP changeover
> last_ack=4, last_sent=4, from schannel 16, no INSERVICE schannel found
> Sep 14 03:05:48 NOTICE[5295]: mtp.c:475 mtp_changeover: Failover not
> possible, no other signalling link and no other host available.
> Sep 14 03:05:59 WARNING[5295]: mtp.c:760 timeout_sltm_t1: No SLTA received
> within Q.707 timer T1, trying again on link 'l1'.
> Sep 14 03:06:08 ERROR[5295]: mtp.c:765 timeout_sltm_t1: No SLTA received
> within Q.707 timer T1, faulting link on link 'l1'.
> Sep 14 03:06:08 WARNING[5295]: chan_ss7.c:3598 monitor_main: MTP is now
> DOWN on link 'l1'.
> Sep 14 03:06:08 NOTICE[5295]: mtp.c:471 mtp_changeover: MTP changeover
> last_ack=8, last_sent=8, from schannel 16, no INSERVICE schannel found
> Sep 14 03:06:08 NOTICE[5295]: mtp.c:475 mtp_changeover: Failover not
> possible, no other signalling link and no other host available.
> ss7 Sep 14 03:06:19 WARNING[5295]: mtp.c:760 timeout_sltm_t1: No SLTA
> received within Q.707 timer T1, trying again on link 'l1'.
> cluster Sep 14 03:06:21 WARNING[5295]: chan_ss7.c:3534 monitor_main:
> Received CIC=65 for unequipped circuit (typ=CGB), link 'l1'.
> status
> Sep 14 03:06:28 ERROR[5295]: mtp.c:765 timeout_sltm_t1: No SLTA received
> within Q.707 timer T1, faulting link on link 'l1'.
> Sep 14 03:06:28 WARNING[5295]: chan_ss7.c:3598 monitor_main: MTP is now
> DOWN on link 'l1'.
> Sep 14 03:06:28 NOTICE[5295]: mtp.c:471 mtp_changeover: MTP changeover
> last_ack=7, last_sent=7, from schannel 16, no INSERVICE schannel found
> Sep 14 03:06:28 NOTICE[5295]: mtp.c:475 mtp_changeover: Failover not
> possible, no other signalling link and no other host available.
>
> *CLI> ss7 linestat
> Linkset: suic
> CIC 1 Idle Reset pending BLOCKED Link down
> CIC 2 Idle Reset pending BLOCKED Link down
> CIC 3 Idle Reset pending BLOCKED Link down
> CIC 4 Idle Reset pending BLOCKED Link down
> CIC 5 Idle Reset pending BLOCKED Link down
> CIC 6 Idle Reset pending BLOCKED Link down
> CIC 7 Idle Reset pending BLOCKED Link down
> CIC 8 Idle Reset pending BLOCKED Link down
> CIC 9 Idle Reset pending BLOCKED Link down
> CIC 10 Idle Reset pending BLOCKED Link down
> CIC 11 Idle Reset pending BLOCKED Link down
> CIC 12 Idle Reset pending BLOCKED Link down
> CIC 13 Idle Reset pending BLOCKED Link down
> CIC 14 Idle Reset pending BLOCKED Link down
> CIC 15 Idle Reset pending BLOCKED Link down
> CIC 17 Idle Reset pending BLOCKED Link down
> CIC 18 Idle Reset pending BLOCKED Link down
> CIC 19 Idle Reset pending BLOCKED Link down
> CIC 20 Idle Reset pending BLOCKED Link down
> CIC 21 Idle Reset pending BLOCKED Link down
> CIC 22 Idle Reset pending BLOCKED Link down
> CIC 23 Idle Reset pending BLOCKED Link down
> CIC 24 Idle Reset pending BLOCKED Link down
> CIC 25 Idle Reset pending BLOCKED Link down
> CIC 26 Idle Reset pending BLOCKED Link down
> CIC 27 Idle Reset pending BLOCKED Link down
> CIC 28 Idle Reset pending BLOCKED Link down
> CIC 29 Idle Reset pending BLOCKED Link down
> CIC 30 Idle Reset pending BLOCKED Link down
> CIC 31 Idle Reset pending BLOCKED Link down
>
> *CLI> Sep 14 03:07:08 ERROR[5295]: mtp.c:765 timeout_sltm_t1: No SLTA
> received within Q.707 timer T1, faulting link on link 'l1'.
> Sep 14 03:07:08 WARNING[5295]: chan_ss7.c:3598 monitor_main: MTP is now
> DOWN on link 'l1'.
> Sep 14 03:07:08 NOTICE[5295]: mtp.c:471 mtp_changeover: MTP changeover
> last_ack=6, last_sent=6, from schannel 16, no INSERVICE schannel found
> Sep 14 03:07:08 NOTICE[5295]: mtp.c:475 mtp_changeover: Failover not
> possible, no other signalling link and no other host available.
> Sep 14 03:07:18 WARNING[5295]: mtp.c:760 timeout_sltm_t1: No SLTA received
> within Q.707 timer T1, trying again on link 'l1'.
> Sep 14 03:07:19 WARNING[5295]: chan_ss7.c:3534 monitor_main: Received
> CIC=65 for unequipped circuit (typ=CGB), link 'l1'.
> Sep 14 03:07:27 ERROR[5295]: mtp.c:765 timeout_sltm_t1: No SLTA received
> within Q.707 timer T1, faulting link on link 'l1'.
> Sep 14 03:07:27 WARNING[5295]: chan_ss7.c:3598 monitor_main: MTP is now
> DOWN on link 'l1'.
> Sep 14 03:07:27 NOTICE[5295]: mtp.c:471 mtp_changeover: MTP changeover
> last_ack=7, last_sent=7, from schannel 16, no INSERVICE schannel found
> Sep 14 03:07:27 NOTICE[5295]: mtp.c:475 mtp_changeover: Failover not
> possible, no other signalling link and no other host available.
> Sep 14 03:07:35 NOTICE[5295]: mtp.c:1442 mtp_thread_main: Excessive poll
> delay 21373!
> Sep 14 03:07:35 NOTICE[5295]: mtp.c:1496 mtp_thread_main: Full Zaptel
> input buffer detected, incoming packets may have been lost on link 'l1'.
> Sep 14 03:07:35 NOTICE[5295]: mtp.c:1543 mtp_thread_main: Empty Zaptel
> output buffer detected, outgoing packets may have been lost on link 'l1'.
> Sep 14 03:07:35 NOTICE[5295]: mtp.c:1227 mtp2_read_su: MTP2 CRC error
> (CRC=0xfe96 != 0xf0b8) on link 'l1'.
> Sep 14 03:07:35 NOTICE[5295]: mtp.c:1442 mtp_thread_main: Excessive poll
> delay 13193!
> Sep 14 03:07:35 NOTICE[5295]: mtp.c:1496 mtp_thread_main: Full Zaptel
> input buffer detected, incoming packets may have been lost on link 'l1'.
> Sep 14 03:07:35 NOTICE[5295]: mtp.c:1543 mtp_thread_main: Empty Zaptel
> output buffer detected, outgoing packets may have been lost on link 'l1'.
> Sep 14 03:07:35 NOTICE[5295]: mtp.c:1442 mtp_thread_main: Excessive poll
> delay 14158!
> Sep 14 03:07:35 NOTICE[5295]: mtp.c:1496 mtp_thread_main: Full Zaptel
> input buffer detected, incoming packets may have been lost on link 'l1'.
> Sep 14 03:07:35 NOTICE[5295]: mtp.c:1543 mtp_thread_main: Empty Zaptel
> output buffer detected, outgoing packets may have been lost on link 'l1'.
> Sep 14 03:07:35 NOTICE[5295]: mtp.c:1221 mtp2_read_su: Short MTP2 frame
> len 3 < 5 on link 'l1'.
> Sep 14 03:07:35 NOTICE[5295]: mtp.c:1442 mtp_thread_main: Excessive poll
> delay 13360!
> Sep 14 03:07:35 NOTICE[5295]: mtp.c:1496 mtp_thread_main: Full Zaptel
> input buffer detected, incoming packets may have been lost on link 'l1'.
> Sep 14 03:07:35 NOTICE[5295]: mtp.c:1543 mtp_thread_main: Empty Zaptel
> output buffer detected, outgoing packets may have been lost on link 'l1'.
> .
> .
> .
> (almost same CLI log as above)
> .
> .
> .
> Sep 14 03:07:37 NOTICE[5295]: mtp.c:1442 mtp_thread_main: Excessive poll
> delay 3391!
> Sep 14 03:07:37 WARNING[5295]: mtp.c:644 mtp2_emon_count_error: Excessive
> errors detected in alignment error rate monitor, link failed on link 'l1'.
> Sep 14 03:07:37 NOTICE[5295]: mtp.c:1496 mtp_thread_main: Full Zaptel
> input buffer detected, incoming packets may have been lost on link 'l1'.
> Sep 14 03:07:37 NOTICE[5295]: mtp.c:1543 mtp_thread_main: Empty Zaptel
> output buffer detected, outgoing packets may have been lost on link 'l1'.
> ------------------------------(CLI log: end )---------------------------
>
> observing this all carefully identifies to us that there is something
> wrong with the CRC4 when we try to run it on an SS7 link, because on PRI it
> works all okay
> moreover it seems that if we enable crc4 in zaptel.conf then the problem
> is get caught at the very initial steps by the zaptel driver, thats why when
> we disable it then it lets asterisk run successfully & once chan_ss7.so is
> loading or loaded, it show the errors(shown in above log)
>
> we are using:
>
> FC-4 (kernal-2.6)
> Asterisk-1.2.10
> zaptel-1.2.7
> chan_ss7-0.8.4
> (& the SS7-E1 link of the telco do not has any problems as it works all
> fine on their own SIP server)
>
> our configuration: --------zaptel.conf----------
> span=1,1,0,ccs,hdb3,crc4
> bchan=1-31
> loadzone=uk
> defaultzone=uk
> ---------------------------------
>
> ----------ss7.conf----------
> [linkset-siuc]
> enabled=>yes
> enable_st=>yes
> use_connect=>yes
> hunting_policy=>even_mru
> subservice=>auto
>
> [link-l1]
> linkset=>siuc
> channels=>1-15,17-31
> schannels=>16
> firstcic=>1
> enabled=>yes
>
> [host-ACDsvr]
> enabled=>yes
> opc=>0x8e0
> dpc=>suic:0x3fff
> links=>l1:1
> ----------------------------
>
> any thing wrong with the configuration, concept or etc
> plz help in making the Asterisk work with the ss7 E1 link
>
--
|__\__/__| /__/ \__\ |__| \__|
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-ss7/attachments/20060921/fcffcc95/attachment.htm
|