Inbound call delay

[MaximusBrian]

Hey guys,

I am a bit stumped on this one.

setup: IPO R11 w/ VMPRO
issue: when call comes in, it takes 8-10 seconds for the AA to answer. I was looking around for settings that may control that but didnt see anything.

test:

setup: IPO R9.1 w/ VMPRO (test machine)
notes: when you dial a DDI from an external source, AA picks up immediately.

I was looking to compare settings under the "System -> telephony" and "Line" but not seeing anything that's glaring out.

 

[snowman50]

Watch SSA and see what happens when call comes in during this 8-10 seconds.
See if AA is answering first and if the voice ports are active during call

What call?? Is not answered

You say the DDI answers AA immediately

Is this the same module you are using for the call that’s takes 8-10 seconds

Could be your incoming number is not routed correctly.

Do you hear the greeting you have set up
Is it following the prompts you have assigned

Is it using a timeout when not answered.

You really need to explain better how your call is routed and what actually happens when it is answered.

Have you tested your module using a short code internally.

Screen shot of module would be nice
Screen shot of how line is routed would be nice.

 

[MaximusBrian]

point taken, let me clarify better. please let me know if there is more clarification needed.

System 1:
setup: IPO R11 w/ VMPRO
issue: when call comes in, it takes 8-10 seconds for the AA to answer. I was looking around for settings that may control that but didnt see anything.

from an external source (ex cell phone) you dial the main number you experience a 8-10 delay til the AA kicks in, same as if you dial a user's DDI, there is the 8-10 delay prior to the desk phone to ring.

the ICR's go where they need to go. main number goes to VM:AA (AA is the name of the module in VMPro). the ICR for the DDI goes to the user EXTN.

the outbound took a bit longer but i lowered the dial delay back to the default 4.

everything works as expected other than the delay to get to the AA or user's DDI.

System 2:
test:
setup: IPO R9.1 w/ VMPRO (test machine)
notes: when you dial a DDI from an external source, AA picks up immediately.

on system 2, you dial a DDI, it hits the AA within a sec or 2 from an external source.



I can log in tonight to get screenshots, not an issue.

 

[RocketJTech]

What types of trunks are we talking about at the receiving end? A POTS line usually does not actually ring on the IPO until the CID is received, between the first and second rings. Somebody correct me if I'm mistaken, but I don't think SIP or PRI require this delay to pass CID. Just a thought.

Please remember... If it's not the way that YOU would do it, that does not necessarily mean it's wrong. EVERYONE knows SOMETHING that you do not.

 

[snowman50]

Actually I should have asked …..are these analogue lines.

If so then the system is waiting for caller ID info which it’s not getting
If there is no caller ID presented change line setting in the drop down menu under each line.

I know you said DDI but if these are American lines then I am not sure on there set up.


Use SSA to watch the call coming in to see what happens

 

[snowman50]

got in before me

 

[MaximusBrian]

hey guys, these are SIP trunks (American) terminating to the IPO.

i had fun with POTS lines years ago lol.

under the "Line" category -> SIP Line 17 -> ??

snowman50 - which specific line setting? SIP URI?

 

[MaximusBrian]

wanted to update this thread to close it.

after tracing the calls coming in to the trunk, turns out the provider didnt remove the old ip from the previous ISP. instead they added it to the end.

once we got that figured out, they removed it and it immediately fixed the issue and the IPO is working as expected without delay.