Mobility Server and UC500 Bug
Just wanted to let you guys know I ran into a BUG with Mobility server and UC500. It seems that you can not use Autoattendant with Mobility. It needs to be a direct inward dial (DID) number only. I have a Main number ring a few users and then go to AA is it is not picked up. The message says "press the parties extension now, or #2 to dial by name etc. etc.
When the caller enters an extension like for instance extension 102, the AA forwards in to 102 but the SIP message (wehn debugging) doesnt forward extension 102, it appends some garbage in front of the extension and Mobility server and UCC (Call Connector) does not see the extension as 102, so it does not run any rules that you set up.
I have a case open with Cisco and it is a BUG right now.
They say it should be fixed within a week or two.
- Login or register to post comments
- Email this Forum topic
UC500 Rss Feed
Popular Tags
Active forum topics
- how to setup auto attendent feature using UC520 series.
- Problem in registering IP communicator (cisco sw phone) to UC500 via VPN
- configuring rollover with 4 port FXO
- UC520 and Windows SBS2003
- No call out and incomming calls
- Analogue trunk with UC520
- When I connect via VPN client I can not ping other computers on remote site
Cisco TAC Issues - CME - UE
- JPN: 7921 XML Services are displayed as squares , Open CSCsq42134
- CME DN 'description' command may allow for open-ended quote delimination , Open CSCsq48167
- forwarded MLPP call caller ID corrupted , Open CSCso13941
- Memory Leak - "Presence Process" , Open CSCsq41189
- CME/SRST with dialpalan does not remove dial-peer after IP phone unreg. , Open CSCsq34098
FIXED!!!!!
Just got a couple of the latest images from TAC and it looks like they have finally cleaned up this bug!!
RE: Mobility Server and UC500 Bug
Correct, the cause of the problem has been identified. DDTS CsCsq22702 will eventually be duplicated to CSCsq24129, which is the real cause of the SNR failure. The problem affects both UC500 and ISRs.
O.K. I received a call from
O.K. I received a call from Cisco Today... they have a fix that is due out tomorrow June 5th. So if you have been having this problem, open a TAC request to get a IOS upgrade patch to the UC500.
John
NIKTEK LLC
Same problem here
Been having this problem since 1.3 and still happening in 1.4 with our UC500. Same call flow scenario applies.
Everything in UCC seems to work fine except when the AA forwards to a users extension. Also had a problem when trying to transfer to an extension when using full-blind transfer-system and UCC wouldn't pick up the call. Once I switched it back to full-consult the transfers started working with mobility but still had the same problem with the AA.
I also have a case open with Cisco for this particular problem. The bug DDTS number is CsCsq22702.
Do you know if this problem is specific to the UC500 and not the ISRs?