On Fri, 17 Apr 2009 13:26:45 +0100, Theo Markettos wrote:
> Chris <g7b8c4-> wrote:
>> It's for a Linksys PAP2 device with sipgate
>>
>> (*xx|<:0044121>[2-8]xxxxxxS0|<0:0044>[12]xxxxxxxxxS0|<0:0044>[58]
00xxxx.|<0845:0044845>xxxxxx.|<0870:0044870>xxxxxx .|<07:00447>xxxxxxxxxS0|
999S0
>> |1xx.|09!|00!)
>
> Looks OK to me.
>
>> <07:00447>xxxxxxxxxS0
>>
>> same for mobile numbers
>
> That'll catch 070 Personal Numbers as well (can be almost Premium Rate).
>
> You don't do anything about 03....
>
> What about 0844/0871, or 05... (I thinking of 056... numbers in
> particular)?
For 0844 could, should you wish, lump it with 0845:- <084:004484>[45]xx.
In the above plan I don't see the point of putting in lots of 'x' and
then ending with a dot. The same would be achieved with a lesser number.
If it is known that a particular number type has a specific number of
digits then represent those digits with the correct number of 'x' but
don't add a dot to the end! I also think that the inclusion of S0 at the
end, in most cases, makes no difference. You are best to include the
correct number of 'x' and then it is known, implicitly, when the number
being dialled is complete.
>
> What happens if a number doesn't match the pattern? You don't have a
> fallback route. (Or is there a default in the PAP2?)
>
> Theo
I guess, if you wanted a default you would simply include xx. as the last
pattern in the dial plan. That is always assuming that previous patterns
are followed first. I think this is the case but I've not checked it as I
usually have each 'field' unique. Personally I prefer not to have a
default. I don't want to allow numbers to be dialled where I haven't
decided on the LCR. If the number is foreign to the dial plan then,
simply, I prefer that it doesn't get routed.
|