Hi,

According the the messages below you received a Status Indication "Out of Service" from the remote end. You need to check what is happening at the remote end and why they are sending a SIOS to you.

Best Regards,
Amish


On 04/18/2010 11:36 PM, Goke M Aruna wrote:
Thanks Amish,

I do not know anything about the 1538, however, from the console i got this message.

i dont have my schannels set as 15 but 16.

Thanks

================================================================================================
[Apr 16 13:59:53] NOTICE[20466]: l4isup.c:2354 ss7_read: Audio buffer underrun, data 20 msecs, real time: 123 msecs! (supressed 0) [Apr 16 13:59:53] NOTICE[20418]: l4isup.c:2423 ss7_write: Write buffer full on CIC=21 (wrote only 0 of 160), audio lost (suppress 0). [Apr 16 13:59:53] NOTICE[20436]: l4isup.c:2423 ss7_write: Write buffer full on CIC=47 (wrote only 0 of 160), audio lost (suppress 0). [Apr 16 13:59:53] NOTICE[17618]: mtp.c:1091 mtp2_process_lssu: Got status indication 'OS' while INSERVICE on link 'l1'. [Apr 16 13:59:53] WARNING[17618]: chan_ss7.c:126 process_event: MTP is now DOWN on link 'l1'. [Apr 16 13:59:53] NOTICE[17618]: mtp.c:637 mtp_changeover: MTP changeover last_ack=6, last_sent=7, from schannel 15, no INSERVICE schannel found [Apr 16 13:59:53] NOTICE[17618]: mtp.c:641 mtp_changeover: Failover not possible, no other signalling link and no other host available. [Apr 16 13:59:53] WARNING[17618]: chan_ss7.c:126 process_event: MTP is now DOWN on link 'l1'.
    -- SS7 hangup 'SS7/ewsd/37' CIC=37 Cause=0 (state=4)
== Spawn extension (gts, 08089073468, 1) exited non-zero on 'SIP/222-00000ae5' [Apr 16 13:59:54] WARNING[17618]: mtp.c:2085 mtp_thread_main: No signalling links inservice and no cluster receivers alive, dropping packet!
    -- SS7 hangup 'SS7/ewsd/43' CIC=43 Cause=0 (state=4)

=========================================================================================================================


On Sun, Apr 18, 2010 at 9:39 PM, Amish <[email protected] <mailto:[email protected]>> wrote:

    Dear Goke,


    Where in the trace do the links fail?
    I see that at packet 954 and and 956 you receive a TFP, for point
    code 1538.

    A.



    On 04/18/2010 10:01 PM, Goke M Aruna wrote:
    Dear Amish,

    my ss7.conf

    [linkset-ewsd]
    enabled => yes
    enable_st => no
    use_connect => no
    hunting_policy => seq_lth
    subservice => auto
    language => en
    variant => ITU
    context => outbound
    ;sltm => no

    [link-l1]
    linkset => ewsd
    channels => 1-15,17-31
    schannel => 16
    firstcic => 1
    enabled => yes

    [link-l2]
    linkset => ewsd
    channels => 1-15,17-31
    schannel =>
    firstcic => 33
    enabled => yes

    [link-l3]
    linkset => ewsd
    channels => 1-15,17-31
    schannel =>
    firstcic => 65
    enabled => yes

    [link-l4]
    linkset => ewsd
    channels => 1-15,17-31
    schannel =>
    firstcic => 97
    enabled => yes


    [host-brooks1]
    enabled => yes
    opc => 1366
    dpc => ewsd:1304
    links => l1:1,l2:2,l3:3,l4:4

    the setup is as below.

    [ IP SIP calls] <== (ethernet / internet) ==> [asterisk /
    chan_ss7 box PC=1366] <==(ss7 link (1 signalling 4 E1s)) ==>
    [EWSD  PC=1304 ] <== (ss7 links) ==> [GSM / CDMA operators]

    Thanks

    On Sun, Apr 18, 2010 at 1:39 PM, Amish Chana <[email protected]
    <mailto:[email protected]>> wrote:

        Dear Goke,

        Can you post the ss7.conf file.
        Can you provide a diagram of the flow of voice calls and
        signalling?
        How are you generating the call traffic?
        >From the trace it looks like all the traffic is generated by
        point code 1366 and sent to 1304. How many signalling links
        do you have?
        I assume you have chan_ss7 at 1366? What protocol stack do
        you have at 1304?
        Where in the trace do the links fail?
        I see that at packet 954 and and 956 you receive a TFP, for
        point code 1538.

        Best Regards,
        Amish



        On 04/16/2010 07:28 PM, Goke M Aruna wrote:
        Amish,

        Thanks everybody for your response so far.

        however, after loading the call to certain 78 simultaneous
        calls and the signalling just failed and the dump is as
        attached.
        I tried disabling the sltm, asterisk refuse to start giving
        me the error "unknown options".

        kindly help.



        On Wed, Apr 14, 2010 at 8:44 PM, Goke M Aruna
        <[email protected] <mailto:[email protected]>> wrote:

            Log messages.

            On 4/14/10, Amish <[email protected]
            <mailto:[email protected]>> wrote:
            > On 04/14/2010 02:32 AM, Goke M Aruna wrote:
            >> Thanks Amish,
            >>
            >> the links have been up for the last 4 hours with
            minor error util.c :
            >> failed to delete timer.
            >>
            > Hi,
            >
            > Where this this error appear? The asterisk messages
            file or the console?
            > I don't see this error in my
            /var/log/asterisk/messages file.
            >
            > Cheers,
            > A.
            >
            >

            --
            Sent from my mobile device







<<attachment: amish.vcf>>

-- 
_____________________________________________________________________
-- 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

Reply via email to