Dial Plan conflict?
 

Hi people,

I have the following dial plans:

1 _11 ${EXTEN} AstraTel [Edit] [Delete]
2 _613XXXXXXXX ${EXTEN} Freecall [Edit] [Delete]
3 _04XXXXXXXX ${EXTEN} PennyTel [Edit] [Delete]
4 _[45689]XXXXXXX 613${EXTEN} Freecall [Edit] [Delete]

Dialing 93213210 works
Dialing 61393213210 doesn't

Changing the priorities around does not affect it.
Removing line 4 makes dialing 61393213210 work.

Are there any conflicts in my dial plans?

BTW i have my home number registered on the ENUM e164.org but my home phone rang instead of my voip phone.

Have you confirmed that the number is found in the ENUM database?

http://www.sipbroker.com/sipbroker/action/enumLookup

Yes. Also works with Sipbroker *011

I just tried a number with 617 and it did not work either, it was working yesterday however.

Hi,

When the 4 entries are set-up does the "Test" functionality report the correct result?

BTW Conflicts are OK in VoXaLot as the entries are evaluated in priority order.

Nothing has changed in VoXaLot since the release of Web Call-back so I am unsure what has caused this change in behaviour.

Any more details you can provide would be help us look into it.

Yes, the "Test" function returned the correct results.

Ok. I have done further testing. Some numbers work dialing both ways and some don't. And some do sometimes and don't other times. Seems to me it is a provider related problem.

The reason I used the 61 prefix is because of the ENUM thing and it worked with Freecall.

Has anyone else tested the ENUM thing. I tried my home number and the times it got through it rang my PSTN number.

Ok cool.

At the moment ENUM lookups in VoXaLot are done on the dialled number and not the post modified one.

In other words ATM it will only work if you dial the full number including the country code. In the next release, there will be an option to instruct the system to perform the lookup before consulting the dial plan or after applying the dial plan.

Martin,

I can come up with a multitude of perfectly reasonable examples where ENUM lookups will fail regardless of whether they're performed before consulting the dial plan or after applying the dial plan. The flexibility and power of a Dial Plan to convert arbitrary input formats, coupled with the highly inconsistent output formats required by various providers, makes it virtually impossible for a simple before/after option to solve the ENUM lookup problem.

What I think is needed is the addition of a second replacement field in the Dial Plan. The existing replacement field doesn't change except for being called "Replacement to Provider". The added replacement field is called "Replacement to ENUM". It works exactly like the existing replacement field except its output is used for the ENUM lookup.

Doesn't this get rid of all restrictions and ambiguities and ensure that both the provider and ENUM get exactly what they expect regardless of the original dialed number?

Ron

Hi Ron,

It certainly does address the ambiguities. I guess to make it simple for the users we could make this field optional. If it is not filled out, then we will use the provider replacement field value.

We should probably also add default behaviour for the numbers that dont match a dial plan entry. This behaviour should probably be to perform an ENUM lookup on the dialled number. That way people are not "forced" to add an entry for numbers that they don't want to link to a provider.