asterisk users - Oct 2008 - Budge Tones pick up wrong calls

We have 3 Grandstream Budge Tone 100 phones which are being very fluid 
on incoming calls.  They are set up as extensions 2501, 2518, and 2536.  
When calling out to another phone, they always identify themselves 
correctly.  But sometimes they will respond to the wrong incoming 
calls.  (By respond, I mean that the phone rings and if someone picks up 
the receiver, the call then goes thru.)  For example, 2501 might respond 
to the calls for 2518.  After a reboot, it might decide to respond to 
2501 as it should.  Or it might respond to 2536.  The phone it responds 
for will not respond.
I don't know whether to look in the settings on the phone or in an 
Asterisk setting, and what setting to check in either place.  Has anyone 
seen this behavior before?
--Paul

-- 
Paul Douglas Franklin
Computer Manager, Union Gospel Mission of Yakima, Washington
Husband of Danette
Father of Laurene, Miriam, Tycko, Timothy, Sarabeth, Marie, Dawnita, Anna Leah,
Alexander, and Caleb

First of all, are the handsets using distinct SIP peers?  Are they set 
up statically or to register?

Secondly, unless you are using an Ethernet hub, SIP signaling data 
destined for one phone should not go to another.

Paul Douglas Franklin wrote:
> We have 3 Grandstream Budge Tone 100 phones which are being very fluid 
> on incoming calls.  They are set up as extensions 2501, 2518, and 2536.  
> When calling out to another phone, they always identify themselves 
> correctly.  But sometimes they will respond to the wrong incoming 
> calls.  (By respond, I mean that the phone rings and if someone picks up 
> the receiver, the call then goes thru.)  For example, 2501 might respond 
> to the calls for 2518.  After a reboot, it might decide to respond to 
> 2501 as it should.  Or it might respond to 2536.  The phone it responds 
> for will not respond.
> I don't know whether to look in the settings on the phone or in an 
> Asterisk setting, and what setting to check in either place.  Has anyone 
> seen this behavior before?
> --Paul
> 

-- 
Alex Balashov
Evariste Systems
Web    : http://www.evaristesys.com/
Tel    : (+1) (678) 954-0670
Direct : (+1) (678) 954-0671
Mobile : (+1) (706) 338-8599

Are you using NAT?

On Fri, Oct 10, 2008 at 4:24 PM, Paul Douglas Franklin <pdf at yugm.org>
wrote:
> We have 3 Grandstream Budge Tone 100 phones which are being very fluid
> on incoming calls.  They are set up as extensions 2501, 2518, and 2536.
> When calling out to another phone, they always identify themselves
> correctly.  But sometimes they will respond to the wrong incoming
> calls.  (By respond, I mean that the phone rings and if someone picks up
> the receiver, the call then goes thru.)  For example, 2501 might respond
> to the calls for 2518.  After a reboot, it might decide to respond to
> 2501 as it should.  Or it might respond to 2536.  The phone it responds
> for will not respond.
> I don't know whether to look in the settings on the phone or in an
> Asterisk setting, and what setting to check in either place.  Has anyone
> seen this behavior before?

Paul Douglas Franklin wrote:
> When calling out to another phone, they always identify themselves 
> correctly.  But sometimes they will respond to the wrong incoming 
> calls.  (By respond, I mean that the phone rings and if someone picks up 
> the receiver, the call then goes thru.)  For example, 2501 might respond 
> to the calls for 2518.  After a reboot, it might decide to respond to 
> 2501 as it should.  Or it might respond to 2536.  The phone it responds 
> for will not respond.
>   
I have seen this with Polycom phones. In my case the problem turned out 
to be because there were several phones behind NAT and the NAT router 
got a little confused. The only solution I could find was to have the 
phones use different ports - ie. 5060, 5061, 5062. When they all shared 
5060 the NAT router was unable to keep track of where an incoming call 
should be routed to.

Hope this helps,
Trevor

This sounds like a likely source of the problem.  I changed the ports on 
two of the phones and the problem seems to have gone away.  Thank you, 
Trevor, and others who responded.
--Paul

Trevor Peirce wrote:
> I have seen this with Polycom phones. In my case the problem turned out 
> to be because there were several phones behind NAT and the NAT router 
> got a little confused. The only solution I could find was to have the 
> phones use different ports - ie. 5060, 5061, 5062. When they all shared 
> 5060 the NAT router was unable to keep track of where an incoming call 
> should be routed to.
-- 
Paul Douglas Franklin
Computer Manager, Union Gospel Mission of Yakima, Washington
Husband of Danette
Father of Laurene, Miriam, Tycko, Timothy, Sarabeth, Marie, Dawnita, Anna Leah,
Alexander, and Caleb