Outbound Call Route Switzerland

Started by Napfgeist, August 28, 2015, 09:27:48 AM

Previous topic - Next topic

Napfgeist

Hello

I have an OBI 100 in use here in Switzerland, without Google Voice, since its not supported in Europe.

I am using the OBI 100 with two providers:

- SP2: Cheap outbound calls
- SP1: Inbound calls

I have set the SP2 as primary line and all calls are routed without any problems to local fixline and mobile numbers.

The phone port settings are default except the primary line as SP2.

Now I would like to set up the right outbound call route for local calls to shared cost, free, shared and business, emergency numbers over SP1.


117 – Police
118 – Fire brigade
144 – Ambulance
145 – Poisoning/intoxication emergency
112 – Police

800 - Free phone
840 - Value added services
842 - Value added services
844 - Value added services
848 - Value added services
900 - Premium rate services
901 - Premium rate services

The number length are max. 9 and min. 9 digits.

Do I have to change OutboundCallRoute settings only?
I tried to add there {08xx:sp1},{09xx:sp1}, but it didnt worked.

Thank you for your help.

Regards,
Pius


OBI100
Outbound: Jumblo
Inbound: NetVoip

azrobert

Try this: {(0[89]xx.|112|117|118|144|145):sp1},

You made 2 mistakes with {08xx:sp1},
You must enclose the 08xx with parentheses to make it a DigitMap
Without the parentheses it becomes a literal and you are comparing for alpha xx
With parentheses you are comparing for 08 followed by 2 digits
xx. will compare for 1 or more digits

drgeoff

If the 08 and 09 numbers are 9 digits long, why not replace the 'xx.' with 'xxxxxxx' ?

Napfgeist

Quote from: azrobert on August 28, 2015, 10:18:25 AM

Try this: {(0[89]xx.|112|117|118|144|145):sp1},


Hi, thank you for the quick reply and help.
That is working perfectly!

Rgrds,
Pius
OBI100
Outbound: Jumblo
Inbound: NetVoip

Napfgeist

Hi there

I am using the OBi100 now without any problems in Switzerland.
The only issue is the dialing speed.

According to the admin manual, there is a way to change the digit map timer.

QuoteChange Inter-digit Long Timer Dynamically After Partial Match
The OBi starts off with the inter-digit long timer set to the configured DigitMapLongTimer value when processing a new digit sequence by a digit map. You may change the long timer as some patterns are partially matched by embedding the syntax {L=<time>} within a rule in the digit map, where <time> is the desired number of seconds for the long timer. For example:

(011 853 xxxx xxxx{L=5}x. |xx.)

Here the long timer is shortened to 5s after the user has entered 011 853 + 8 digits. Hence the OBi will declare that a complete number is collected in 5s when no more digits are received. Without the {L=5} syntax the user will have to wait for 10s (by default) for the same to happen.

Note: This feature is not available on the OBi100/OBi110.

However this feature seems to be not available on my OBi100.
Is there any hint or tip to speep up the dialing?

Thank you.



OBI100
Outbound: Jumblo
Inbound: NetVoip

ianobi

The Obi1xx series have a short inter-digit Timer fixed at 2 seconds and a long inter-digit timer fixed at 10 seconds. if your a digit map rule provides an exact match to the digits dialled, then the whole number will either be processed instantly or the short inter-digit timer will be used, depending on other rules in your digit map.

If the match is not exact, typically if using "xx." type rules, then the long inter-digit timer will be used to wait and see if any more digits are likely to be dialled.

Either inter-digit timer can be changed for any particular rule by using the "S" function, like so:
( ... |1408xx.S3| ... )
Any number starting with 1408 followed by any number of digits will be processed after a wait of 3 seconds.

Napfgeist

Thank you for your quick reply and explanantion.

I will add:

{(0[89]xx.S3|112|117|118|144|145):sp1},

Hope that will reduce the wait from 10 to 3 sec.
Thank you.


OBI100
Outbound: Jumblo
Inbound: NetVoip