Fletch

Slag-

I tried to do my first 'out of the box' and did not get very far at all. Now I am not the best in the world (maybe 2nd best ) but I can usually get stuff running from the documentation.

This is just not going to happen on the NRS. You need to see one configured, and get help on the first. The second one I did on my own, and had to do some troubleshooting, but got it running. Number 3 went in like a charm. I had learned my lessons at the school of hard knocks, and understood the theory behind SIP and the function of the NRS.

Get some help on this. Like NARS/BARS, a poor design from the beginning will haunt you forever.

Global Knowledge 0784C is a good one for remote sites and trunking via the NRS and will offer a lot of insight. 5 Days, and $2495. Personally, I think it's a bargain for what you walk away with.

__________________
Fletch

For more on Nortel E911 Solutions on the web:
http://nortel.com/e911

Don't forget to register for the FREE E911 Webinar on Oct. 30th!
http://thevoicereport.com/E911

M1tech

Don't get held up on SIP on the NRS to only indicate connectivity to an MCS.

The war of the H.323 and SIP is been fought out in the IETF and other communities. Right now SIP is winning and H.323 will eventually will phase itself out.

You will notice on your keycode sheet 2 types of ports H.323 Access Ports and SIP Access Ports. These are the same as the old Virtual Trunks.

CallPilot on the MCS was pulled last release and I don't think they brought support back for it as of yet (i.e. CP Support on a standalone MCS).

CallPilot in a future release is supposed to move the Channels to IP to get around the trans-coding issues which happen today. This is where you will see SIP and CallPilot come together.

You could on a greenfield installation set up two sites with SIP Access Ports instead of H323 access ports. The Gatekeeper becomes a Redirect/Registrar server, set up is different but at the end of the day you are acomplishing the same thing as you did with H323.

Remember that SIP and H323 are means of setting up and tearing down calls. The transport is still IP.

slagburn

Man that's a real kick in the balls, if you couldn't do it then I'm SCRWED.

Thanks. The only part I'm not super clear on just is the interaction of the various domain levels. I'm not sure what goes where in terms of the Service domain, LO and L1 etc domains and what comes out of that setup.

Thanks

Fletch

Thats a tough one to explain via text......

I could draw it out for you on paper though. Here goes:

Service Level Domain is YOURCOMPANY.COM

L1 Domain is a text identifier for your UDP site
L0 Domain is a text identifier for your CDP site

So in my lab I have:

Service Level Domain: NortelLab.com
L1 Domain: njparsippany_UDP801
L0 Domain: FletchLab_CDP801

L1 Domain: njparsippany_UDP802
L0 Domain: FletchLab_CDP802

My CS1000M and CS1000S sit in
FletchLab_CDP1 under njparsippany_UDP801

My BCM400 sits in
FletchLab_CDP2 under njparsippany_UDP802

The CS1000's can CDP and UDP call each other and UDP call the BCM400

__________________
Fletch

For more on Nortel E911 Solutions on the web:
http://nortel.com/e911

Don't forget to register for the FREE E911 Webinar on Oct. 30th!
http://thevoicereport.com/E911

slagburn

Thanks for the help y'all.

Hopefully I'll be able to work with the 5100 installer / comissioner to get something working.

Maybe it's just me but there doesn't seem to be a lot of love for CS1000 integrations from that group, I might as well be trying to integrate a CrISCO built 3 phase lightbulb into a 5100 with the way they act at the management / engineering levels.

slagburn

Well they're talking... calls from the public hit a MG3200 then the 5100 and if no answer they foward to the CS1000 Call Pilot... the problem is that when they get to the CS1000 they don't look like redirected calls so the DN doesn't get sent to Call Pilot and the default greeting picks up instead of the mail box.

SIPTrace shows that everything seems to be there, I can see the calling number and the dialed number along with the Call Pilot number however when I turn on the DCH monitor (mon 2) for the virtual d-channel I only see the calling number (public number) and the Call Pilot number no redirect number (dialed number) that I'm used to seeing on a FNA from a regular switch.

The problem is that I'm not exactly sure where to start with this one but I'm sure that it's pretty simple.

Another issue I'm having is with the DTMF tones doubling up on calls from the public net, I think it has something to do with the MG3200 sending SIP Notify messages at each push of a keypad button along with Call Pilot picking up the DTMF tones from the audio stream... I played with the DTMF settings in the MGWC and SigServer but with no luck.

The good news is that on Monday I'll have support from both our vendor and Nortel who say that this config is really simple.

slagburn

Well this has been in a working well for a couple of weeks now.

The problem with the calls not redirecting properly and the double singalling to Call Pilot was in the DTMF transport settings of the MG3200. (I don't remember off hand what we changed it from - to)

As was stated by Fletch - I had to get a few hours of walk through with someone who has done this a few times before, the most difficult part of the process to understand was the SIP URI mapping in the 5100 and CS1000, once I understood and saw it setup everything sort of fell into place.

Another snag I ran into was that the system was not properly speced for the job... it was ordered as an Enhanced Buisness (I think that's what it was... don't have the paperwork here) and needed to be Advanced Networking - the biggest differences between the two for me were the inclusion of the NMS and MWI feature packages which allow the CS1000 hosting the Call Pilot to provide Message Waiting indication to the MCS5100... I beat my head off the wall for a day trying to figure out why it didn't work even though I had everything setup correctly. Once we upgraded the CS1000 the MWI setup was straight forward.