linkset and CIC configuration

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,
once you define sigchan - all channels (CICs) defined before that are 
used for that link. When you define new channels after that - they will 
belong to the next one.
Just move the block below at the end and you are done:

ss7type=itu
networkindicator=national
linkset=1
pointcode=4
adjpointcode=1
defaultdpc=3
sigchan=1
sigchan=32
ss7type=itu
networkindicator=national
linkset=2
pointcode=4
adjpointcode=2
defaultdpc=3
sigchan=63
sigchan=94

P.S. To actually use SS7 timers you need to define them for each linkset 
... just use "#include ss7.timers" for each one after sigchans

On 2013-08-13 10:13, Frederic Van Espen wrote:
> Hi,
> 
> I have 5 E1's connected to my asterisk box. These are connected to 2
> STP's (pointcodes 1 and 2) through a MGW. Behind the STP's there's an
> MSC (pointcode 3). Our box is assigned pointcode 4.
> 
> The first channel of the first 4 E1's are signalling channels. The
> first 2  E1's are set towards STP1, the 2 following towards STP2. The
> fifth one is not clear to me where it is going (Does it matter?
> There;s only CIC's on this E1) How would I go about configuring
> chan_dahdi.conf? I'm using the patched asterisk 11.5.0 with the
> patched libss7 as described in
> https://issues.asterisk.org/jira/browse/SS7-27?focusedCommentId=208465&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-208465
> 
> 
> Here's what I currently have:
> [channels]
> 
> switchtype=EuroISDN
> context=incoming
> group=1
> 
> ss7type=itu
> signalling=ss7
> networkindicator=national
> linkset=1
> pointcode=4
> adjpointcode=1
> defaultdpc=3
> sigchan=1
> sigchan=32
> ss7type=itu
> networkindicator=national
> linkset=2
> pointcode=4
> adjpointcode=2
> defaultdpc=3
> sigchan=63
> sigchan=94
> 
> 
> ss7_called_nai=national
> ss7_calling_nai=national
> ss7_internationalprefix=
> ss7_nationalprefix=
> ss7_subscriberprefix=
> ss7_unknownprefix=
> echocancel=yes
> echocancelwhenbridged=no
> echotraining=no
> 
> pridialplan=unknown
> prilocaldialplan=unknown
> 
> cicbeginswith=34
> channel=2-31
> cicbeginswith=66
> channel=33-62
> cicbeginswith=98
> channel=64-93
> cicbeginswith=130
> channel=95-124
> cicbeginswith=161
> channel=125-155
> 
> For some incoming IAM's I see this in the logs:
> [Aug 13 09:07:31] VERBOSE[31407] sig_ss7.c: [Aug 13 09:07:31] Linkset
> 0: Processing event: ISUP_EVENT_IAM
> 
> Linkset 0! It seems like asterisk can not detect the linkset on which
> theis message entered.
> 
> Any thoughts and/or recommendations?
> 
> Thanks,
> 
> Frederic
> 
> --
> _____________________________________________________________________
> -- 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



[Index of Archives]     [Asterisk App Development]     [PJ SIP]     [Gnu Gatekeeper]     [IETF Sipping]     [Info Cyrus]     [ALSA User]     [Fedora Linux Users]     [Linux SCTP]     [DCCP]     [Gimp]     [Yosemite Backpacking]     [Deep Creek Hot Springs]     [Yosemite Campsites]     [ISDN Cause Codes]     [Asterisk Books]

  Powered by Linux