UC QoS

ref

https://thevoiceman.wordpress.com/2011/10/19/configuring-voice-qos/

DIal-Peer Binding issue

Cisco UC gotcha is "Unable to add dial peer binding while there is an active session".


My solution:

For inbound call, we rerouted all call to different SIP circuit

First, you can get a good overview of active calls with the command 

#show call active voice (It may say no active call but look for the call legs:##)

#Show call active voice compact (It will show list of active call session on CUBE and number associated with it)

"ANS" Meaning= This number initiated call(calling Number)

"ORG" Meaning= This number received call(Called Number)

#sh voip rtp connections (It will show remote end and end point ip address for active session)

Note***If you only get ITSP IP address as remote and Endpoint most likely those calls are hung call on CUBE.

The command to Clear hung calls:
"clear call voice causecode 1  called-number 91414XXXXXXX"
"clear call voice causecode 17 calling-number 91414XXXXXXX"

clear call voice causecode identifier{id identifier | media-inactive | calling-number number |called-number number}



what is cause-code:


Then we open a d ticket with Cisco on this issue. Open Cisco Recommendation was:

Below are the commands to forcefully shut down the sip service on CUBE.

Router# conf t
    Voice service voip
    Sip
    Call service stop forced
====
This will get rid of all sip sessions (existing and transient)
"Personally I do not agree with Cisco about force stop we should do graceful stop.Then again we were waiting for one call to finish to half an hour then called that guy and asked him to hang up. lol"

The way to monitor whether calls failover to secondary or a backup CUBE is to run show commands/debugs on the expected backup/secondary CUBE


“show sip sessions brief”
Show call active voice brief

Debug voip ccapi inout
Debug ccsip messages



Solution 1:

Solution 2:

ref: 
https://supportforums.cisco.com/t5/collaboration-voice-and-video/unable-to-stop-voice-call-processing-on-a-cisco-ios-gateway/ta-p/3133040
https://supportforums.cisco.com/t5/collaboration-voice-and-video/cube-sip-media-and-signalling-binding-to-an-interface/ba-p/3107153
http://ucpros.net/cisco-sip-gateway-configuration/

Never SCCP again

Optimus Prime

Prime Collaboration Deployment

Prime Collaboration Assurance

Setting up Devices for Prime Collaboration Assurance Click

Prime Collaboration

Prime License Manager

VG 204/224

Things need to know for Analog and FAX gateway:

VG config using SCCP
*************************************
! stcapp ccm-group <groupnum> 
stcapp 
! voice-card 0 
! 
! voice service voip 
modem passthrough nse codec g711ulaw 
! sccp ccm <ipaddr> identifier <idnum1> 
sccp ccm <ipaddr> identifier <idnum2> 
sccp 
! sccp ccm group <groupnum> 
associate ccm <idnum1> priority 1 
associate ccm <idnum2> priority 2 
! 
! dial-peer voice <dialpeer1> pots 
service stcapp 
port 2/0 
! dial-peer voice <dialpeer2> pots 
service stcapp 
port 2/1 
! 
******************************************************

Cisco VG224 Configuration Example Click Here

For FXO line on cisco IOS router that remains connected even after the call ends

#Power denial-based supervisory disconnect

#Ground-start signalling disconnect

#Tone-based supervisory Disconnect

#disconnect-ack 


T-shoot:

The FXS ports on the VG224 Voice Gateway do not go off-hook, which results in a fast busy tone Click Here

Fax Pass-through Click here 

Useful Handy command

Linux system shutdown Command
#shutdown -h now
#

DB issue.

well well well..Where do I start.It's like the scariest word on planet Earth for me. One time I saw some unusual behavior on our cluster I told my architect then he goes "Please don't give me heart attack" Lol


The project I am working on has supercluster.We have like 10 Subscriber,1 Publisher, and 2 TFTP server. Not bad huh! It's been more than a year we are being hunted by this Db issue now and then we spend countless house week weekend on a call with Cisco trying figure out if we can find the root cause and fix it.

Well, we were able to fix database temporary but we were never lucky enough to find any valid root cause.I will try to see if I can get the story from the beginning but for now, we will just have to stick with what happened next.

email copied from TAC finding name has been changed for security reason.

Problem Description:

Phones are in rejected state when they are failed over to secondary node

Action Plan:

As discussed, please find the summary of the Webex we had:

++ If the phone is associated to the device pool with only secondary node, it registers fine

++ If the phone is associated to the device pool with primary and secondary node, phone fails over fine with secondary

++ Issue is only with one particular device pool

++ Took CCM traces, App and Sys logs, pcaps from secondary node, TFTP logs

++ From pcaps, phone sends a register request and receive a 404 not found from the CUCM, as it is not present in the database

Warning: 399 XYZ-CUCMSUB-01 "Unable to find device/user in database"

++ With SQL query we can see that the phone is present in the database

++ Checked replication, its fine

++ From CCM traces, it shows that phone is in DB but it cannot find that it is a member of CM group of the same device pool

81068379.007 |15:08:57.507 |AppInfo  |Device=SEP123456789 in DB already but cannot register. isDeviceNameAllowedToRegister=CallManager Pkid(3a5-880) is not a member of Call Manager Group(PPP-CMG) (isCallManagerMemberOfDevicePool)

++ Created a new DP with all same subs in it

++ phone registers fine with secondary node if primary is down

As per the observation, it looks like the above error was happening because of the RIS Data Collector Service having incorrect information about this phone (since we are testing with one) that was trying to register. Even though the phones were not registered on the first subscriber in the group, the RIS DC assumed that the phones were using the old node in the CCM group This is why we see " SEP123456789” in DB already but cannot register.

After making new CM group, we noticed that the subscriber was having incorrect status of phones and Publisher was now showing right status of phones. Since RIS DC interfaces the memory between CCM and Tomcat, it looked like Tomcat was not picking the right entries from its memory, which RIS DC has to provide.

Action Plan –

++ Restart RIS DC, Tomcat and CCM service for that node

++ For further RCA, please collect detailed logs:

1) CUCM

2) TFTP

3) RIS

4) APP and sys logs

Wanna Learn More Click Here