bcm 50 6.0 h.323 to 3.0

[Wallysworld]

Hi Guys;

I'm having an issue trying to connect 2 bcm 50's through VoIP trunks. Here's the particulars:
6.0 & 3.0
current patches
3 digit dn's (yes, I know 4 is better, couldn't change their mind)
h.323 using udp
3.0 CAN call 6.0 (any extension)

6.0 CANNOT call 3.0 (as soon as last digit of ext'n # is dialed, call goes to a fast busy)

2 odd things about this scenario both in the 6.0 bcm;
a) under the "ip trunks" tab, in "H323 trunking" after you create the destination digits and enter the i.p. address of the other bcm... your not able to edit it... it goes away. I can see it under the "General" tab but am unable to see it in "H323 trunking"

b) in my "Dialing Plan" tab under "Routing"; if I create a destination code (ie. 7) and "absorb all", I dial 7444 and the call goes to fast busy.
If I say "absorb 0" and dial 7444 the call rings on the 3.0 bcm at the control dn (221, zero out, whatever you want to call it).

Has anyone had any issues like this and suggestions for fixing it. Thanks, Wally

 

[telcodog]

Do you have MCDN licenses in both systems?

 

[norstarboy125]

Use the BCM monitor to see what your system is actually dialing. It is the best troubleshooting tool when trying to fix something like this.

Jeremy J. Carter
Charm City Communications

http://www.charmcitycommunications.com

Norstar. BCM. CS1000 Programmer

 

[Wallysworld]

No mcdn,
In Monitor the system shows that the set is grabbing a VoIP line and "active" until the last digit is dialed (which is when the fast busy begins) and then says "idle".

 

[bluemr2]

You need to downgrade your version of element manager to see the ip trunk routing. I had the same issue, and I downloaded the element manager off the 50 and it worked.

 

[Wallysworld]

Downgrade?
It wasn't working with 62.0.0 and I was told to "upgrade" to 62.0.3... however, that still doesn't work. Are you saying I should take it to an older version lower than 62. I've just recently patched the 3.0 so I'm not sure I have an older version available...

 

[bluemr2]

I downloaded the element manager that was on the system, and it worked.

 

[Crowtalks]

Are you using UDP because both systems share the same dialing plan? You wrote: if I create a destination code (ie. 7) and "absorb all" Absorb all absorbs all digit and sends none...absorb none, sends all digits so 7444 is probably arriving at the far end and the system is sending the unknown extension to the attendant. Have you tried absorb 1?



"If I had known it would turn out like this, I would have became a locksmith" Albert Einstein

NCSS NCTS NCTE CS1000E
Mitel 3300 4.2 basic & advanced, 5000 4.0, NuPoint I&M 4.2