Moshimoshi
Technical User
I'm vexed. I've been working with network services for a while now trying to curtail a problem we're having where our 4610SW IP phones ignore the MCIPADD line in our DHCP scopes and seem to grab another address (instead) arbitrarily.
But, because of our network topology, we cannot have these phones using the CLAN they're trying to jump too.
(NOTE: we're in the middle of an IP change, I've asked about this before and didn't get much input). Our data network moved to 10.150.xx.xx addresses before, from 10.130.xx.xx addresses. The routing is perfect, we can ping back and forth and route packets from 10.150 to 10.130 and back again, we tested this repeatedly, it doesn't seem to be the proble, and we exhausted the possibility that it was)
Basically. the MCIPADD line in DHCP states that the phones need to use 10.130.1.60 as the choice CLAN, since its local, vs. taking some very long packet trips out of T1's to another site.
When we register the phones...for example, I see...
10:37:04 rcv GRQ endpt 10.150.17.120:49300 switch 10.130.1.60:1719 ext
10:37:04 snd GCF endpt 10.150.17.120:49300 switch 10.130.1.60:1719 ext 5359
10:37:04 rcv RRQ endpt 10.150.17.120:49300 switch 10.150.121.2:1719 ext 5359
10:37:05 snd RCF endpt 10.150.17.120:49300 switch 10.150.121.2:1719 ext 5359
And the phone skips to 10.150.121.2 as a call server. Why? I don't understand how its ignoring our DHCP scope MCIPADD pref for 10.130.1.60 when the phones can (and do) use it when we force them too, but we don't want to have to set a static IP on every IP phone in the company.
This needs to be resolved so that we can do firmware updates to finish our IP move...
Anyhow have any thoughts?
~Sean
-----------------------
Telecom Analyst, FOI.\\\\_______________