Bug in CCA 2.2.2?

Unanswered Question
Apr 20th, 2010

Hi,


I've had two similar problems with two new UC500 boxes with software release 8.0.2 and CCA 2.2.2. The problem occurs when incoming DID dial-plans are modified or added using the CCA. Translation-rules, dial-peers and dial-plans get's altered, added and old rules are not deleted correctly which causes incoming calls to be diverted to wrong dial-plans or translation-rules. This caused all incomming calls to a client to fail.

In the first case all incomming DID calls were diverted to a POTS dial-plan that was'nt even visible in CCA and the only trunk configured was a SIP trunk. After trying to start from scratch with deleting all dial-plans, trunk settings and so on in CCA I was able to get thier SIP-trunk main number going to the AA. Incoming to DID still failed. I called the TAC and spent about 4 hours on the phone solving the case.

Dial-plans, translation-rules and dial-peers had to be redone using CLI. The dial-peers debuging showed the call coming in but the media type was'nt accepted and call was rejected. The engineer switched the codec to G.729 for it to work. (Never had to do this before). The CCA had totally wreaked havoc on the config whitout showing any irregularities in CCA other then newly added DID dial-plans that disappear when hitting the apply button.

Is this a known bug or I'm I first to be affected?

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Steven DiStefano Tue, 04/20/2010 - 13:52

Hi Markus,

I inquired within our Engineering team about this earlier.  No, this is not  known issue. In fact, we would need to see you logs to proceed further and need more detail about the exact steps you followed to see the issue....

Perhaps the best thing to do is open a support case please...

treating your report with seriousness, we did the following:


1) Configured T1 trunk
2) Created DID dial plans with T1 trunk
3) Translation rules, translation profiles, dial peers are created.
4) Configured AT&T SIP trunk
5) Edited the previously created dial plan and chose SIP trunk instead of T1
6) Previously created configuration is deleted and new translation rules,
profiles and dial peers are created.

See below config. delivered for step 6.

no voice translation-rule 5
no voice translation-rule 6
no voice translation-rule 7
no voice translation-rule 8
no voice translation-rule 9
no voice translation-rule 10
no voice translation-profile t1_Called_5
no voice translation-profile t1_Called_6
no voice translation-profile t1_Called_7
no voice translation-profile t1_Called_8
no voice translation-profile t1_Called_9
no voice translation-profile t1_Called_10
no dial-peer voice 3000 
no dial-peer voice 3001 
no dial-peer voice 3002 
no dial-peer voice 3003 
no dial-peer voice 3004 
no dial-peer voice 3005 
voice translation-rule 11
rule 1 /4085551000/  /100/
rule 2 /4085551001/  /101/
rule 3 /4085551002/  /102/
rule 4 /4085551003/  /103/
rule 5 /4085551004/  /104/
rule 6 /4085551005/  /105/
rule 7 /4085551006/  /106/
rule 8 /4085551007/  /107/
rule 9 /4085551008/  /108/
rule 10 /4085551009/  /109/
exit
voice translation-rule 12
rule 1 /4085551010/  /110/
rule 2 /4085551011/  /111/
rule 3 /4085551012/  /112/
rule 4 /4085551013/  /113/
rule 5 /4085551014/  /114/
rule 6 /4085551015/  /115/
rule 7 /4085551016/  /116/
rule 8 /4085551017/  /117/
rule 9 /4085551018/  /118/
rule 10 /4085551019/  /119/
exit
voice translation-rule 13
rule 1 /4085551020/  /120/
rule 2 /4085551021/  /121/
rule 3 /4085551022/  /122/
rule 4 /4085551023/  /123/
rule 5 /4085551024/  /124/
rule 6 /4085551025/  /125/
rule 7 /4085551026/  /126/
rule 8 /4085551027/  /127/
rule 9 /4085551028/  /128/
rule 10 /4085551029/  /129/
exit
voice translation-rule 14
rule 1 /4085551030/  /130/
rule 2 /4085551031/  /131/
rule 3 /4085551032/  /132/
rule 4 /4085551033/  /133/
rule 5 /4085551034/  /134/
rule 6 /4085551035/  /135/
rule 7 /4085551036/  /136/
rule 8 /4085551037/  /137/
rule 9 /4085551038/  /138/
rule 10 /4085551039/  /139/
exit
voice translation-rule 15
rule 1 /4085551040/  /140/
rule 2 /4085551041/  /141/
rule 3 /4085551042/  /142/
rule 4 /4085551043/  /143/
rule 5 /4085551044/  /144/
rule 6 /4085551045/  /145/
rule 7 /4085551046/  /146/
rule 8 /4085551047/  /147/
rule 9 /4085551048/  /148/
rule 10 /4085551049/  /149/
exit
voice translation-rule 16
rule 1 /4085551050/  /150/
exit
voice translation-profile t1_Called_11
translate called 11
exit
voice translation-profile t1_Called_12
translate called 12
exit
voice translation-profile t1_Called_13
translate called 13
exit
voice translation-profile t1_Called_14
translate called 14
exit
voice translation-profile t1_Called_15
translate called 15
exit
voice translation-profile t1_Called_16
translate called 16
exit
dial-peer voice 3006  voip
no vad
description t1
incoming called-number 408555100.
translation-profile incoming t1_Called_11
session protocol sipv2
session target sip-server
rtp payload-type cisco-codec-fax-ind 98
dtmf-relay rtp-nte
ip qos dscp ef media
ip qos dscp ef signaling
voice-class sip dtmf-relay force rtp-nte
exit
dial-peer voice 3007  voip
no vad
description t1
incoming called-number 408555101.
translation-profile incoming t1_Called_12
session protocol sipv2
session target sip-server
rtp payload-type cisco-codec-fax-ind 98
dtmf-relay rtp-nte
ip qos dscp ef media
ip qos dscp ef signaling
voice-class sip dtmf-relay force rtp-nte
exit
dial-peer voice 3008  voip
no vad
description t1
incoming called-number 408555102.
translation-profile incoming t1_Called_13
session protocol sipv2
session target sip-server
rtp payload-type cisco-codec-fax-ind 98
dtmf-relay rtp-nte
ip qos dscp ef media
ip qos dscp ef signaling
voice-class sip dtmf-relay force rtp-nte
exit
dial-peer voice 3009  voip
no vad
description t1
incoming called-number 408555103.
translation-profile incoming t1_Called_14
session protocol sipv2
session target sip-server
rtp payload-type cisco-codec-fax-ind 98
dtmf-relay rtp-nte
ip qos dscp ef media
ip qos dscp ef signaling
voice-class sip dtmf-relay force rtp-nte
exit
dial-peer voice 3010  voip
no vad
description t1
incoming called-number 408555104.
translation-profile incoming t1_Called_15
session protocol sipv2
session target sip-server
rtp payload-type cisco-codec-fax-ind 98
dtmf-relay rtp-nte
ip qos dscp ef media
ip qos dscp ef signaling
voice-class sip dtmf-relay force rtp-nte
exit
dial-peer voice 3011  voip
no vad
description t1
incoming called-number 4085551050
translation-profile incoming t1_Called_16
session protocol sipv2
session target sip-server
rtp payload-type cisco-codec-fax-ind 98
dtmf-relay rtp-nte
ip qos dscp ef media
ip qos dscp ef signaling
voice-class sip dtmf-relay force rtp-nte
exit

