Dialing prefix #0 for selecting 2nd PSTN line
RonR:
Quote from: obi-support2 on December 08, 2011, 09:46:07 am
Yes you can insert pauses...
.
.
.
Each comma inserts about 200 ms of pause. You can
add enough comma according to what you need.
It sure would be nice to have these kinds of things documented somewhere.
Quote from: obi-support2 on December 08, 2011, 09:46:07 am
Note: Since # and #0... are all legit digit patterns, with this you will experience 2s delay when trying to invoke
PSTN dial tone by dialing # (since OBi needs to make sure you don't mean #0...). You can consider using a different pattern to explicitly invoke PSTN dial tone, such as ##.
A possibly more elegant solution that doesn't interfere with dialing # to invoke a PSTN dialtone:
Physical Interfaces -> LINE Port -> DigitMap : (<+>04xxxxxxxx|...)
Physical Interfaces -> PHONE Port -> OutboundCall Route : ...,{(<#:>|<+:#0,,,,,>04xxxxxxxx|911):li},...
marcb:
Quote from: Stewart on December 07, 2011, 06:38:01 pm
If you take out the special config for #0, pressing # should cause the OBi to connect directly to the Line port and you'll hear dial tone from your AX-520. Then, dial #0, wait for new dial tone and dial the 04 number.
Thanks Stewart, but this is not really practical. I prefer using numbers stored in memory. Thanks anyway.
Quote from: obi-support2 on December 08, 2011, 09:46:07 am
marcb,
Yes you can insert pauses after #0.
Here is 1 way to do it, by
inserting a rule in the PHONE Port OutboundCallRoute, like this.
{(<#:>|<#004:#0,,,,,,,,04>xxxxxxxx|911):li}
Each comma inserts about 200 ms of pause. You can
add enough comma according to what you need.
----
Note: Do not insert the comma's in DigitMap; only in OutboundCallRoute.
Note: Since # and #0... are all legit digit patterns, with this you will experience 2s delay when trying to invoke
PSTN dial tone by dialing # (since OBi needs to make sure you don't mean #0...). You can consider using a different pattern to explicitly invoke PSTN dial tone, such as ##.
This gave no positive result. There was a problem with the Call route. Thanks anyway.
Quote from: RonR on December 08, 2011, 11:32:11 am
Quote from: obi-support2 on December 08, 2011, 09:46:07 am
Yes you can insert pauses...
.
.
.
Each comma inserts about 200 ms of pause. You can
add enough comma according to what you need.
It sure would be nice to have these kinds of things documented somewhere.
Quote from: obi-support2 on December 08, 2011, 09:46:07 am
Note: Since # and #0... are all legit digit patterns, with this you will experience 2s delay when trying to invoke
PSTN dial tone by dialing # (since OBi needs to make sure you don't mean #0...). You can consider using a different pattern to explicitly invoke PSTN dial tone, such as ##.
A possibly more elegant solution that doesn't interfere with dialing # to invoke a PSTN dialtone:
Physical Interfaces -> LINE Port -> DigitMap : (<+>04xxxxxxxx|...)
Physical Interfaces -> PHONE Port -> OutboundCall Route : ...,{(<#:>|<+:#0,,,,,>04xxxxxxxx|911):li},...
Dear RonR,
I implemented your proposal and it works just fine. Thanks again and sorry for replying so late, but I found no occasion to test it earlier.
A follow up question: how can I dial out via the second line using the Obitalk application for Iphone? I can dial 04xxxxxxxx numbers but line 1 is used instead of line 2.
Marcb
Marcb
RonR:
Quote from: marcb on December 18, 2011, 01:34:48 pm
A follow up question: how can I dial out via the second line using the Obitalk application for Iphone? I can dial 04xxxxxxxx numbers but line 1 is used instead of line 2.
marcb,
Call routing from OBiON Apps is handled by OBiTALK Service InboundCallRoute rules in the OBi. OutboundCallRoutes are not used. According to obi-support2, pauses (commas) can only be used in OutboundCalRoutes.
You might want to try an experiment to see if pauses (commas) are also valid in InboundCallRoute rules (I'd run the test here, but my LINE Port is incoming only). Temporarily set the following:
Voice Services -> OBiTALK Service -> InboundCallRoute : {>(<#0,,,,,>04xxxxxxxx):li}
Then dial an 04 number from your OBiON App and see if the pauses work and the call goes through properly. If it does, I'm pretty sure we can come up with a satisfactory solution.
If pauses are not allowed in an InoundCallRoute rule, then your only option is to place calls from your OBiON App using the OBi Auto Attendant. The Auto Attendant has its own DigitMap and OutboundCallRoute that can be modified similar to the PHONE Port to support the pauses.
marcb:
RonR,
Apparently pauses are allowed in the OBITALK Service InboundCallRoute because it works. After a few test calls I noticed that a new call was no longer initiated (nothing happens when choosing a contact's number), I guess this might be a problem with the OBiON App, since restarting the App solved that problem.
Ideally I would still have to add *31* in front of the 04 number and # at the end in order to mask the originating number, because I do not want people to call that number.
marcb
RonR:
Quote from: marcb on December 20, 2011, 12:53:32 pm
Apparently pauses are allowed in the OBITALK Service InboundCallRoute because it works. After a few test calls I noticed that a new call was no longer initiated (nothing happens when choosing a contact's number), I guess this might be a problem with the OBiON App, since restarting the App solved that problem.
That's what I suspected and hoped for, but obi-support2 made it sound like pauses would only be honored in the OutboundCallRoute. Give me a little time and I'll work up an OBiTALK InboundCallRoute that should solve your problem.
Quote from: marcb on December 20, 2011, 12:53:32 pm
Ideally I would still have to add *31* in front of the 04 number and # at the end in order to mask the originating number, because I do not want people to call that number.
I don't know what you're referring to here.
Navigation
[0] Message Index
[#] Next page
[*] Previous page