BCM 400 call progress taking too long, ISP dropping call. Any timer settings to check?

[bwdavis]

Hi I've got 3 3.6 BCM's networked together and set up to us H.323 voip trunks. Sites A, B, and C. There is a PRI connected to site B. Site A and Site C non-local calls route over voip to site B to go out. This all works. The problem occurs when someone at site A or C forwards their set to a non-local number like their cell phone. Call rings into Site B PRI for the forwarded set at site C, site B BCM opens a VoIP trunk to site C, and finds the set is forwarded to a non local number, it sets up a VoIP trunk back to site B and as soon as site B sees that trunk, the call is disconnected by the ISP after what they say is the default maximum allowed setup time of 6 seconds with no call progress reported. They have increased the time to 15 seconds and it works now - however they cautioned me that we may have "other issues," for example other ISP's reporting that our calls are taking too long to set up. I'm wondering if there's any settings in the BCM that may impact this call progress reporting or call setup time.

Thanks in advance.

Bruce Davis

 

[curlycord]

How does the call get to site C?
Are they calling DID or using AA from site B to dial DN on site C?

Have you looked at Monitor on both sites at the same time and calculated the time from first hitting site B until that last digit is dialed for the cell phone?
And how long it takes to ring the cell phone from the last digit dialed too.




________________________________________
We take the time to try to answer your questions for free, please return the favor and take the time to answer back and include any resolution you found elsewhere, thanks.

=----(((((((((()----=

http://www.curlycord.com

Toronto Canada

http://www.telcopc.ca

 

[bwdavis]

Inbound call originates as a DID on a PRI into site B. B sends call to C over voip trunk, C sends it back to B over VOIP trunk because destination set C is set to Fwd All Calls to a number that routes it back over voip trunk to go out site B.

I monitored both sides and it doesn't seem to take more than a couple of seconds, but ISP says it is lack of call progress reporting to his core network is causing them to end the call with a normal disconnect which is what I see in the monitor.

The BCMs try three times to set up the call and then it fails.

ISP says his PRI never sees the outbound setup attempt from site B.

This core ISDN call setup time limit apparently starts when the last digit is dialed in the incoming call, and if there is no ring or answer or other feedback for 6 seconds, the call is deemed a failed call and disconnected. If call progress is received, the timer resets and you get another 6 seconds.

Thank you for your response.

Bruce Davis