David Trad Tue, 04/20/2010 - 15:07

Hi Steve,

No, this is not  known issue. In fact,

I am not sure why this is not a known fact, as it has been reported quite a few times including myself of this happening :(

If you are able to look over my post history, you will see my biggest gripes/complaints about CCA are the following:

  • Excessive code being left behind
  • Making changes in CCA and then CCA modifying code that has ot relevance to the changes made by the user, and breaking things, thus requiring much time on the CLI debugging things, often it is just best to do the work by hand

Those are the two main issues that disappoint me the most, they can cause you many hours of lost sleep, and plenty of gray hair to go with that as well.

My only advise i can give to Markus, is that make one change at a time with CCA, then check and see what it has updated in the background, and always make sure you have taken a backup of the config prior to doing this, otherwise you might regret it, and CCA will become a sware word to you :)

Cheers,

David.

Steven DiStefano Tue, 04/20/2010 - 17:39

I am not arguing that there havent been issues with CCA since I started playing with it in 1.1 release.  And I dont dispute your posts.  But posts become dated and aged, and new CCA releases come out, and I dont know anyone that goes back to revisit all their old posts to see if they are still valid.

However I know for a fact this happens with CDETS (which are derived from TAC cases).  We do check a new release addresses a CDETS and we close cases as a result.

Now if you want to give me a case that defines this Partners problem I am open to looking for it and telling you what we know about it.  But this isnt a case (yet) and I think it should be when it happens.  What we did was try it ourselves after confirming it is NOT known.  I dont just say things like that without doing the homework.

Having said that, you advise is sound and prudent, but CCA is able to accomplish this task if we interpreted it correctly.

Steve

m.junghage Wed, 04/21/2010 - 00:36

Hi Steve,

I'm glad that Cisco is taking this serious. I will pm the TAC case number regarding this case so you can see the debugs and solution.

I'm thinking that the initial "Telephony wizard" have something to do with the unwanted POTS dail-peers lingering in the config, since it won't let me go through the guide without configuring at least 1 FXO/BRI even though I'm not planning on using them. After the config is read to the device I delete the traces left behind and shutdown the FXO/BRI ports.