Hi All, I'm in the lab with sip router 3.0 mocking up some trunk-group prefix routing with PDT and load balancing with Dispatcher. This is working great and as expected. I would like to incorporate some sort of LCR matching on NPA-NXX but I'm having some difficulty. The PDT module automatically strips the prefix so for trunk group routing it works great but really can't be used for matching NPA-NXX. The Carrierroute module is pretty nice and works as expected but the issue I'm having, it appears that I have to have a NPA-NXX entry for each domain gateway I want to send calls to. For instance if I have 3 gateways in domain 1, then I would need the same NPA-NXX record entry in the database for each gateway. The database entries would be [NPA-NXX] x [Number of Gateways] per domain. So having 100K routes would mean having 300K records. Am I looking at this correctly? This is really what it seems like to me but logically I would think this should not be the case? I really like the Dispatcher polling functions to actively know what gateways are on-line and off-line plus the different distribution algorithms to choose from. So it makes sense to me to implement a pseudo PDT/Distpacher scenario as an LCR but with PDT stripping the prefix, that can not be done. Is there another mechanism whereby I can dip the database looking for the NPA-NXX, extract the domain group and send that to the Dispatcher function, without stripping the prefix? Or can a PDT module parameter be added to not strip the prefix. But I'm not sure this will work, can the PDT module hold in memory a few hundred thousand records? Thanks. JR -- JR Richardson Engineering for the Masses _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users(a)lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Hi All, I'm in the lab with sip router 3.0 mocking up some trunk-group prefix routing with PDT and load balancing with Dispatcher.  This is working great and as expected.  I would like to incorporate some sort of LCR matching on NPA-NXX but I'm having some difficulty.  The PDT module automatically strips the prefix so for trunk group routing it works great but really can't be used for matching NPA-NXX.

The Carrierroute module is pretty nice and works as expected but the issue I'm having, it appears that I have to have a NPA-NXX entry for each domain gateway I want to send calls to.  For instance if I have 3 gateways in domain 1, then I would need the same NPA-NXX record entry in the database for each gateway.  The database entries would be [NPA-NXX] x [Number of Gateways] per domain.  So having 100K routes would mean having 300K records.  Am I looking at this correctly?  This is really what it seems like to me but logically I would think this should not be the case? I really like the Dispatcher polling functions to actively know what gateways are on-line and off-line plus the different distribution algorithms to choose from.  So it makes sense to me to implement a pseudo PDT/Distpacher scenario as an LCR but with PDT stripping the prefix, that can not be done.  Is there another mechanism whereby I can dip the database looking for the NPA-NXX, extract the domain group and send that to the Dispatcher function, without stripping the prefix? Or can a PDT module parameter be added to not strip the prefix.  But I'm not sure this will work, can the PDT module hold in memory a few hundred thousand records? Thanks. JR -- JR Richardson Engineering for the Masses