[cisco-voip] IP Communicator over wiFi

[Erick Bergquist]

I just saw the problem on the same model HP model laptops with AMD
chipsets, but can't recall wireless chipset with a older Cisco
Wireless AP.

On Thu, Apr 24, 2008 at 9:18 AM, Paul Lakra <plakra at planer.co.uk> wrote:
>
> One is an Acer Ferrari 1005 with an AMD Turion 64 and Broadcom 802.11n
> chipset. The other is an Acer Travelmate with an Intel Centrino processor
> and Intel 915 wireless chipset. I am more inclined to think it has something
> to do with the chipset in the Access point.
>
> There are a load of settings for the chipset in the laptop.
>
>
>
>
>  From: "Erick Bergquist" <erickbee at gmail.com>
>  To:
> "Matthew Saskin" <matt at saskin.net>
>  Cc: "Paul Lakra" <plakra at planer.co.uk>, cisco-voip at puck.nether.net
>  Date: 24/04/2008 14:39
>  Subject: Re: [cisco-voip] IP Communicator over wiFi
>  ________________________________
>
>
>
>
>
> I have seen similar issue with earlier and current IP Communicator
>  versions, on laptops with a AMD processor. I forgot what the Wireless
>  chipset was offhand, but a Laptop with a Intel processor and different
>  Wireless chipset worked fine next to the AMD laptop that sat and spun
>  with IP Comm.  Didn't matter what the MAC was set to.  But when you
>  plugged in Cat5 CIPC came right up. I haven't had a chance to really
>  look more into the problem yet. Regular data (web, outlook, etc)
>  worked fine though over wifi. I don't think it is a CIPC issue, but
>  maybe an issue with certain wireless chipsets and AP models maybe. Is
>  weird though.
>
>
>  On Thu, Apr 24, 2008 at 6:55 AM, Matthew Saskin <matt at saskin.net> wrote:
>  > Disregard - I missed your public AP comment
>  >
>  >  -matt
>  >
>  >
>  >
>  >  Matthew Saskin wrote:
>  >  > What method of identifying the device are you using, MAC address or
>  >  > "dummy" MAC address/username?  If the former, do you have two device
>  >  > entires in CallManager, one for the wired MAC and one for the wireless
> MAC?
>  >  >
>  >  > -matt
>  >  >
>  >  > Paul Lakra wrote:
>  >  >
>  >  >> This happens with 2 users. IP Communicator 2.1.3.0 installed on
> laptop
>  >  >> running Windows XP Pro.
>  >  >>
>  >  >> Works fine in the office on a wired LAN
>  >  >> At home on a Buffalo wireless access point (Wireless G - about 4
> years
>  >  >> old) behind a Linksys router the IP sits registering for ever. WPA
>  >  >> encryption is used. If a wired ethernet link is made to the router
> via
>  >  >> a hub the phone immediately registers and works OK.
>  >  >> When connecting to public access points as in hotels everything works
>  >  >> fine.
>  >  >>
>  >  >> No adjustments are made to the laptop between any of the above
> scenarios.
>  >  >>
>  >  >> There are no QoS options in the access point.
>  >  >>
>  >  >> I think I saw something a while ago about D-Link wireless access
>  >  >> points not working. Is this the same thing?
>  >  >>
>  >  >> Paul
>  >  >>
> ------------------------------------------------------------------------
>  >  >>
>  >  >> _______________________________________________
>  >  >> cisco-voip mailing list
>  >  >> cisco-voip at puck.nether.net
>  >  >> https://puck.nether.net/mailman/listinfo/cisco-voip
>  >  >>
>  >  >>
>  >  >
>  >  > _______________________________________________
>  >  > cisco-voip mailing list
>  >  > cisco-voip at puck.nether.net
>  >  > https://puck.nether.net/mailman/listinfo/cisco-voip
>  >  >
>  >
>  >  _______________________________________________
>  >  cisco-voip mailing list
>  >  cisco-voip at puck.nether.net
>  >  https://puck.nether.net/mailman/listinfo/cisco-voip
>  >
>
>
>
> _______________________________________________
>  cisco-voip mailing list
>  cisco-voip at puck.nether.net
>  https://puck.nether.net/mailman/listinfo/cisco-voip
>
>