<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
</head>
<body bgcolor="#ffff99" text="#000000">
In case this is useful to others, a tip...<br>
<br>
I moved one of my Polycom 501's off it's subnet to another one (I've
got an ether bridge glued to the back of the phone and a wireless card
in the * box acting as AP). Now it
is still served by the same Asterisk box, albeit through another
ethernet port. It works just fine, except that on incoming calls, the
full SIP address is displayed for the caller number. I was initially
puzzled until I realized that the phone was simply qualifying the
address of the caller because it was in a domain that is different than
it's own - technically. But my users don't do "technically", and come
to think of it, I don't like it either.<br>
<br>
The fix: use iproute2 to mangle the packets:<br>
<br>
BEFORE:<br>
<br>
root@pig:/home/ftp/polycom4# ip ro sh<br>
192.168.20.0/24 dev eth0 proto kernel scope link src 192.168.20.3 <br>
192.168.99.0/24 dev ath0 proto kernel scope link src 192.168.99.1 <br>
71.245.116.0/24 dev eth2 proto kernel scope link src 71.245.116.10 <br>
169.254.0.0/16 dev eth2 scope link metric 1000 <br>
192.168.0.0/16 via 192.168.20.65 dev eth0 <br>
default via 71.245.116.1 dev eth2 metric 100 <br>
<br>
FIX:<br>
<br>
root@pig:/home/ftp/polycom4# ip ro rep 192.168.99.0/24 dev ath0 proto
kernel scope link src 192.168.20.3<br>
<br>
AFTER:<br>
<br>
root@pig:/home/ftp/polycom4# ip ro sh<br>
192.168.20.0/24 dev eth0 proto kernel scope link src 192.168.20.3 <br>
192.168.99.0/24 dev ath0 proto kernel scope link src 192.168.20.3 <br>
71.245.116.0/24 dev eth2 proto kernel scope link src 71.245.116.10<br>
169.254.0.0/16 dev eth2 scope link metric 1000 <br>
192.168.0.0/16 via 192.168.20.65 dev eth0 <br>
default via 71.245.116.1 dev eth2 metric 100 <br>
<br>
Now the phone thinks it's "routing" to the * box, but ignorance is
bliss.<br>
<br>
Hope this helps someone.<br>
<br>
<br>
<br>
</body>
</html>