CUCM 11.0.1.22900-14 strange pickup issues

[Joel Lallemand]

Hi all

We updated our CUCM-Clusters last weekend from 11.0.1.21900-14 to 11.0.1.22900-14. After that, we observed that some calls cannot be picked up anymore. If pickup is pressed, the call ends immediately and the caller hears fast busy. We observed it with several phone models (7841, 8851). Resetting, deleting and factory resetting the phones didn't help. We also deleted the pickup-group and configured it new.

Using RTMT, we saw the following error during pickup:

2016/08/30 07:38:35.734|SIPL|0|TCP|IN|172.21.11.x|5060|SEPDC7B9476A8xx|172.21.192.x|49764|3,100,14,730.2059^172.21.192.x^*|4489159|dc7b9476-a8670596-77020748-106fe6ce@172.21.192.x|INVITE
2016/08/30 07:38:35.735|SIPL|0|TCP|OUT|172.21.11.x|5060|SEPDC7B9476A8xx|172.21.192.x|49764|3,100,14,730.2059^172.21.192.x^*|4489160|dc7b9476-a8670596-77020748-106fe6ce@172.21.192.x|100 Trying
2016/08/30 07:38:35.738|CC|SETUP|51093424|51093425|jane.doe@xy.com|05843xxxxx|05843yyyyy 2016/08/30 07:38:35.747|CC|OFFERED|51093424|51093425|05843xxxxx|05843yyyyy|05843yyyyy|SEPDC7B9476A8xx|SEP64168DBB7Cyy
2016/08/30 07:38:35.748|SIPL|51093424|TCP|OUT|172.21.11.x|5060|SEPDC7B9476A8xx|172.21.192.x|49764|3,100,14,730.2059^172.21.192.x^SEPDC7B9476A8xx|4489162|dc7b9476-a8670596-77020748-106fe6ce@172.21.192.x|180 Ringing
2016/08/30 07:38:40.745|CC|RELEASE|51093425|0|0 2016/08/30 07:38:40.745|CC|SETUP|51093424|51093431|jane.doe@xy.com|05843yyyyy|05843yyyyy
2016/08/30 07:38:40.753|CC|OFFERED|51093424|51093431|05843xxxxx|05843yyyyy|05843yyyyy|SEPDC7B9476A8xx|SEP64168DBB7Cyy
2016/08/30 07:38:40.754|SIPL|51093424|TCP|OUT|172.21.11.1x5060|SEPDC7B9476A8xx|172.21.192.x|49764|2,100,14,551677.19^172.22.224.x^*|4489284|dc7b9476-a8670596-77020748-106fe6ce@172.21.192.x|480 Temporarily Not Available
2016/08/30 07:38:40.758|SIPL|51093424|TCP|IN|172.21.11.x|5060|SEPDC7B9476A8xx|172.21.192.x|49764|3,100,14,730.2061^172.21.192.x^*|4489285|dc7b9476-a8670596-77020748-106fe6ce@172.21.192.x|ACK 2016/08/30 07:38:40.758|CC|RELEASE|51093424|51093431|41

Also Cisco Jabber (11.5.4) sometimes didn't show the pickup information when calling on a hunt with pickup. That worked with SU1.

Does anyone knows this issue?

Thanks for your help!

[Manish Gogna · Accepted solution]

Hi Joel,

If only SIP phones are affected by this then it can be the following bug

https://bst.cloudapps.cisco.com/bugsearch/bug/CSCva71953/?reffering_site=dumpcr

You will need an upgrade to the ES for 11.0.1 with the fix.

Manish

[Joel Lallemand]

Hi Manish

You're right. We configured the directory uri on the Directory Number configuration page and pickup worked!!

Thanks a lot for your fast response! Great job.

[Manish Gogna]

Good to know that it worked, thanks for updating the post for the benefit of all.

Manish

[Joel Lallemand]

Hi all

Problem still persists when calling on a hunt pilot, where no direcory uri can be defined...is there another workaround?

[Manish Gogna]

Hi Joel,

Unfortunately there doesn't seem to be a workaround for the hunt pilot, you may open a TAC case to get the ES for 11.0.1 with a fix or check the release notes of latest 11.5 on cisco.com and see if the bug is fixed in that and upgrade to the same.

Manish