OBi110 Long delay to get dialtone on landline
RonR:
Quote from: FM9295 on February 03, 2012, 10:07:01 pm
Line Port:
(xxxxxxxS4|1xxxxxxxxxx|xx.)
2. We have 10 digit dialing so all numbers are 10 digit (plus 1 for LD)
There's the extra 10 second delay. The default DigitMaps in the OBi aren't usually optimal. Use this instead:
Physical Interfaces -> LINE Port -> DigitMap : ([2-9]11|[2-9]xxxxxxxxx|1xxxxxxxxxx)
FM9295:
Thanks! That's much better. I guess I should have called the thread "Long delay to get ringback" (rather than dialtone).
Stewart:
Quote from: FM9295 on February 03, 2012, 10:30:21 pm
That's much better ...
You can probably save another 2-3 seconds by setting (for the LINE port) DialDigitOnTime and DialDigitOffTime to 70. If that doesn't dial reliably, try 100. If still no luck, set them back to 200 (the default).
You could reduce call setup time further, by setting up speed dials for your often-called contacts.
If you need to make international calls on the landline, set the LINE port digit map to something like
([2-9]11|[2-9]xxxxxxxxx|1xxxxxxxxxx|011xxxx.)
lk96:
for whatever is worth, in addition to optimizing the digitmap (ie by adding a S0 term after
the matchin expressions), I did set the digiton/off times to shorter intervals.
My Dialdigitontime is set to 100ms and the Off timer is set to 50ms for couple months now.
These settings worked well for me and haven't introduced any side effects.
Keep in mind though that in my case, my line port on Obi is connected to a Vonage adaptor.
So for other adaptors or a real landline, you may have to eye on it until you verify
that everything is stable and working predictably.
L.
PS: if I recall correctly I had experimented with shorter values for the dialdigitontime and
that was working also ok. But I decided no to push my luck since the time savings
were very small.
FM9295:
This may be slightly "off-thread" but when I made the changes to the "digitmap" line, I did so via the web interface (ie, 192.168.x.x), then saved and rebooted. However, when I went back to the ObiTalk Web portal (via Expert setup), the change appeared not to have been saved. (I even logged out and back onto ObiTalk to see if that was the reason it hadn't noticed the changes sent to the device--that didn't do it either.)
Strangely enough, I did make changes to the "ontime" and "offtime" lines via ObiTalk and then saved them and they did show up when I went back into the web interface (192.168.x.x).
Is this some sort of bug between the web interface and the ObiTalk web portal?
Navigation
[0] Message Index
[#] Next page
[*] Previous page