Reducing time taken to make outbound call on POTS line

<< < (2/2)

Mango:
"None" means no delay, "assume connected" is a short (don't know how short) delay.  So the user will hear ringing sooner (depending on how soon the POTS provider sends it) with "none".

For the record, (((200+200)*11)+1000) milliseconds is 5.4 seconds.  (((75+50)*11)+1000) milliseconds is 2.375 seconds, or less than half.

ProfTech:
Mango is absolutely correct. I didn't read the post close enough and didn't notice that you were reducing the dtmf times. I never tried reducing them to anything less than the defaults since I was having trouble making outdialing working reliably. I was instead going the other way which only made the pause before ringing was heard worse. However, it wasn't until I changed the DialDelay setting to 1000 that my original issue was fixed. At that point I put the dtmf time settings back to the defaults and the pause before I hear ringback is not noticeable. The "assume connected" setting does cause a sort of weird behavior when you dial a busy number on the POTS line, however. The Obi generates a short 1 to 2 second burst of Ringback then you hear the busy signal. Since one hardly ever gets a busy signal any more my wife hasn't even noticed. Point I was making is the dial plan is probably the culprit in unmesh case. It definitely can cause a very noticeable delay and might be fixed by tweaking the dial plan to remove any xx.

Navigation

[0] Message Index

[*] Previous page