Hello Ariel:
I have a few comments on this topic.
--- El mar 14-oct-08, Ariel Leche (Metrotel) <aleche at metrotel.com.ar> escribi?:
> De: Ariel Leche (Metrotel) <aleche at metrotel.com.ar>
> Asunto: [asterisk-ss7] Answer chanss7 Argentina
> Para: asterisk-ss7 at lists.digium.com
> Fecha: martes, 14 de octubre de 2008, 2:20 pm
> My name is Ariel, I write from Buenos Aires Argentina,
> I'm configuring a
> platform for SS7 to by connected to PSTN ZTE model J10. I
> need your help, if
> you cant, take time to help me solving my problem.
>
>
>
>
>
>
>
> Asterisk 1.4.21
>
> Zaptel 1.4
>
> Chan-ss7 1.0.0
>
> 4E1 Digium
>
>
>
> The link this is in SERVICE, but de channel CIC, always are
> in: Idle Reset
> pending
>
> metross7*CLI> ss7 link status
>
> linkset metro, link i1, schannel 16, sls 0, INSERVICE, rx:
> 3, tx: 3/3,
> sentseq/lastack: 85/85, total 13626416, 13626512
>
>
>
> metross7*CLI> ss7 linestat
>
> Linkset: metro
>
> CIC 1 Idle Reset pending
>
> CIC 2 Idle Reset pending
>
> CIC 3 Idle Reset pending
>
> CIC 4 Idle Reset pending
>
> CIC 5 Idle Reset pending
>
> CIC 6 Idle Reset pending
>
> CIC 7 Idle Reset pending
>
>
>
> metross7*CLI> ss7 mtp data
>
> [Sep 26 08:09:49] ERROR[4208]: mtp.c:870 mtp2_queue_msu:
> Got illegal MSU
> length 0 < 2, dropping frame on link 'i1'.
>
> metross7*CLI>
>
>
The idea behind the "ss7 mtp data" command is inject a hex encoded string into the MTP buffer, e.g. you can use it to replicate a SS7 message out of the flow.
You are getting an error because you aren't executing the command correctly.
>
> EJ: ZAPTEL:
>
> #span=1,2,0,ccs,hdb3
>
> # termtype: te
>
> bchan=1-15,17-31
>
> #dchan=16
>
>
>
> # Span 2: TE4/0/2 "T4XXP (PCI) Card 0 Span 2"
>
> span=2,1,0,ccs,hdb3
>
> # termtype: te
>
> bchan=32-46,47-63
>
> #dchan=47
>
>
I would suggest you to use bchan=32-62. The syntax of bchan=32-46,47-63 doesn't make any sense to me.
>
> Or If I configured Bchan= 1- 124 too Works it good.
>
>
>
> SS7. conf.:
>
> [linkset-metro]
>
> enabled => yes
>
> enable_st => no
>
> use_connect => no
>
> hunting_policy => seq_lth
>
> context => ss7
>
> language => ar
>
> subservice => 8
>
>
>
> [link-i1]
>
> linkset => metro
>
> channels => 1-15,17-31
>
> schannel => 16
>
> firstcic => 1
>
> enabled => yes
>
> echocancel => allways
>
> ;echocan_train =>250
>
> ;echocan_taps =>118
>
>
>
> [host-metross7]
>
> enabled => yes
>
> opc => 4673
>
> dpc => metro:4672
>
> links => i1:2 ==>>> this is because the trunk
> [physical level] is connect
> to port 2
>
>
>
> ****************************************************************************
> ************************************
>
>
>
> The Central ZTE J10 had COD SLC 0 and 1, The cic became in
> 1 example: 1- 31,
> and the file confg.c of SS7 the cic is configured to start
> in 1.
>
>
>
> ****************************************************************************
> **************************************
>
> If I send unblok of cic to PSTN to GW ss7, you cant view
> this message:
>
>
>
>
>
> [Sep 26 07:30:36] WARNING[3760]: l4isup.c:385
> mtp_enqueue_isup_packet: MTP
> send fifo not ready.
>
> [Sep 26 07:30:51] NOTICE[3760]: l4isup.c:2275
> handle_GRS_send_hwblock: Got
> GROUP RESET message, opc=0x1240, dpc=0x1241, sls=0x1,
> cic=1, range=9.
>
> [Sep 26 07:30:51] WARNING[3760]: l4isup.c:385
> mtp_enqueue_isup_packet: MTP
> send fifo not ready.
>
> [Sep 26 07:31:14] WARNING[3760]: mtp.c:914 timeout_sltm_t1:
> No SLTA received
> within Q.707 timer T1, trying again on link 'i1'.
>
> [Sep 26 07:31:22] NOTICE[3760]: l4isup.c:2275
> handle_GRS_send_hwblock: Got
> GROUP RESET message, opc=0x1240, dpc=0x1241, sls=0x1,
> cic=1, range=9.
>
> [Sep 26 07:31:22] WARNING[3760]: l4isup.c:385
> mtp_enqueue_isup_packet: MTP
> send fifo not ready.
>
> [Sep 26 07:31:23] ERROR[3760]: mtp.c:919 timeout_sltm_t1:
> No SLTA received
> within Q.707 timer T1, faulting link on link 'i1'.
>
> [Sep 26 07:31:36] NOTICE[3760]: l4isup.c:2275
> handle_GRS_send_hwblock: Got
> GROUP RESET message, opc=0x1240, dpc=0x1241, sls=0x1,
> cic=1, range=9.
>
> [Sep 26 07:31:36] WARNING[3760]: l4isup.c:385
> mtp_enqueue_isup_packet: MTP
> send fifo not ready.
>
>
>
> =========================================================================
>
> Connected to Asterisk 1.4.21.2 currently running on
> metross7 (pid = 22594)
>
> [Oct 10 11:49:35] WARNING[22609]: l4isup.c:1246
> t23_timeout: T23 timeout (No
> "ci rcuit group reset
> acknowledge" from peer) CIC=1.
>
> [Oct 10 11:49:35] WARNING[22609]: l4isup.c:385
> mtp_enqueue_isup_packet: MTP
> send fifo not ready
>
> [Oct 10 11:49:35] WARNING[22609]: l4isup.c:1246
> t23_timeout: T23 timeout (No
> "ci rcuit group reset
> acknowledge" from peer) CIC=17.
>
> [Oct 10 11:49:35] WARNING[22609]: l4isup.c:385
> mtp_enqueue_isup_packet: MTP
> send fifo not ready
>
>
According to this log, I'm not sure that your link is in service. I would suggest you to run "ss7 link status" after getting this error. I have some experience with trunks going down after a few seconds of INSERVICE state.
If you run zttool, what do you get?
>
> ****************************************************************************
> **************************************
>
> metross7*CLI> ss7 mtp data
>
> [Oct 10 11:51:41] ERROR[22609]: mtp.c:870 mtp2_queue_msu:
> Got illegal MSU
> length 0 < 2, dropping frame on link 'i1'.
>
> metross7*CLI>
>
>
>
> ****************************************************************************
> ***********************
>
>
>
>
>
> What do you said about it
>
>
>
> Thank for you help.
>
>
>
> _______________________________________________
> --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
Hope this helps.
Best regards, Tom?s Peralta.
Yahoo! Cocina
Recetas pr?cticas y comida saludable
http://ar.mujer.yahoo.com/cocina/
|