We have a BCM 3.7 with i2004 phones. It is networked using VoIP trunks to a CSE1000 that's connected to an opt. 81c. We are experiencing an intermittent problem connecting to cellphones from the BCM end. When the call fails I get "No User Response" in the display with error code 18. I did a network capture, and I can see where the BCM sends an "H.225. CS: releaseComplete" to the Gatekeeper. If you call the same number enough times you will eventually get through. Also, when the call fails to connect, we get a busy signal at the BCM end, and the cellphone gets a quick ring. I have used the BCM Monitor to look at the calls, but just can't seem to find the problem. The tech at the Opt. 81c is pointing the finger at the BCM, but I am not sure where to go from here. Any help will be greatly appreciated.
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 Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
BCM 3.7 VoIP Issue (Strange Problem)
- Thread starter NstarGuru
- Start date
Have you installed the FEPS 37.160.0.33 patch? Check this out - sounds like this might be what's happening....
BCM 3.7 FEPS v. 37.160.0.33 Patch
o Q01145202: One way voice path when call from IPT card on option 11C is transferred
back to another destination on the option 11C. This problem occurs when TAT is
disabled or simply does not work. The transferring operator on the BCM whether TDM
or IP phone must attempt to press transfer and then dial the digits for the destination on
the option 11C to transfer the call to. The operator on the BCM must press the hang up
very quickly after he/she dials the last digit in the transfer operation. This can cause a
one way voice path between the two participants on the option 11C. The transferred to
entity will no be able to hear the original caller on the option 11C who started the call to
the BCM. This problem affects feps 130,140 and 150. It was reproduced on a 3.6 system
with core 6.12.
o Q01211403: Calls to CS1K when h245 tunneling is enabled on both the CS1K and
BCM do not work and are dropped by the BCM. This problem will occur depending on
the CS1K's signalling, but it is a BCM problem.
o Q01212372: When connection to GK is lost but BCM does not realize it yet, and the
BCM makes an outgoing trunk call, it can cause FEPS to crash. Fixed by preventing a
dangling pointer access. Code fix.
BCM 3.7 FEPS v. 37.160.0.33 Patch
o Q01145202: One way voice path when call from IPT card on option 11C is transferred
back to another destination on the option 11C. This problem occurs when TAT is
disabled or simply does not work. The transferring operator on the BCM whether TDM
or IP phone must attempt to press transfer and then dial the digits for the destination on
the option 11C to transfer the call to. The operator on the BCM must press the hang up
very quickly after he/she dials the last digit in the transfer operation. This can cause a
one way voice path between the two participants on the option 11C. The transferred to
entity will no be able to hear the original caller on the option 11C who started the call to
the BCM. This problem affects feps 130,140 and 150. It was reproduced on a 3.6 system
with core 6.12.
o Q01211403: Calls to CS1K when h245 tunneling is enabled on both the CS1K and
BCM do not work and are dropped by the BCM. This problem will occur depending on
the CS1K's signalling, but it is a BCM problem.
o Q01212372: When connection to GK is lost but BCM does not realize it yet, and the
BCM makes an outgoing trunk call, it can cause FEPS to crash. Fixed by preventing a
dangling pointer access. Code fix.
- Thread starter
- #3
Biv343 Thanks for the quick response.
I have applied both the FEPS and the Core patch on the BCM. But still have the problem. Local and longdistance calls to non-cellphone numbers work fine. The problem only arises when calling cellphones. Some cellphone numbers have a higher failure rate than others, and I have witnessed failures on most carriers, (T-Mobil, Cingular, and Sprint). I forgot to mention that the BCM is a BCM 200.
I have applied both the FEPS and the Core patch on the BCM. But still have the problem. Local and longdistance calls to non-cellphone numbers work fine. The problem only arises when calling cellphones. Some cellphone numbers have a higher failure rate than others, and I have witnessed failures on most carriers, (T-Mobil, Cingular, and Sprint). I forgot to mention that the BCM is a BCM 200.
- Status
Similar threads
- Question