I think that this arrangement should work, 3 gws with different "tags", it should do a load balancing among the 3 gws and append an specific "tag" to each gw <br>556233 for gw1<br>1 for gw2<br>nothing for gw3<br>
<br>I do not know about using "#" as part of the URI, <br><br>regards<br><br>jp<br><br><br>lcr routes<br>+----+-----------------+----------+--------+----------+<br>| id | prefix | from_uri | grp_id | priority |<br>
+----+-----------------+----------+--------+----------+<br>| 1 | 5555551212 | | 1 | 1 |<br>| 2 | 5555551212 | | 2 | 1 | <br>| 3 | 5555551212 | | 3 | 1 | <br>
+----+-----------------+----------+--------+----------+<br>lcr gateways<br>+-----------+--------------+------+------------+-----------+--------+-------+-------+-------+<br>| gw_name | ip_addr | port | uri_scheme | transport | grp_id | strip | tag | flags |<br>
+-----------+--------------+------+------------+-----------+--------+-------+-------+-------+<br>| gw1 | ip_gw_1 | 5060 | 1 | 1 | 1 | 0 |556233 | 0 | <br>| gw2 | ip_gw_2 | 5060 | 1 | 1 | 2 | 0 | 1 | 0 | <br>
| gw3 | ip_gw_3 | 5060 | 1 | 1 | 3 | 0 | | 0 | <br>+-----------+--------------+------+------------+-----------+--------+-------+-------+-------+<br>[root@proxy1 ~]#<br>[root@proxy1 ~]#<br>
<br><br>On Thu, Mar 5, 2009 at 3:03 PM, Geoffrey Mina <<a href="mailto:geoffreymina@gmail.com">geoffreymina@gmail.com</a>> wrote:<br>><br>> Thanks! I hadn't seen that before. I have another semi-related<br>
> question about LCR. I have multiple gateways, each require me to<br>> prefix the dial string with a specific account ID or rule.<br>><br>> i.e. to dial the phone number 5555551212 I would need to do the following:<br>
><br>> gateway 1:<br>> #556233#<a href="mailto:5555551212@mygateway1.com">5555551212@mygateway1.com</a><br>><br>> gateway 2:<br>> +<a href="mailto:15555551212@mygateway2.com">15555551212@mygateway2.com</a><br>
><br>> gateway3 :<br>> <a href="mailto:5555551212@mygateway3.com">5555551212@mygateway3.com</a><br>><br>> Is there any way the LCR system can account for this, or will I need<br>> to build some custom functionality to make this work?<br>
><br>> Thanks,<br>> Geoff<br>><br>> On Thu, Mar 5, 2009 at 2:24 PM, Daniel-Constantin Mierla<br>> <<a href="mailto:miconda@gmail.com">miconda@gmail.com</a>> wrote:<br>> > Hello,<br>> ><br>
> > On 03/05/2009 09:03 PM, Geoffrey Mina wrote:<br>> >><br>> >> Hello,<br>> >> I am currently deploying the LCR module. I have some questions about<br>> >> fields and what they do... I searched the docs, but couldn't find<br>
> >> anything. Can someone please fill in the blanks?<br>> >><br>> ><br>> > have you seen (I forced a regeneration to be sure is up to date):<br>> > <a href="http://kamailio.org/docs/db-tables/kamailio-db-devel.html#GEN-DB-GW">http://kamailio.org/docs/db-tables/kamailio-db-devel.html#GEN-DB-GW</a><br>
> ><br>> > Cheers,<br>> > Daniel<br>> ><br>> >> [LCR Gateways]<br>> >> Gateway Name: description of the gateway<br>> >> Group ID: Numeric identifier used to link LCR Rules<br>
> >> IP Address: The IP of the SIP gateway<br>> >> Hostname: The hostname of the SIP gateway (not required if IP provided?)<br>> >> Port: The port the SIP gateway listens on<br>> >> URI Scheme: (well documented) NULL = sip, 1 = sip and 2 = sips<br>
> >> Transport: (well documented) NULL = none, 1 = udp, 2 = tcp, 3 = tls,<br>> >> and 4 = sctp<br>> >> Strip: ?<br>> >> Tag: ?<br>> >> Weight: ?<br>> >> Ping: ?<br>> >> Flags: ?<br>
> >><br>> >> [LCR Rules]<br>> >> Prefix: The matching prefix. In the US most would do this by area<br>> >> code, so I would assume I would put something like 1678 or 1770 to<br>> >> route Atlanta calls. Would putting a NULL or Empty String force a<br>
> >> default route for everything?<br>> >> >From URI: If I don't care about the from URI can I leave this NULL or<br>> >> BLANK?<br>> >> Group ID: The numeric identifier matching to LCR Gateways<br>
> >> Priority: I am assuming if there are 2 records which match the prefix<br>> >> and from URI the high priority will be chosen first?<br>> >><br>> >> Also, say for example, one of my gateway providers has a primary and a<br>
> >> secondary gateway. If the primary is down I need to route calls to<br>> >> the secondary. How would this fit into an LCR scheme? Would I need<br>> >> duplicate routes for the secondary with a lower priority?<br>
> >><br>> >> Thanks,<br>> >> Geoff<br>> >><br>> >> p.s. for anyone holding out, I just installed Siremis today and it<br>> >> rocks! I am really quite pleased with the solution.<br>
> >><br>> >> _______________________________________________<br>> >> Kamailio (OpenSER) - Users mailing list<br>> >> <a href="mailto:Users@lists.kamailio.org">Users@lists.kamailio.org</a><br>
> >> <a href="http://lists.kamailio.org/cgi-bin/mailman/listinfo/users">http://lists.kamailio.org/cgi-bin/mailman/listinfo/users</a><br>> >> <a href="http://lists.openser-project.org/cgi-bin/mailman/listinfo/users">http://lists.openser-project.org/cgi-bin/mailman/listinfo/users</a><br>
> >><br>> >><br>> ><br>> > --<br>> > Daniel-Constantin Mierla<br>> > <a href="http://www.asipto.com">http://www.asipto.com</a><br>> ><br>> ><br>><br>> _______________________________________________<br>
> Kamailio (OpenSER) - Users mailing list<br>> <a href="mailto:Users@lists.kamailio.org">Users@lists.kamailio.org</a><br>> <a href="http://lists.kamailio.org/cgi-bin/mailman/listinfo/users">http://lists.kamailio.org/cgi-bin/mailman/listinfo/users</a><br>
> <a href="http://lists.openser-project.org/cgi-bin/mailman/listinfo/users">http://lists.openser-project.org/cgi-bin/mailman/listinfo/users</a><br><br>