Hello, I have a MX300 G2 with a touch 10. Currently if I have the Touch 10 plugged directly into the MX unit it will pair just fine. If however I move it to a switch port it can no long find the MX unit.
Couple of questions. Do the units have to be on the same subnet? Currently the MX is on 172.21.143.22 and touch is on 172.21.205.13. Both are on the same VLAN however the Touch never finds the codec.
we have discovered with an SX20 and Touch 8 pairing.
1) Our touchpad is on a different subnet / VLAN - and although it connects - the SX20 web interface (Configuration / Peripherals) doesnt show connected AND it doesnt show an IPv4 IP address - it is paired via IPV6 (even though the codec has IPV6 turned off - go figure?)
2) Our touchpad freezes intermittently.
3) If we enter a static IP on the touchpad - same subnet - it wont even see the codec - and we believe this is due to different VLANs for the wired connection (patch panel / switch ports).
4) Our resolution is to enter a static IP on the same subnet/vlan as the codec and ensure the patchpanel / switchports are correctly configured.
I wouldn't think that the Touch would pair with the codec over IPv6 if the IPv6 was actually disabled. Are you sure it's actually turned off (ie, the Network IPStack is set to "IPv4", not "Dual") not just having the CallProtocolIPStack set to IPv4?
If you check an "ifconfig" on the device at the "root" level, is it showing that IPv6 is active - mine (with the Network IPStack setting as IPv4) only shows an inet addr for the eth0 interface, not an inet6 addr.
I am having the same issue with the Touch 10 over the network - did you ever get this work correctly and if so what were your findings? I have tried on both the same subset and a different one but it can not see the MX300 G2. I have not been able to find much information about setting up the Touch 10.
IntroductionCUCM Routing RulesDial String implementation PolicyCUCM Routing LogicSIP URI Call Routing Analysis+++ Case Study: 1 ++++++ Case Study: 2 +++Conclusion
Over the last few months, I have had the privilege of working on SI...
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...