<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Grant Arix wrote:
<blockquote cite="mid:241009.80883.qm@web24006.mail.ird.yahoo.com"
type="cite">
<pre wrap="">Hi,
could you paste your ss7.conf here so that i can see it ?
Thanx.
</pre>
</blockquote>
I've bin trying and searching through the source code, and I currently
have this:<br>
<br>
So the connection should be:<br>
1 x E1 link a to PC 299 (KPN-Rt).<br>
1 x E1 link b to PC 300 (KPN-Ut).<br>
<br>
Both links have signalling on timeslot 16.<br>
<br>
But that's only signalling.<br>
The voice channels should be connected to PC 110 and PC 111.<br>
This moring i discovered that the ISUP traffic from both PC 110 and PC
111 are received<br>
through the signalling link on link a.<br>
<br>
The lines on link a connected to PC 111 are Idle, and yesterday we even
had a succesfull call over it.<br>
Bot the lines on link a are still in 'reset pending'.<br>
<br>
What I see is:<br>
Our side sends the GRS (reset) to PC 111 and PC 110.<br>
Both answer with GRA (ack.), but incoming on link a.<br>
The chan_ss7 looks up the CIC code from that link (link a).<br>
For the GRA from PC 111, this is ok.<br>
One step further (in process_isup_messages()).<br>
The msg->opc is checked with the linkset->dpc.<br>
And that's where it goes wrong. because the linkset (KPN-Rt) belonging
to link PC111, from the E1 link a) is 111.<br>
And the GRA just received over that link has a source PC of 110.<br>
<br>
By searching a little furhter...<br>
In l4isup_event(), the ss7_chan is filled with the return value of
find_pvt.<br>
This only used the link and the CIC.<br>
<br>
Because the CIC in my situation is for both links the same (1-15,17-31).<br>
The find_pvt returns link a, because the CIC exists.<br>
<br>
So I think we have two ways:<br>
1) change something in chan_ss7 to return the correct channel (on
combined linkset) by supplying the peer PC to find_pvt<br>
2) Or ask my local telco to change the CIC on PC 110 to 33-47,49-63<br>
<br>
<br>
Oh, and in my config, Ignore the PC229 and PC300 links.<br>
I just created them, so the PC110 en PC111 would get a SLS of 1 (PC229
an PC300 should have an sls of 0).<br>
But the PC229 and PC300 are not linked to a zaptel span, because the
software only allows max. 1 link per span.<br>
<br>
<br>
Thnx,<br>
Robert<br>
<br>
== /etc/asterisk/ss7.conf ==<br>
[linkset-KPN-Rt]<br>
enabled => yes ; The linkset is enabled<br>
enable_st => no ; The end-of-pulsing (ST) is
not used to determine when incoming address is complete<br>
use_connect => yes ; Reply incoming call with
CON rather than ACM and ANM<br>
hunting_policy => even_mru ; The CIC hunting policy
(even_mru, odd_lru, seq_lth, seq_htl) is even CIC numbers, most
recently used<br>
context => from-ss7-kpnglasvezel ; Incoming calls are placed
in the ss7 context in the asterisk dialplan<br>
language => nl ; The language for this
context is da<br>
subservice => auto ; The subservice field:
national (8), international (0), auto or decimal/hex value<br>
; The auto means that the
subservice is obtained from first received SLTM<br>
loadshare => combined<br>
combined => set-KPN-RTKPN-Ut<br>
<br>
[linkset-KPN-Ut]<br>
enabled => yes ; The linkset is enabled<br>
enable_st => no ; The end-of-pulsing (ST) is
not used to determine when incoming address is complete<br>
use_connect => yes ; Reply incoming call with
CON rather than ACM and ANM<br>
hunting_policy => even_mru ; The CIC hunting policy
(even_mru, odd_lru, seq_lth, seq_htl) is even CIC numbers, most
recently used<br>
context => from-ss7-kpnglasvezel ; Incoming calls are placed
in the ss7 context in the asterisk dialplan<br>
language => nl ; The language for this
context is da<br>
subservice => auto ; The subservice field:
national (8), international (0), auto or decimal/hex value<br>
; The auto means that the
subservice is obtained from first received SLTM<br>
loadshare => combined<br>
combined => set-KPN-RTKPN-Ut<br>
<br>
[link-PC299]<br>
enabled => yes ; The link is enabled<br>
linkset => KPN-Rt ; This link belongs to
linkset siuc<br>
channels => ; The speech/audio circuit
channels on this link<br>
schannel => 16 ; The signalling channel<br>
firstcic => 1 ; The first CIC<br>
sltm => no<br>
<br>
[link-PC111]<br>
enabled => yes<br>
linkset => KPN-Rt<br>
channels => 1-15,17-31<br>
schannel => 16<br>
firstcic => 1<br>
sltm => no<br>
<br>
[link-PC300]<br>
enabled => yes ; The link is enabled<br>
linkset => KPN-Ut ; This link belongs
to linkset siuc<br>
channels => ; The speech/audio circuit channels
on this link<br>
schannel => 16 ; The signalling channel<br>
firstcic => 1 ; The first CIC<br>
sltm => no<br>
<br>
[link-PC110]<br>
enabled => yes<br>
linkset => KPN-Ut<br>
channels => 1-15,17-31<br>
schannel => 16<br>
firstcic => 1<br>
sltm => no<br>
<br>
[host-calcium.exa-omicron.nl]<br>
enabled => yes ; The host is enabled<br>
opc => 576 ; The point code for this
SS7 signalling point is 0x8e0<br>
;dpc => KPN-Rt:299,KPN-Ut:300 ; The destination point
(peer) code is 0x3fff for linkset siuc<br>
dpc =>
KPN-Rt:111,KPN-Ut:110,PC299:299,PC300:300,PC111:111,PC110:110 ; The
destination point (peer) code is 0x3fff for linkset siuc<br>
;links => PC111:1,PC299:1,PC110:2,PC300:2 ; Syntax:
links => link-name:digium-connector-no<br>
links => PC111:1,PC110:2 ; Syntax: links =>
link-name:digium-connector-no<br>
; The links on the host is
'l1', connected to span/connector #1<br>
if-1 => 127.0.0.1<br>
default_linkset=KPN-Rt<br>
<br>
<div class="moz-signature">-- <br>
<title></title>
<b>Exa-Omicron</b><br>
Patroonsweg 10<br>
3892 DB Zeewolde<br>
Tel.: 088-OMICRON (66 427 66)<br>
<a href="http://www.exa-omicron.nl">http://www.exa-omicron.nl</a><br>
</div>
</body>
</html>