Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

call forwarding problems

Status
Not open for further replies.

pbxNewb

MIS
Jan 9, 2008
179
US
For the past year since installation of our BCM50, we have had phantom forwarding issues. I've finally been able to narrow down what is happening, but don't know why or how to fix. We have a BCM-50 connected to our CS-1000 on our main campus via SIP trunks. on-net (we can call each other with 7 digit internal dialing, no 9 required) Calls can be made from the remote location (BCM50) to the CS1000. At night, they want to call forward their main line to one of our on-net numbers. The phone accepts the call forward request, but when the number is called from outside (off net) or inside (on net), the caller gets a short delay followed by a fast busy signal.

If I forward the calls out and back in again (9+ number) then external callers get routed correctly, but internal callers still get the fast busy. I don't know why this is happening, neither does my support vendor and they basically said live with it. Is this something that can be fixed? I saw something about enabling supervision on the phone/line, but couldn't find anything like that in the elements manager other than silent supervisor. Help, i'm pulling my hair out!

Looking at the BCM monitor I can see that the call comes in, then is dialed out but the outbound number does not have a 9 in front of it, and then I get the fast busy. This happens when the BCM is forwarded to an external number and I dial it from an on-net phone. If the BCM is forwarded on-net and I call it from an on-net phone, the monitor shows the incoming call, then the outgoing briefly (dialing correct on-net number) and then it drops and I get fast busy. What do you think? Let me know if you need any clarification, this is hard to accurately describe. Thanks!
 
This has nothing to do with supervision. Try setting the send name display to either on or off.
Also sould make sure it's up to date with latest patches.
 
It is up to date with patches, that was the first thing we tried. Where would I find this "send name display" option, I don't recall seeing that anywhere on the BCM-50. Let me know, thanks!
 
First off ... fire your support vendor. Just live with it??? They are obviously in over their head.

I am a bit confused with your description.
Who is forwarding? The BCM user?

There are two rules to externally forwarding a BCM set.
1) You must have redirect set to yes in capabilities
2) You must use destination codes and routing

Can you provide another explanation of what you want to do?



-SD-
 
I have redirect enabled, and have destination codes and routing setup correctly. Users dial 9 to grab an outside line, then dial their 7 or 10 digit number. The 9 is absorbed and the calls go out. This works fine for everyday calling, but the problem comes when they want to forward the calls at night. I'm thinking maybe the problem is on my 61c (which routes calls over a wireless link to the BCM50 via CDP/DSC). When calls come into the 61c (which has the main number they are using), it is routed out to the BCM, which then rings 4 phones based on the target line. When they in turn try to forward that call back to an on-net number (which would come back to the 61, and then out to an option 11).

The I2004 on the BCM accepts the forward and shows the lines on that set are forwarded. When outside callers call, they get a fast busy. If I forward the BCM calls outside via routing (dialing 9 and then the public number on the option 11), then inbound calls from the community forward correctly. On net callers to the number get a fast busy in this scenario though. Is there some setting that prohibits a call from coming out of the 61 and then back into it at the same time (I think this is called tromboning?? which I have enabled on the 61c). Hope this helps, thanks!
 
TAT or Trunk Anti Tromboning prevents calls from leaving on one trunk and returning on another through the same switch. (think of the U shape at the end of the slide on a Trombone)
This could be causing some issues.

Does the BCM50 have any telco trunks terminated, or do all inbound/outbound calls come through the 61?

Can you view the D channel messaging on the 61 during one of the failed calls?

-SD-
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top