BCM50 3.0 H323 networked calls all going to Prime Set? 2

[Deweyhumbolt]

I have set this up multiple times in the past with earlier versions of BCM50 1.0 and 2.0. All the route and destination digits appear to be correct. The offices were just pre-pended with a lead digit. For instance, all the receptionist CAP M7324s are 2221, 3221, 4221, and 5221. You can see all the calls leave and then arrive with BCM Monitor.

I've built the Target Lines w Private Recvd., assigned them with Ring Only (2 appearances)and they always default to the Prime Set or ring fast busy.

Should I be using SIP, and if so, what are the important settings?

"Adversity is Opportunity

 

[Deweyhumbolt]

Big Clue: Take everything I said above as true. I can build a Public Recvd. on the same Target Line and have it ring to Vmail, but Private Recvd. goes to GD.

I'm guessing it has somethin' to do with CDP or UDP? It has to be a Private Network issue, right?

Thanks for any insight!

"Adversity is Opportunity

 

[gberger]

Do you have MCDN license in?

 

[Deweyhumbolt]

Negative.

Won't the calls go through without an MCDN license. I thought it just added CLID like Business Name and DN name.

I'm in real trouble if I NEED an MCDN license! Can I avoid it by using SIP?

Thanks for any help.

"Adversity is Opportunity

 

[tech1979]

did you remove the primeset dn from the IP trunks?

 

[oldestgeek]

Are you stripping the pre-pended digit in the destination code setup? Also. try making the prime set for the target line the set where you actually want it to ring. You're right you don't have to have MCDN but without it I believe you'll need to set the route up as public and use the public rcvd no.

 

[gberger]

MCDN use the Private received number field.Do like oldestgeek mentionned and populate the Public field instead.

 

[Deweyhumbolt]

1. Removing Prime Set gets fast busy.

2. No need to strip, Dest. Digit in routing 22,32,42, and 52. Private Dns 4-digits.

3. Tried using Public Recvd. in place of Private Recvd. along with changing to Public Unknown.

BIG Question? Is it normal under Resources/Telephony Resources/IP Trunks for it to display N/A under "Bus" and under "State"!

I just need a way to dial to the remote offices off the PSTN and on network. I'd even settle for an AA answering remotely with them entering the 4 digits again. I can only make remote test calls via AA with the Vmail transferring across the network. Even with setting up Enable Network Transfers, building Remote Access Packages, applying to PRI/VoIP lines cannot guarantee it's the same if I were onsite. No IP telephone keycodes.

Stars for oldestgeek and gberger for at least hinting there is a way around an MCDN keycode.



"Adversity is Opportunity

 

[tech1979]

Just to repeat and to get more info, the problem you are having is when calling from any site to another, all calls are going to "the prime set." In saying "the prime set" do you mean the reception extensions you mentioned above?

You had also mentioned "they always default to primeset or ring fast busy".... Is this random on the same extension or different extensions?

Regarding... "Is it normal under Resources/Telephony Resources/IP Trunks for it to display N/A under "Bus" and under "State"!....Yes it is, that being said, what do you have set for your remote gateways (aka routing tables) under that heading, Resources/Telephony Resources/IP trunks.

 

[oldestgeek]

Bus should show N/A but on all mine state is enabled.
Check this:
BlocA - service type set to public since you don't have MCDN.
Are the actual VoIP lines or the target lines ringing on the prime set? change the first display on the set to line so you can be sure. If it is the target line matching the digits you dialed going to the prime, that indicates you're sending and receiving digits as programmed and that they match the public rcvd number on the target line. After that, its justa line assignment issue. Try assigning to a different set. Try having AA answer the target line. Let us know how you're doing with it.

As for SIP, besides the routing table, the only one I don't leave at default is the SIP domain name. Dosen't matter what it is, it just has to match on all end points. I also set the codec to C.729 to reduce bandwidth usage. Good luck.

 

[gberger]

What do you see on both ends in CDR and Bcm Monitor?
That's usually how i get around that issue.

 

[Deweyhumbolt]

Part off the issue was testing from a sight that had the Default Gateway incorrect. It finally works, and here is what I found out. To avoid MCDN keycode, you need to leave at Private Network, None on MCDN protocol, Target Lines must be Private, you need a Prime Set on VoIP lines. You need to build the Recvd. Digits under Public Recvd., and if you expect the call to end up in a mailbox you need your Target Line as Express Messaging Line.

Yes gberger, BCM Monitor is your best friend in troubleshooting these issues.

I was able to use the Vmail's AA to make my numerous test calls, mind you that adding Remote Packages, Allow Redirect, and giving the Vmail access to all Line Pools was required.


"Adversity is Opportunity