Lag time in incoming calls

[etolentino]

when i call the land line plugged in the fxo port, it takes 2 rings before it gets forwarded to the extension. this is set in the fxo settings to enable FXO and it gets routed to extension 13, IP phone.


when i call the ITSP provided phone number it gets forwarded right away.


are there any settings to remedy this?

[etolentino]

found the answer on the other post.basically turning off the caller id in the hidden page.


/fxoconfig.cgi


sucks though. i am wondering if call forwarding on the fxo number to the VOIP number will pass over the caller id info so that we do not have to endure the lag on the fxo ring.

[hrant]

With ITSP provided number it works without lag because they dont use analogue FXO lines. Instead they are using E1/T1 trunks working with ISDN PRI where the caller ID information is being sent with the ISDN message which is not causing any delay.

[etolentino]

isn't there a way around it programatically? There is no delay if in the fxoconfig.cgi it is set to No caller id expected. Why not just pass the call through so that there is no lag time in the rings and when the caller id signal is sent between the first and second ring,have itdecoded by the quadro. Isn't thathow traditional caller id devices work for fxo lines?

[etolentino]

playing around it more seems like if i set it to fsk, the delay isalmost 1ring instead of 2 rings. ofcourse i take a chance if it is dtmf or others being sent. any one out there that is more familiar with the type of caller id commonly used.

[awhite]

As you mentioned, the caller id is typically sent between the 1st and 2nd ring cycle. To receive the caller id, the Quadro must wait before routing the call. There are also alot of feature that make use of the caller id, including Call Routing.