cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
720
Views
2
Helpful
5
Replies

Replaced new Touch T10 with the new one and its not pairing with sx80

jawadaq
Level 1
Level 1

We replaced an old touch10 with new touch 10 and its not showing in control hub and also not going to Welcome page i suspect the issue is in software version and sx80 is running RoomOS 9.15.18.5 and the touch 10 is running RoomOS 10.8.3.1 .Please guide if it is compatibility issue or i am doing something wrong . We connected directly also to the codec but its not pairing . When we plung in the old one it takes it instantly .

sx80 versionsx80 versionIMG_3267.jpegTouch t10 versionTouch t10 version

1 Accepted Solution

Jonathan Schulenberg
Hall of Fame
Hall of Fame

The Cisco Room Navigator does not support the older SX/MX generation codecs. The data sheet clearly states which models are supported. The SX80 needs a Touch 10 panel.

View solution in original post

5 Replies 5

Jonathan Schulenberg
Hall of Fame
Hall of Fame

The Cisco Room Navigator does not support the older SX/MX generation codecs. The data sheet clearly states which models are supported. The SX80 needs a Touch 10 panel.

PJMack
Level 7
Level 7

FYI the new one is a Navigator, not a Touch 10. Not being picky - it's quite different even though it's serving the same purpose in this use case. That said - I do believe the SX running 9.x code vs the 10.x on the Navigator is likely the issue. Try putting the nav on your network and pair it via IP - see if that gives you any different results. If it triggers a SW change you might then be able to go back to the direct connection you have now. 

Hi 
Yes already did that both are on the VLAN and network. Also, we connected the Navigator to 2 port of the codec and via poe still nothing .  can you please say the usual process of pairing a new device with sx80 I must be making a mistake over there somewhere . i have already unpaired the old T10 .

I don't think your navigator is fully on your network - the picture you're showing shows an IP address starting with 169, which means it's not getting a valid IP address. Check your cables - you might be getting POE but missing one of the ethernet pins, which would explain why it's getting power but not an IP address. 

169. is the internal address which codec gives to its connected deices .