SV8100 to SV9100 migration, IP Phones will not connect

[Daniel_RO]

Hey Guys and Gals,

Migrated an NEC SV8100 to an SV9100 CP20 two days ago, and have been trying to work with NEC Support in Australia about this, but figured someone else may have come across this issue.

Ever since Migration, none of the IP handsets that were connected to the 8100, are able to connect to the 9100. I can see the traffic coming into the phone system, but the system is responding sporadically with Destination Port Unreachable, Handsets are coming up with SIP Server not found but I can ping the CPU IP from the handset without fail.

We are on a VLANd environment, all the handsets are communicating across the same VLAN Tagged Switches back to the phone system. The local IT guy swears black and blue there is no rules in his equipment that is blocking the traffic from the system, and NEC support is taking forever to get back to me. So I turn to you obi wan kenobi, your my only hope.

I have tested another port for the handsets to communicate across in 10-46,
I rolled back to the 8100, and the handsets communicate no problem
I have tested with a brand new handset, programmed from scratch, and an existing handset, to no avail

I am at my wits end here, and losing what little hair I have left, and am on a timeline to get this resolved, as over half the system is IP. Any information or pointers anyone can give would be greatly appreciated.

 

[CoralTech]

Run a wireshark cap. Check the simple stuff. Go over all your subnets etc. Does your CPU have an IPLE? Does the IPLE have an IP address? Are you plugged into the IPLE? Is your IPLE card tagged for the correct VLAN? Are your phones tagged correctly? Are you certified? Is VOIP resources allocated for 5103? Was the 8100 in a VLAN environment before the upgrade?

 

[Daniel_RO]

Found my problem, and it wasnt anything to do with what I had programmed. Seems that someone in their infinite wisdom had changed 84-20 to use 5060 for third party sip over 5070, and changed the SIP settings to be 5090. After resolving this and changing the third party sip to use 5070 (as per defaults), all IP handsets returned.

 

[OzzieGeorge]

Daniel

Have you tried running the data conversion again to see if this was changed automatically (no need to upload it, just see if the database is wrong)? If it is, we need to flag this with TAC.

Nice find by the way.

 

[Daniel_RO]

I confirmed the programming in the 8100 database, so it did migrate correctly. I involved TAC before I posted here, but you know what they are like responding to queries =P.

TAC wasn't able to locate the issue, it was only through pure luck that I did. The customer IT fessed up to having changed the ports to register an Yealink Cordless IP Phone, cos they figured it was easier changing it in the system than in the phone itself ... which I don't understand.