Ramjet

1st, forget all you know about X11 and CDP, NARS, BARS, and the like. Next, go in there and tell them that if you want me to do this, send my a-- to school. Seriously, I haven't had the chance to do it, and I have several BCM's under my belt. But if they came at me with this like they did you I sure would ask for the course for it. It always seems so much easier after you've seen someone else do it.

__________________
Two snips, a snort, a turn, a fly, and a grunt, and it was so simple, like the jitterbug, it plum evaded me!

Meridianman69

I agree, the PM's here are less than adequate and that is a gross understatement. There will be no schooling offered as I am a sub. I guess I will need to fly by the seat of my pants yet again on this one. lol

Crowtalks

It's not like NARS in X11.

Are you going to be using VoIP trunking?

CDP between BCMs is a fairly straightforward process.

Are you BCMs in a campus environment or separated?

Do the Published IPs on the BCMs have public IPs?

Crowtalks

Did you figure out the steps to set up your private network using CDP?

Meridianman69

I believe they are on their private network, what would I need to look at to make this work from a network and a BCM config standpoint? Thanks!

Meridianman69

still working on it...do you have any input? Much appreciated!

Crowtalks

I have set up several CDP networks between BCMs and also BCMs-to-MICS via gateways.

In each instance, our network/sales engineer had the system setup preconfigured with public IPs and I configured the firewalls on each router for security.

With the number of systems to network, I would suggest MCDN/Q Sig keycodes for an efficient call flow for your intersystem transfers, etc.

I would also suggest five digit DNs with two digit destination digits at your gateway programming step.

CDP, as you know, takes the first digit(s) of the remote DN as the destination code for your VoIP Trunking and requires that each system DN range be unique from the other systems on the network.

Even though SIP is newer and more scalable, I have always used H.323 as the routing protocol because of it's simplicity for this situation.

In each systems Private network menu, your network ID is what the remote systems look for to identify it on the network, these digits must match what is setup as destination digits on the remote system. The network type should be CSE. There is no location code, that is only used for UDP.

You need to build destination codes for each remote site (example 22A, 23A, 24A, etc)and those destination codes pointing to either route O or BlocA, depending on your system. Your VoIP trunks need to be assigned to this route.

Crowtalks

Also, regardless whether the systems have private IPs or public IPs, they are going to have to be able to ping each other before they can communicate.

Once your network guys get that solved, then the rest is fairly easy.

Meridianman69

Thanks Crow, much appreciated! I may be reaching out to you again...