Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Error 98

Status
Not open for further replies.

TIgerV

Instructor
Mar 19, 2006
176
US
I am still in Urinary Olympics with my Nortel guys on this one. "It's YOUR switch, no it's YOUR switch!"

My Hipath 4000 v6 is behind a Nortel CS1000M, connected with a PRI using 4ESS.

Calls from the Avaya to the Hipath work fine.

Calls from the Hipath to the Avaya are disconnected with:
"Cause No. 98: message not compatible with call state or message type non-existent or not implemented. This cause indicates that the equipment sending this cause has received a message such that the procedures do not indicate that this is a permissible message to receive while in the call state, or a STATUS message was received indicating an incompatible call state. "

I can dial out trunks on the Avaya, just not local to it.

Any idea, either from the Avaya or the Hipath End, what we can do?

TIger
 
Can I tell the Hipath to IGNORE the status?

TIger
 
Can the Nortel do 5ESS? I have good luck with that in my general world.... I know the 4000 can.
 
If I have to change protocols, I'd rather use QSIG. But I don't really want to blow out all the routes in both switches and start over.

TIger
 
If I have to change protocols, I'd rather use QSIG. But I don't really want to blow out all the routes in both switches and start over.

TIger
 
I wouldn't delete a whole bunch of stuff without hearing from someone else first. I wasn't aware a protocol change would require you to delete everything and recreate it - I have done them before on other stuff just by changing the first trunk on the span, or the D-channel, I forget which one was first. In my experience the switch will then give you an error message telling you if you change one trunk you have to change them all, and then proceed to change them all, and *poof* you're done....

Maybe it's different on the 4000. All I have changed on there so far was the communication protocol on the Cornet span.

 
Per my Unify service tech, changing protocol requires deleting and rebuilding routing. If this isn't true, I would love to know.

I know for a fact that on the Nortel you have to delete all the routes that go with it.

TIger
 
I'm not 100% sure, which is why I suggested having someone else chime in on it first. I know I have done it on Cornet spans before. I don't even know if changing the protocol will fix the problem - I just figured if it was a quick and easy thing to do that it was worth a shot, but not if you have to through all that!!
 
You can change the protocol on TDCSU by CHA-TDCSU:pROTVAR=?
then reload the circuit
Because you are using 4ESS you might also have to change the number of channels.
Before you change any protocol try changing the SEGMENT=8
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top