Hi,
I am sorry for writing you again with the same email . But I need this
feature extremely and I believe lots of people in the world are waiting
for this nice feature .
Could anyone focus on this topics please ?
Best regards,
..Tusar..
---------- Forwarded message ----------
From: Tusar <[EMAIL PROTECTED]>
Date: Mar 31, 2007 12:57 PM
Subject: Re: [asterisk-ss7] Two Asterisk boxes, only ONE signal link
To: [email protected]
Hi,
I am trying to configure using one signaling link with multiple asterisk box
where I have only one signaling link from Telco company .
Astreisk_1 --> SS7 Signalining --> Telco
/
Astreisk_2--/ ---> Bearer Channel --> Telco
I have patched the "cluster.c" provided from [Anders Baekgaard <[EMAIL
PROTECTED]>]
.
--- cluster.c~ 2006-04-19 09:54:08.000000000 +0200
+++ cluster.c 2007-03-23 09:51: 25.000000000 +0100
@@ -847,9 +847,8 @@
}
}
- if (this_host->has_signalling_receivers)
- if (setup_receiver_socket())
- goto fail;
+ if (setup_receiver_socket())
+ goto fail;
connect_receivers();
receivepipe[0] = receivepipe[1] = -1;
receivebuf = lffifo_alloc(200000);
Asterisk_1 box is running fine and seems "cluster service" is connected each
other but Asterisk_2 is complaing ..
"Mar 31 12:43:05 NOTICE[9666]: l4isup.c:1076 t22_timeout: T22 timeout (No
"circuit group reset acknowledge" from peer) CIC=32.
Mar 31 12:43:05 WARNING[9666]: mtp.c:1708 mtp_thread_main: No signalling
links inservice and no cluster receivers alive, dropping packet!
"
Asterisk_1
===========
*CLI> ss7 cluster status
receiver Asterisk_1 if 1, addr 192.168.10.17, c:connected, p:, last try 154
msec, 23 fails, 0 forwards
*CLI>
Asterisk_2
===========
*CLI> ss7 cluster status
receiver Asterisk_2 if 1, addr 192.168.10.16, c:connected, p:, last try 399
msec, 0 fails, 0 forwards
*CLI>
Here is below my config file for both the box ...
Asterisk_1 [IP:192.168.10.16]
=======================
[linkset-siuc]
enabled => yes
enable_st => no
use_connect => yes
hunting_policy => even_mru
subservice => auto
[link-l1]
linkset => siuc
channels => 1-15,17-31
schannel => 16
firstcic => 1
enabled => yes
[host-Asterisk_1]
enabled => yes
default_linkset => siuc
opc => 0x2
dpc => siuc:0x1
if-1 => 192.168.10.17
links => l1:1
[cluster]
port => 5040
l1 => Asterisk_2#if-1
Asterisk_2 [IP:192.168.10.17]
======================
[linkset-siuc]
enabled => yes
enable_st => no
use_connect => no
hunting_policy => even_mru
subservice => auto
[link-l2]
linkset => siuc
channels => 1-31
schannel =>
firstcic => 32
enabled => yes
[host-Asterisk_2]
enabled => yes
default_linkset => siuc
opc => 0x2
dpc => siuc:0x1
if-1 => 192.168.10.16
links => l2:1
[cluster]
port => 5040
l2 => Asterisk_1#if-1
Could anyone please push me to right direction to sort out this issue
resolve .
Best Regards,
..Tusar..
On 3/23/07, Anders Baekgaard <[EMAIL PROTECTED]> wrote:
Hi Daniel
Yes, a "fake" signalling channel is a work aound. The patch below is also
a
work around..
--- cluster.c~ 2006-04-19 09:54:08.000000000 +0200
+++ cluster.c 2007-03-23 09:51:25.000000000 +0100
@@ -847,9 +847,8 @@
}
}
- if (this_host->has_signalling_receivers)
- if (setup_receiver_socket())
- goto fail;
+ if (setup_receiver_socket())
+ goto fail;
connect_receivers();
receivepipe[0] = receivepipe[1] = -1;
receivebuf = lffifo_alloc(200000);
Best regards
Anders Baekgaard
_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --
asterisk-ss7 mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-ss7
