I understand that it should work. But not having deployed it myself, it is nice to get confirmation from a live setup. On a different note, cluster setup is not possible if running mtp3d. As a matter of academic curiosity, will the same signalling channel work across boxes if cluster is deployed? Regards HASSAN On 7/17/09, Vashkar <vashkar at gmail.com> wrote: > it must work on 8 or more E1's > > only thing is to get the signalling server from all the system and using > cluster > > -Vashkar > > On Fri, Jul 17, 2009 at 3:28 AM, Nyamul Hassan <mnhassan at usa.net> wrote: > >> Hi Antoine, >> >> Did you get around to using this setup with full 8 E1s? >> >> It would be very helpful if you could post your results. >> >> Regards >> HASSAN >> >> >> On Wed, Apr 8, 2009 at 2:22 AM, Antoine Megalla<aatef at rocketmail.com> >> wrote: >> > >> > Thank you Anders, >> > >> > It seems like it is working now. >> > Although I could not test with the full 8 E1s, but I tested on 2 E1s, >> > one >> in each server and it is working. >> > >> > When I test with the 8 E1s I will report back. >> > >> > Thank you and best regards, >> > >> > Antoine Megalla. >> > >> > >> > >> > ----- Original Message ---- >> > From: Anders Baekgaard <ab at dicea.dk> >> > To: asterisk-ss7 at lists.digium.com >> > Sent: Thursday, April 2, 2009 3:05:25 PM >> > Subject: Re: [asterisk-ss7] chan_ss7 signalling across multiple servers >> > >> > The config spec looks correct. >> > >> > You will not need a [cluster] section when you use mtp3d to transport >> > signaling for multiple servers. >> > >> > You can also configure a cluster using the [cluster] section, and then >> not use >> > mtp3d. There is a template ss7.conf for that in the source distribution. >> > >> > The method of configuring clusters using the [cluster] section is the >> > old >> > approach. The newer approach of using mtp3d was introduced as a step >> towards >> > supporting SIGTRAN, and for support of sharing transport for other >> protocols >> > like GSM MAP and INAP. >> > >> > Best regards, >> > -- >> > Anders Baekgaard >> > Managing Director, Dicea ApS >> > Esromgade 15, 1110 >> > DK-2200 Copenhagen N >> > Denmark >> > Tel: +45 46931411 >> > Fax: +45 46931466 >> > Mobile: +45 20771844 >> > >> > On Thursday 02 April 2009 14:03:00 Antoine Megalla wrote: >> >> Hi, >> >> >> >> So I wrote 1 ss7.conf for both servers as suggested, I just need >> comments >> >> if the file looks correct, or if it missing anything: Do I need a >> [cluster] >> >> section in the file: >> >> >> >> Here is my ss7.conf file: >> >> >> >> [linkset-MSC1] >> >> enabled => yes >> >> enable_st => no >> >> use_connect => yes >> >> hunting_policy => seq_htl >> >> subservice => auto >> >> context => ss7 >> >> language => en >> >> t35 => 15000,timeout >> >> >> >> [link-l1] >> >> linkset => MSC1 >> >> channels => 1-15,17-31 >> >> schannel => 16,host1:12000 >> >> firstcic => 1 >> >> echocancel => no >> >> echocan_train => 350 >> >> echocan_taps => 128 >> >> enabled => yes >> >> >> >> [link-l2] >> >> linkset => MSC1 >> >> channels => 1-31 >> >> schannel => >> >> firstcic => 33 >> >> echocancel=allways >> >> echocan_taps=32 >> >> echocan_train=350 >> >> enabled => yes >> >> >> >> [link-l3] >> >> linkset => MSC1 >> >> channels => 1-31 >> >> schannel => >> >> firstcic => 65 >> >> echocancel=no >> >> echocan_taps=32 >> >> echocan_train=350 >> >> enabled => yes >> >> >> >> [link-l4] >> >> linkset => MSC1 >> >> channels => 1-31 >> >> schannel => >> >> firstcic => 97 >> >> echocancel=no >> >> echocan_taps=32 >> >> echocan_train=350 >> >> enabled => yes >> >> >> >> [link-l5] >> >> linkset => MSC1 >> >> channels => 1-31 >> >> schannel => >> >> firstcic => 129 >> >> echocancel=no >> >> echocan_taps=32 >> >> echocan_train=350 >> >> enabled => yes >> >> >> >> [link-l6] >> >> linkset => MSC1 >> >> channels => 1-31 >> >> schannel => >> >> firstcic => 161 >> >> echocancel=no >> >> echocan_taps=32 >> >> echocan_train=350 >> >> enabled => yes >> >> >> >> [link-l7] >> >> linkset => MSC1 >> >> channels => 1-31 >> >> schannel => >> >> firstcic => 193 >> >> echocancel=no >> >> echocan_taps=32 >> >> echocan_train=350 >> >> enabled => yes >> >> >> >> [link-l8] >> >> linkset => MSC1 >> >> channels => 1-31 >> >> schannel => >> >> firstcic => 225 >> >> echocancel=no >> >> echocan_taps=32 >> >> echocan_train=350 >> >> enabled => yes >> >> >> >> [host-host1] >> >> enabled => yes >> >> default_linkset => MSC1 >> >> opc => 1000 >> >> dpc => MSC1:2000 >> >> links => l1:1,l2:2,l3:3,l4:4 >> >> if-1 => 10.0.0.1 >> >> >> >> [host-host2] >> >> enabled => yes >> >> default_linkset => MSC1 >> >> opc => 1000 >> >> dpc => MSC1:2000 >> >> links => l5:1,l6:2,l7:3,l8:4 >> >> if-1 => 10.0.0.2 >> >> >> >> >> >> Appreciate your comments, >> >> >> >> Regards, >> >> >> >> Antoine Megalla. >> >> >> >> >> >> >> >> >> >> ----- Original Message ---- >> >> From: Anders Baekgaard <ab at dicea.dk> >> >> To: asterisk-ss7 at lists.digium.com >> >> Sent: Thursday, April 2, 2009 12:03:57 PM >> >> Subject: Re: [asterisk-ss7] chan_ss7 signalling across multiple servers >> >> >> >> Assuming link 'l1' has signaling on ts 16, and this is connected on >> server >> >> 'host1', you will write >> >> >> >> [link-l1] >> >> ... >> >> schannel => 16, host1:12000 >> >> ... >> >> >> >> >> >> You must specify this on both servers. It is easiest to have the same >> >> configuration specification (ss7.conf) on both servers. chan_ss7 will >> >> forward signaling using TCP/IP to 'host1', port 12000, so you must >> ensure >> >> mtp3d is running on that server. >> >> >> >> Best regards, >> > >> > >> > _______________________________________________ >> > --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 >> > >> > >> > >> > >> > >> > _______________________________________________ >> > --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 >> > >> > >> >> _______________________________________________ >> --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 >> >