answerdelay

Description:   Used to delay when the Tenor signals to the call origination that the call was answered. On Loop Start signaled lines without the Reverse Battery feature enabled, there is no signaling sent back from the network to indicate that a call has been answered. Yes, the user will hear ringing, etc., but from a telecommunications point of view, the Tenor does not know when the call is connected (or if it is connected for that matter). This is true of any equipment configured for loop-start. The typical procedure is that when the call is originated to the network, the origination device assumes that the call has connected after a pre-determined time period has passed after the last digit has been sent to the network. This time period is very short, somewhere around 500ms (.5 seconds) and could cause incorrect billing. You can adjust this timer to your needs. For the purposes of this section, the prompt will be shown as config pstntg 1# or config pbxtg 1#.   

Cmd Type:   command.   

Prompt Level:   config pstntg 1# and config pbxtg 1#   

Syntax:   answerdelay or answ {sec}   

Arguments:   sec   The time, in seconds, to delay signaling the call has been answered. Valid values are between 0 and 360 seconds.   

Default:   0   

Availability:   Only if cassignaling is set to Loop Start (1) or Loop Start Reverse Battery (5), or Loop Start Forward Disconnect (6). All Tenor releases. The setting increment was changed from milliseconds to seconds during Software Release P4-2-14.   

Guidelines:   If required, start with 1 second and go from there. There is no standard time delay to use. The upper limit is 360 seconds.   

Examples:   

config pstntg 1# answerdelay 45

Sets the answer delay to 45 seconds for the first PSTN Trunk Group.   

Related Cmds:   ccsorcas, casorient, cassignaling, dialdelay, supervision