Iam Working as Technical Community Manager for the Voice and Unified communications domain. I will be focusing on IP Telephony and Unified Communication as Community Manager and driving the Document/Videos/Blog Creation and growth of CSC with Customers and Partners.
Introduction This document explains how to verify the Cisco Jabber DNS SRV configuration. How to verify the Cisco Jabber DNS SRV configuration? "NSLOOKUP" can be used to verify that the SRV records are correctly configured. This is particular important in environment where DNS configuration is handled by different organizational entities. Best use the NSLOOKUP from one of the Windows 7 PC to verify they can correctly resolve the SRV. By default, the NSLOOKUP tool queries either DNS A records - mapping a name to an IP address or PTR records mapping IP address to DNS names. To use the tool to check SRV records, First start nslookup (on a windows client ) start the command prompt and then enter nslookup Next set the query type to SRV -> set type = SRV After that insert the SRV record we need to check -> _cisco-uds._tcp.example.com This will return the DNS A records pointing to the CUCM servers. The following is an example of the _cisco-uds SRV record: _cisco-uds._tcp.example.com SRV service location: priority = 6 weight = 30 port = 8443 svr hostname = cucm3.example.com _cisco-uds._tcp.example.com SRV service location: priority = 2 weight = 20 port = 8443 svr hostname = cucm2.example.com Related Information Cisco Jabber DNS configuration guide
... View more
Introduction This document describes how to enable the Meetings Tab in the Jabber for windows client. Enable Meetings Tab on Cisco Jabber for Windows Client Set Meetings_Enabled to true/false to add/remove the Meeting Tab from Jabber for windows client. Using the key Meetings_Enabled in the jabber-config.xml should allow the user to change the configuration: ----Enables meetings capabilities in the client. Works in conjunction with the CalendarIntegrationType parameter. true (default) ----Enables meetings capabilities, allowing you to create meetings and get reminders to join meetings. false Disables meetings capabilities and user interface This setting can be enabled in the Jabber client by configuring policies in the jabber-config.xml file. <Policies> <Meetings_Enabled>true</Meetings_Enabled> <Voicemail_Enabled>true</Voicemail_Enabled> <EnableCallPickup>true</EnableCallPickup> <EnableHuntGroup>true</EnableHuntGroup> </Policies> The following is an example of a configuration file used in an on-premises deployment for all clients: <?xml version="1.0" encoding="utf-8"?> <config version="1.0"> <Client> <PrtLogServerUrl>http://server_name:port/path/prt_script.php</PrtLogServerUrl> <jabber-plugin-config> <browser-plugin> <page refresh="true" preload="true"> <tooltip>Cisco</tooltip> <icon>http://www.cisco.com/web/fw/i/logo.gif</icon> <url>www.cisco.com</url> </page> </browser-plugin> </jabber-plugin-config> </Client> <Options> <Set_Status_Inactive_Timeout>20</Set_Status_Inactive_Timeout> <StartCallWithVideo>false</StartCallWithVideo> </Options> <Policies> <Meetings_Enabled>true</Meetings_Enabled> <Voicemail_Enabled>true</Voicemail_Enabled> <Disallowed_File_Transfer_Types>.exe;.msi</Disallowed_File_Transfer_Types> </Policies> <Directory> <BDIPresenceDomain>example.com</BDIPresenceDomain> <BDIPrimaryServerName>dir.example.com</BDIPrimaryServerName> <BDISearchBase1>ou=staff,dc=example,dc=com</BDISearchBase1> <BDIConnectionUsername>firstname.lastname@example.org</BDIConnectionUsername> <BDIConnectionPassword>jabber</BDIConnectionPassword> <BDIPhotoUriSubstitutionEnabled>True</BDIPhotoUriSubstitutionEnabled> <BDIPhotoUriSubstitutionToken>sAMAccountName</BDIPhotoUriSubstitutionToken> <BDIPhotoUriWithToken>http://example.com/photo/sAMAccountName.jpg </BDIPhotoUriWithToken> </Directory> </config> Related Information Deployment and Installation Guide for Cisco Jabber, Release 10.5
... View more
Introduction This document describes the procedure to configure the Telephony features, Hunt group and Call Pickup group which are supported in Jabber for Windows (JFW)10.5. Configuring Telephony features in CUCM for Jabber Hunt Group A hunt group has to be configured on the CUCM and you will have to add the user line to the Group. To do that Logon to the CUCM admin interface and go the menu option "Call Routing -> Route/Hunt -> Line Group", find and select the group say "sales service" and add the user lines configured on Jabber clients. Select the Hunt options as shown here... Find the available DN to add to the line group and Select "Add to Line Group" and hit "save" Call Pickup Group Another Telephony feature supported with Jabber 10.5 and greater is Pickup Group. To activate the pickup functionality the Pickup group has be associated with the DNs lines configured for Jabber client Navigate to "Call Routing -> Directory Number" - Find and select the DNs configured for jabber scroll down and select the "Call pickup group" configured and hit "save" Repeat the same step for the other Directory number and configure the Call Pickup group. Check this link for, Enabling the Hunt Group & Pickup tab in the Jabber for Windows client Related Information Enabling the Hunt Group & Pickup tab in the Jabber for Windows client Jabber for windows Administration Guide
... View more
I can find a very good content on AA configuration.. This may help you to check the configurations you made on CME
... View more
In this document we will see how to configure the configurable SIP error codes to override the SIP error code response on CUBE.
In case of Total-call thresold configured using CAC, we just send a "503 service unavailable" response when the threshold is exceeded. Sending a more meaningful response back to the initiating party when a certain CAC threshold is exceeded allows for the initiating party to take appropriate action and makes troubleshooting easier.
In this example we will see how to configure the SIP error codes for CUBE to send " “502 Total Number of Calls Allowed Exceeded” when the total call limit on CUBE is exceeded.
Configuring SIP Error code
1. Configure Error code at the dial-peer level when total-calls are exceeded
The error-code-override command can either be configured globally or under the dial-peer.
CUBE(config)#call threshold global total-calls low 1 high 1 CUBE(config)#call treatment on CUBE(config)#voice service voip CUBE(conf-voi-serv)#sip CUBE(conf-serv-sip)#error-code-override ? cac-bandwidth Status code to be sent for max-bandwidth CAC call Configure call parameters cpu Status code to be sent for all cpu threshold max-conn Status code to be sent for max-conn threshold mem Status code to be sent for all memory threshold options-keepalive Status code to be sent for options keepalive sip-shutdown Status code to be sent for all SIP Shutdown total-calls Status code to be sent for total call threshold
CUBE(conf-serv-sip)#error-code-override total-calls failure 502
dial-peer voice 100 voip description *WAN dial-peer to CUBE* session protocol sipv2 incoming called-number 70247595 voice-class sip error-code-override total-calls failure 502 voice-class sip bind control source-interface GigabitEthernet0/1 voice-class sip bind media source-interface GigabitEthernet0/1 dtmf-relay rtp-nte codec g711ulaw no vad
2. SIP response status line modification with SIP Profiles
By default 502 message says “Bad Gateway”. With SIP Profile 4, we are changing the default response status to say “502 Total Number of Calls Allowed Exceeded”
voice class sip-profiles 4 response 502 sip-header SIP-StatusLine modify "(.*)" "502 Total Number of Calls Allowed Exceeded"
3. Apply SIP profile to the inbound WAN dial-peer
Apply SIP Profile 4 to dial-peer 100 as shown below:
CUBE(config)#dial-peer voice 100 voip CUBE(config-dial-peer)#voice-class sip profiles 4
Dial-peer 100 should look like as below:
dial-peer voice 100 voip description *WAN dial-peer to CUBE* session protocol sipv2 incoming called-number 70247595 voice-class sip profiles 4 voice-class sip error-code-override total-calls failure 502
voice-class sip bind control source-interface GigabitEthernet0/1 voice-class sip bind media source-interface GigabitEthernet0/1 dtmf-relay rtp-nte codec g711ulaw no vad
Place an inbound call and keep running debug ccsip message and debug voip ccapi inout on CUBE to see the new response received in the sip error code...
Jun 21 05:44:59.684: %CALLTREAT-3-HIGH_TOTAL_CALLS: High call volume. Processing for callID(108) is rejected. Jun 21 05:44:59.684: %SIP-3-TOTCALLCAC: Call rejected due to CAC based on Total-calls, sent response 502 Jun 21 05:44:59.688: //108/841FE2118265/SIP/Msg/ccsipDisplayMsg: Sent: 502 Total Number of Calls Allowed Exceeded
Configurable SIP Error codes
... View more