[asterisk-ss7] Asterisk, Taqua T7000, and you guessed it, SS7

[Paul Timmins]

I know it works fine on 6.1 (but I think I had it working on 5.0 too?)

I assume you have the trunk group configured like this:

TRUNKNAME
       +-- Trunk-1-X-X-X (when you click on this, you see CIC 26)
       +-- Trunk-2-X-X-X
(etc)
       +-- Trunk-23-X-X-X (When you click on this, you see CIC 48)

Also, when you go to ISUP in open manager and click on the point code, 
you see the range of 00026 through 00048 on the right pane.

Can you select all of those, right click and choose "Query Circuit 
Range" and let me know what that says?

-Paul

Bryan Scott wrote:
> Great.  Patch seems to work on the Asterisk side.  But Asterisk (and the switch) complain if the Taqua has anything but SLC 0.  If I use SLC 0 on the T7000 the link comes up, alarms clear, but the CIC's are still unconfigured.
>
> I'm *this* close to using simple PRI circuits.
>
> And Paul, the T7000 is on 6.0.0p20.  I still need to do the isupMsgTrace that you mentioned.  This is on an LTC card.
>
> -- Bryan
>
>
>
>
> On Fri, Apr 30, 2010 at 7:12 PM, Nahuel Greco <ngreco at gmail.com> wrote:
>   
>> Here you have a patch attached to set the link SLC using an "slc"
>> directive in chan_dahdi.conf. Try it and tell me if works.
>>
>> Saludos,
>> Nahuel Greco.
>>
>>
>>
>> On Fri, Apr 30, 2010 at 7:01 PM, Bryan Scott <sirbryan at gmail.com> wrote:
>>     
>>>>>>  Set your SS7 trunk to SLC 1. I couldn't make it work
>>>>>> on SLC 0. No idea why.
>>>>>>
>>>>>>             
>>>>> The Taqua is 1 too?  Regardless of Asterisk's setting, it shows the SLC 0.  Setting the Taqua to 1 causes the F-Link to go down and Asterisk complains.
>>>>>
>>>>>           
>>>> Yes. Both the taqua and the asterisk are set to SLC=1
>>>>
>>>>         
>>> It looks like Asterisk pays no attention to the "slc" setting in chan_dahdi.conf, but instead libss7 (in ss7.c) automagically calculates the Signaling Link Code based on how many are linksets have been defined:
>>>
>>>
>>> /* ****************** */
>>> // looks like we create a new mtp2 link and autoincrement the SLC counter
>>>
>>>                m = mtp2_new(fd, ss7->switchtype);
>>>
>>>                if (!m)
>>>                        return -1;
>>>
>>>                m->slc = ss7->numlinks;
>>>                ss7->numlinks += 1;
>>>                m->master = ss7;
>>>                if (zapmtp2)
>>>                        m->flags |= MTP2_FLAG_ZAPMTP2;
>>>
>>>                ss7->links[ss7->numlinks - 1] = m;
>>>
>>> /* ****************** */
>>>
>>> So changed it to add one (m->slc = ss7->numlinks + 1) and I'm getting MTP2 link issues:
>>>
>>> [Apr 30 16:01:04] WARNING[19051]: chan_dahdi.c:11509 ss7_linkset: MTP2 link down (SLC 1)
>>> MTP2 link up (SLC 1)
>>> [Apr 30 16:01:06] WARNING[19051]: chan_dahdi.c:11509 ss7_linkset: MTP2 link down (SLC 1)
>>> MTP2 link up (SLC 1)
>>> [Apr 30 16:01:09] WARNING[19051]: chan_dahdi.c:11509 ss7_linkset: MTP2 link down (SLC 1)
>>>
>>>
>>>
>>>
>>> --
>>> _____________________________________________________________________
>>> -- 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
>>>
>>>       
> <libss7.configure_slc.patch>-- 
> _____________________________________________________________________
> -- 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
>
>
>