DAHDI delays - inbound and outbound

tin

New Member
Joined
Sep 5, 2011
Messages
16
Reaction score
0
I've got a cheap PCIe 4 port dahdi compatible PSTN card, which is working fine, apart from a delay problem on FXO ports. It's connected to a Telstra line in Australia, if that helps/matters.

Inbound calls delay 2 rings (~6 seconds). I'm assuming this could be CID detection - there's no CID on our lines. But every effort I made to disable CID detection has failed to fix this. This could be because most info I found was so old it talked about zaptel not dahdi.

Outbound calls also get a ~2 second issue - silence for about 2 seconds, which cuts off part of remote announcements, allows roughly 2 rings remotely before we hear anything, etc. Probably not a big deal for most everyday use, but it's cutting off announcements when remote systems pick up and start IVRs, etc immediately.


For the inbound, on the Asterisk console I see:
-- Starting simple switch on 'DAHDI/1-1'
But then that's all until roughly 6 seconds later when it starts ringing the extensions.

Outbound is a similar deal. It says
-- Called DAHDI/1/67924890
and then waits for about 2 seconds before I see anything else (which is when I start hearing things on the phone). I can understand it needs to dial first, but that doesn't explain the silence well after it's finished dialling.


Any ideas? Even just the inbound delay being fixed would be a massive help.
 

Members online

No members online now.

Forum statistics

Threads
26,688
Messages
174,412
Members
20,259
Latest member
Fadeek86
Get 3CX - Absolutely Free!

Link up your team and customers Phone System Live Chat Video Conferencing

Hosted or Self-managed. Up to 10 users free forever. No credit card. Try risk free.

3CX
A 3CX Account with that email already exists. You will be redirected to the Customer Portal to sign in or reset your password if you've forgotten it.
Back
Top