7921 gap in pickup

Unanswered Question

Ok, I will install 1.1.1...


The only thing is, there is a local phonebook again on the phones... Any idea how this can be disabled ...

We don't like the use of a local phonebook on the phone itself because it's lost when the phone is broken...

The users should create the phonebook via intranet and use it with the services ...

g.rienstra Mon, 03/31/2008 - 09:38
User Badges:

Hi,


i have the identical issue with 1.0.5 and 1.1.1

What i see is that when i call a 7921 i have a 2 sec gap. If i disconnect the call and immidiately call the same 7921 again i do not have the issue.

This seems something related to Power save, if the phone is awake i do not have the issue.

Do you notice the same?


I wander if this is not a config issue?

The doc's mention to disable arp unicast (when using a controller) however for some third party wireless phones its recommended to enable this feature. worth a try ?


Reg

Goen

migilles Mon, 03/31/2008 - 09:43
User Badges:
  • Cisco Employee,

With 1.04 and later, we do not wake up on each DTIM if the AP is advertising proxy ARP support per CCX IE.

If you enable arpunicast then you are disabling proxy arp, which is NOT what you want. Enabling this has caused other issues with L3 mobility as well as non-optimal battery life.

Assume you are referring to a small delay for ring in and not delay after answering the call.

Also not sure which WLC version and AP platform you have.

We recommend to use 4.2.61.0 or later with AP1130 or AP1240.

g.rienstra Mon, 03/31/2008 - 09:52
User Badges:

We are still running WLC (4404) version 4.0.179.11 and combined 1130/1242 APs.

The delay we hear is actually in the voice path (2 seconds gap after answering the call)


G

migilles Mon, 03/31/2008 - 12:28
User Badges:
  • Cisco Employee,

We advise to use 4.0.217.0 or later for 4.0 code, but ideally 4.2 and later.

I would capture a sniffer trace, could be an issue w/ ARPs not getting responded to quick enough. Other than that may want to open a TAC case to proceed troubleshooting further.

Actions

This Discussion