[Frage] COMpact 5020 does not dial last digit via POTS

[Agile]

Hi Forum,
I cannot find the answer to this, probably some setting I overlooked, hope you can advice!
I have recently cancelled my analog line in exchange for CheapConnect VoIP. I'm using a Linksys PAP2 (a VoIP to analog unit) and this works as expected: dial in/out using a pots phone directly connected to the PAP2 analog connection.
However, if I connect the COMpact 5020 analog line to the PAP2, any outgoing call fails. Ingoing is ok.
By monitoring (listening) on the analog line, I noted that if I call a number via the 5020, the 5020 occupies the PAP2 line and start dialing the number. However, it does not dial the last digit, in fact it waits a bit and then dials the last one. Per consequence the call fails due to wait.
I checked and found that this 'wait' is also present using the old analog line, yet this line seems to accept the pause whereas the PAP2/CheapConnect combi does not. I'm clearly also looking in the PAP2 settings (…).
Questions:
- Why does the COMpact 5020 inserts a pause before dialing the last digit?
- Can the 5020 be set to not insert this pause?
Thanks!
SP: apologies for using English, please feel free to reply in German!

### Zusammenführung Doppelpost by stoney ###

Asking the question is partially solving it...
Here is some additional information after some trial & error.
I'm testing with a 10 digit number. Mentioned 'wait' is around 2 seconds.
- if I add a "#" to the number to dial, the 5020 dials the complete sequence of 10 digits (no 'wait' is observed) except the # and the call is established
- if I add a "0" to the number to dial, the 5020 dials the sequence of first 10 digits, waits a bit followed by the 0 and the call is established
- if I activate the "Transmit #" feature in the 5020 "Advanced Settings (POTS)", this does not solve the problem
- If I change in the PAP2 the "Interdigit Long Timer" from the current 2 seconds to 3 seconds, the 5020 obviously still dials out with the delay, but the call is established after a 3 second wait flowing the 10th digit.

So, I have a workaround, but would like to understand why the 5020 waits a bit before sending the last digit and how to overcome this.

 

[Agile]

Think I understand the issue better, so summarizing here to add bit of value to this post.
POTS-to-VoIP interfaces typically use a certain wait time to determine if the user has entered the complete number before sending the number of to the SIP server.
COMpact 5020: setting:"Waiting time after the last dialed digit (3-30 seconds)". The 5020 implements this wait before sending out the last digit. Reading the helpfiles, I understand this is by design.
PAP2 POTS-to-VoIP box: this unit has a setting called "Interdigit-long-timer" which determines how long the PAP2 waits to check if the user enters additional digits. When the wait time is expired, the PAP2 sends whatever it has received so far to the SIP server.
The problem I experienced was caused by the fact that the PAP2 wait time was shorter than the 5020 wait time, resulting in the PAP2 sending out an incomplete number and hence a failing call.
To overcome I figure these workarounds could help:
- Ensure the wait time in the 5020 is set to minimum (3 seconds) and that the PAP2 wait time is longer (I have them both at 3 which seems to work) Setting up the call will take bit more time now.
- add a # at the end of the dialed number to signal 'end of dialing'. In that case there is no wait in the 5020.
- use the 5020 internal VoIP interface instead of an external box.