CS1000E to Cisco, SIP (Have I mentioned I hate SIP trunks?)

[allenmac]

The problem most likely lies in the way both parties have implemented SIP, and how they treat and build the SIP messages, headers, and options.

 

[RyanEOD]

My D-Channel won't even sync. I have read white papers that say it is possible, and I even see some people have done it with like a 4.5 CS1000, so I think I am just missing something. Small I hope. . . .

 

[rain78]

I may be wrong but i dont think you can use regular Nortel SIP access ports to connect to a Cisco system. I am interested if this does work because I would like to implement also.

 

[biv343]

Do you show your signaling server registered to your NRS? You can define the Cisco as a static SIP endpoint in the NRS, then set the CS1K as dynamic. Once you get the sig server/NRS stuff up and running, the virtual d-channel should come up and then you'll be on your way.

 

[RyanEOD]

Biv, I have an entry in my NRS for the SS. I have the Asterisk and Cisco set as static SIP endpoints, and the SS as dynamic. The D-channel won't come up.

 

[biv343]

Check the hostnames in the node file and make sure it matches the endpoint name in the NRS, and that you've entered the TLAN IP of the sig server that has the NRS application. It sounds like you've almost got it all in place.

 

[RyanEOD]

Biv,

That might be what I am missing . . the hostnames in the node file? (In the words of Scooby Doo) RutRoh?

I looked in my Node ID: 1, and I don't see anything in there about hostnames?

Help?

 

[biv343]

Check the node config under SIP gateway. You'll see where you have to enter the hostname, primary proxy tlan address, etc. What release of software are you running? You may have some other stuff to enable to see those prompts. I seem to remember having to specify if the SS was going too run TPS only or TPS/H323/SIP in the original software load. Its been a while since I loaded a 4.5 or 5.X sig server though. I miss the simple days. If you're on 6.0 or higher you should be able to turn on the SIP GW portion in the node config fairly easily.

 

[RyanEOD]

Biv,

Ahh, ok, I am running 7.0. I already have the SIP GW enabled to run to my Asterisk, just trying to add a new Endpoint.

 

[biv343]

Are you building a different route/dch/trunks for the Cisco connection? You'll only have one virtual d-channel per node in the system. If you can call to the Asterisk system then you should be able to call the Cisco using the same route/trunks/d-channel. If you want/need to build a different route and different trunks for the Cisco you can do that, just reference the same virtual d-channel you're already using.

 

[RyanEOD]

Biv,

Ok, that is starting to make sense. So, do I need to just use the same route/trunk/D-Channel, and just route to the Cisco in NRS?

 

[biv343]

That should work or at least get you to the point where you can see calls hitting the dch and cisco side.

 

[bignose21]

If you already have a working SIP trunk I guess the Endpoint is registered with the NRS or SM you just put the traffic down that. You enter the Cisco in the NRS as a static endpoint and route the number range to it. For the inbound traffic you put the Node IP address of the switch in the Cisco.

I have switches using SIP to talk to other CS1k's and sevreal Cisco routers and just shot all traffic out on the one Route. The only issue we have ever come across is with call transfer in release 5.0 where we had to disable the SIP Options in the VXShell of the Sig Servers.