In that case, dialplan is not what you want. Use carrierroute, lcr, or do your own queries with sqlops.

-- Sent from mobile device

On May 25, 2009, at 9:05 AM, Bruce Ferrell bferrell@baywinds.org wrote:

Can you point me to some examples of how to use dialplan?

I want to be able to direct traffic to carrier gateways based on the dial digits and not have to change the config file and bring kamailio down to do it. I always thought that was silly.

Alex Balashov wrote:

...

Depends on what precisely you mean by "dial plans," but there is the "dialplan" module.

What do you want to accomplish?

-- Sent from mobile device

On May 24, 2009, at 8:23 PM, Bruce Ferrell bferrell@baywinds.org wrote:

...

I've spent many hours looking over the module docs and examples.

is there a way to do dialplans from a database?

Thanks

---

Kamailio (OpenSER) - Users mailing list Users@lists.kamailio.org http://lists.kamailio.org/cgi-bin/mailman/listinfo/users http://lists.openser-project.org/cgi-bin/mailman/listinfo/users

---

Kamailio (OpenSER) - Users mailing list Users@lists.kamailio.org http://lists.kamailio.org/cgi-bin/mailman/listinfo/users http://lists.openser-project.org/cgi-bin/mailman/listinfo/users

On 05/25/2009 06:09 PM, Bruce Ferrell wrote:

Those seem useful suggestions and give me a direction in which to look.

Thanks Alex

Alex Balashov wrote:

...

In that case, dialplan is not what you want. Use carrierroute, lcr,

dispatcher and pdt are other modules that can help in routing decisions.

...

or do your own queries with sqlops.

Alternative for those willing to avoid of sql queries is to use htable module and build a cache.

Cheers, Daniel

...

-- Sent from mobile device

On May 25, 2009, at 9:05 AM, Bruce Ferrell bferrell@baywinds.org wrote:

...

Can you point me to some examples of how to use dialplan?

I want to be able to direct traffic to carrier gateways based on the dial digits and not have to change the config file and bring kamailio down to do it. I always thought that was silly.

Alex Balashov wrote:

...

Depends on what precisely you mean by "dial plans," but there is the "dialplan" module.

What do you want to accomplish?

-- Sent from mobile device

On May 24, 2009, at 8:23 PM, Bruce Ferrell bferrell@baywinds.org wrote:

...

I've spent many hours looking over the module docs and examples.

is there a way to do dialplans from a database?

Thanks

---

Kamailio (OpenSER) - Users mailing list Users@lists.kamailio.org http://lists.kamailio.org/cgi-bin/mailman/listinfo/users http://lists.openser-project.org/cgi-bin/mailman/listinfo/users

---

Kamailio (OpenSER) - Users mailing list Users@lists.kamailio.org http://lists.kamailio.org/cgi-bin/mailman/listinfo/users http://lists.openser-project.org/cgi-bin/mailman/listinfo/users

---

Kamailio (OpenSER) - Users mailing list Users@lists.kamailio.org http://lists.kamailio.org/cgi-bin/mailman/listinfo/users http://lists.openser-project.org/cgi-bin/mailman/listinfo/users

Well, I just passed a similar doubt...

Let see if I can help and shine some light... ;)

DIALPLAN module: good for RURI manipulations, but not for routing decisions; LCR module: good for RURI manipulations and routing decisions, but no granularity control (applies to whole system); CarrierRoute module: good for RURI manipulations and routing decisions, applicable to lower granularity (user, domain, system).

So, if I'm not wrong in my assuptions, I have to second Iñaki's question: What is a "dialplan" for You?

Edson.

Iñaki Baz Castillo escreveu:

2009/5/25 Bruce Ferrell bferrell@baywinds.org:

...

I've spent many hours looking over the module docs and examples.

is there a way to do dialplans from a database?

What is a "dialplan" for you?

Juha Heinanen escreveu:

Edson - Lists writes:

...

LCR module: good for RURI manipulations and routing decisions, but no granularity control (applies to whole system);

there is from regex that may help to improve granularity.

perhaps it would be possible to add a lcr_id to lcr table and thus get multiple independent routing rule sets.

-- juha

You are right, Juha, I forgot to consider the regex feature, sorry...

But with Your proposed change (lcr-id), what about functionality overlap with CarrierRoute (or vice-versa)? They already have, but LCR is much simpler and more 'direct' for a single domain/'routing policy' installation...

Edson.