Delay on outgoing call on a SIP trunk

[sunspark]

i have  two sip trunk (primary and secondary). when i shutdown the primary sip peer to test resilience, after dialing the number, it takes 40s before the mitel controller sends request (ringtone)

my Ars route list :
route 1 = primary Sip peer,
route 2 = secondary Sip peer

i'm not using "unknown" in the ars number of digits to follow.

Test 2:

even when i dial number + # hash key i'need to wait 40s


Test 3

without using Route list, i have no delay using secondary route


40s to determine that route 1 is out of service and therefore taking route 2 seems too long to me

any idea?

[lundah]

What do your packet traces tell you?

[sunspark]

i didnt trace yet

[NEPhoneGuy]

i didnt trace yet

Can't really do much without that. Are you using route lists? I'd assume that the MiVB is sending an invite to the first peer and timing out waiting for response before moving on to the next.

[sunspark]

i didnt trace yet

Can't really do much without that. Are you using route lists? I'd assume that the MiVB is sending an invite to the first peer and timing out waiting for response before moving on to the next.

Yes . but what should be checked in the pcap?

[NEPhoneGuy]

i didnt trace yet

Can't really do much without that. Are you using route lists? I'd assume that the MiVB is sending an invite to the first peer and timing out waiting for response before moving on to the next.

Yes . but what should be checked in the pcap?

Validate what is going on so you know what to look at...

Is the secondary peer slow to respond - tshoot that.
Is the primary peer invite timing out - tshoot that.
Is the system slow to invite - tshoot that.