About this Document
This document provides installation instructions for Unified CCE 12.6(1) ES39. It also contains a list of Unified CCE issues resolved by this engineering special.
Review all installation information before installing the product. Failure to install this engineering special as described
can result in inconsistent Unified CCE behavior.
This document contains these sections:
In the Product Alert Tool,
you can set up profiles
to receive email notification of new Field Notices,
Product Alerts, or End of Sale information for your selected products.
The Product Alert Tool is available at
https://www.cisco.com/cisco/support/notifications.html.
Unified CCE Version Support
Unified CCE Component Support
This section lists the Unified CCE components on which you can and cannot install this engineering special.
Supported Unified CCE Components
You can install Unified CCE 12.6(1) ES39 on these Unified CCE components:
Unsupported Unified CCE Components
Do not install this engineering special on any components other than the following:
Installation of this patch requires that all Unified CCE services be shut down during the entire period of installation.
- It is always recommended to install this ES during a scheduled downtime.
- Using the Unified CCE Service Control, stop all the Unified CCE Services running on the system.
- Launch the installer provided and follow the instructions on the screen.
If the Unified CCE Services are set to manual, using the Unified CCE Service Control, start all the Unified CCE Services.
- To uninstall this patch, go to Control Panel.
- Select "Add or Remove Programs".
- Find the installed patch in the list and select "Remove".
Note: Remove patches in the reverse order of their installation. For example, if you installed patches 3, then 5, then 10 for a product, you
must uninstall patches 10, 5, and 3, in that order, to remove the patches from that product.
Resolved Caveats in this Engineering Special
This section provides a list of significant Unified CCE defects resolved by this engineering special. It contains these subsections:
- Resolved Caveats in Unified CCE 12.6(1) ES39
Note: You can view more information on and track individual Unified CCE defects using the Cisco Bug
Search tool, located at: https://bst.cloudapps.cisco.com/bugsearch/search?null.
Resolved Caveats in Unified CCE 12.6(1) ES39
This section lists caveats specifically resolved by Unified CCE 12.6(1) ES39.
Index of Resolved Caveats
Caveats in this section are ordered by Unified CCE component, severity, and then by identifier.
Identifier |
Severity |
Component |
Headline |
CSCwc61797 |
2 |
outbound |
Dialer crashes when receiving 183 malformed SIP packet from remote end |
Detailed list of Resolved Caveats in This Engineering Special
Caveats are ordered by severity then by defect number.
Defect Number: CSCwc61797
Component: outbound
Severity: 2
Headline: Dialer crashes when receiving 183 malformed SIP packet from remote end
Symptom:
Dialer process is crashing with a mini dump created for the 183 malformed sip packet. Below are the log analysis and the error symptoms.
Dialer Logs:
16:09:51:702 dialer-baDialer Trace: (RESIP) DialogId::DialogId: f735536d-79292c5c-00117d25-7163b45c-127bce50-27628A07-1FB4
16:09:51:702 dialer-baDialer Trace: (RESIP) ************** Created Dialog as UAC **************
16:09:51:702 dialer-baDialer Trace: (RESIP) mRemoteNameAddr: ;tag=27628A07-1FB4
16:09:51:702 dialer-baDialer Trace: (RESIP) mLocalNameAddr: ;tag=127bce50
16:09:51:702 dialer-baDialer Trace: (RESIP) mLocalContact:
16:09:51:702 dialer-baDialer Trace: (RESIP) mRemoteTarget:
16:09:51:702 dialer-baDialer Trace: (RESIP) Dialog::Dialog f735536d-79292c5c-00117d25-7163b45c-127bce50-27628A07-1FB4
16:09:51:702 dialer-baDialer Trace: (RESIP) ### Calling CreateAppDialog ###:
SIP/2.0 183 Session Progress
Via: SIP/2.0/UDP 10.112.5.9:58800;branch=z9hG4bK-d8754z-362194175430bd62-1---d8754z-;rport=58800
Require: 100rel
Contact:
To: ;tag=27628A07-1FB4
From: ;tag=127bce50
Call-ID: f735536d-79292c5c-00117d25-7163b45c
CSeq: 1 INVITE
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Content-Type: multipart/mixed;boundary=uniqueBoundary
Date: Fri, 15 Jul 2022 10:51:10 GMT
MIME-Version: 1.0
Server: Cisco-SIPGateway/IOS-16.9.5
Supported: sdp-anat
Allow-Events: telephone-event
RSeq: 9589
Content-Length: 489
Remote-Party-ID: ;party=called;screen=no;privacy=off
Session-ID: 6d3dbb7c33c05b30a9c47da59d2c24f9;remote=ecc8cbc1d4a150f198830cef93f90803
--uniqueBoundary
Content-Type: application/sdp
Content-Disposition: session;handling=required
v=0
o=CiscoSystemsSIP-GW-UserAgentSIP/2.0 183 Session Progress
Via: SIP/2.0/TCP 10.112.5.24:5060;branch=z9hG4bKwtCEyDP9dvrj0FhObNl+oA~~2016367,SIP/2.0/UDP 10.112.5.9:58800;branch=z9hG4bK-d
16:09:51:702 dialer-baDialer Trace: (RESIP) Dialog::dispatch: SipResp: 183 cid=f735536d-79292c5c-00117d25-7163b45c tid=362194175430bd62 cseq=INVITE contact=54109545672757@10.113.60.50:5060 / 1 from(wire)
16:09:51:702 dialer-baDialer Trace: (RESIP) Dialog::dispatch -- Created new client invite sessionSipResp: 183 cid=f735536d-79292c5c-00117d25-7163b45c tid=362194175430bd62 cseq=INVITE contact=54109545672757@10.113.60.50:5060 / 1 from(wire)
16:09:51:702 dialer-baDialer Trace: (RESIP) ^^^ InviteSession::InviteSession 072C3030
16:09:51:717 dialer-baDialer Trace: (RESIP) SipMessage::getContents: multipart/mixed
16:09:51:717 dialer-baDialer Trace: (RESIP) BaseException at ParseBuffer.cxx:949 ParseBuffer.cxx:949, Parse failed unexpected eof in context: Contents
--uniqueBoundary
Content-Type: application/sdp
Content-Disposition: session;handling=required
v=0
o=CiscoSystemsSIP-GW-UserAgentSIP/2.0 183 Session Progress
Via: SIP/2.0/TCP 10.112.5.24:5060;branch=z9hG4bKwtCEyDP9dvrj0FhObNl+oA~~2016367,SIP/2.0/UDP 10.112.5.9:58800;branch=z9hG4bK-d8754z-505084596b2bf201-1---d8754z-;rport=58800
From: ;tag=3a7f3c32
To: ;tag=27629E77-733
Date: Fri, 15 Jul 2022 10:51:15 GMT
Call-ID: 335d
^
16:09:51:717 dialer-baDialer Trace: (RESIP) ParseException
ParseBuffer.cxx:949, Parse failed unexpected eof in context: Contents
--uniqueBoundary
Content-Type: application/sdp
Content-Disposition: session;handling=required
v=0
o=CiscoSystemsSIP-GW-UserAgentSIP/2.0 183 Session Progress
Via: SIP/2.0/TCP 10.112.5.24:5060;branch=z9hG4bKwtCEyDP9dvrj0FhObNl+oA~~2016367,SIP/2.0/UDP 10.112.5.9:58800;branch=z9hG4bK-d8754z-505084596b2bf201-1---d8754z-;rport=58800
From: ;tag=3a7f3c32
To: ;tag=27629E77-733
Date: Fri, 15 Jul 2022 10:51:15 GMT
Call-ID: 335d
^
16:09:51:717 dialer-baDialer Trace: (RESIP) Transition UAC_Start -> UAC_Early
16:09:51:717 dialer-baDialer Trace: (SipISH) onNewSession: SipResp: 183 cid=f735536d-79292c5c-00117d25-7163b45c tid=362194175430bd62 cseq=INVITE contact=54109545672757@10.113.60.50:5060 / 1 from(wire)
16:09:51:717 dialer-baDialer Trace: (SipISH) SIP port: [657], station: [2158], state: [SIP_LINESTATE_DIALING_NUMBER].
16:09:51:717 dialer-baDialer Trace: (RESIP) UAC_Early: startStaleCallTimer
16:09:51:717 dialer-baDialer Trace: (RESIP) Adding application timer: DumTimeout::StaleCall INVITE: 31000 UAC_Early ADDR=;tag=127bce50 PEER=;tag=27628A07-1FB4: duration=233 seq=2
Conditions:
PCCE with outbound functionality GW/CUBE-- Firewall--CUSP-- Dialers
Workaround:
None
Further Problem Description:
Dialer Crash EMS Logs
Dialer exe file
Dialer pdb file
Dialer crash mdmp file
CUSP Logs
Time of Dialer Crash : 16:09:51:717
CUSP_Dialer_Logs_15July.zip file attached to this defect
https://cxfiles-v1-ui.cxapps.cisco.com/files/download?appId=CSOne&forceText=-1&id=693853518&fileName=CUSP_Dialer_Logs_15July.zip
Caveats resolved in earlier ESs and included as part of Unified CCE 12.6(1) ES39
ES#
|
Identifier
|
Severity
|
Component
|
Headline
|
Comments
|
ES15
|
CSCvx81625
|
2
|
outbound
|
Outbound dialer dials more calls than port per agent (PPA) configuration
|
|
You can access current Cisco documentation on the Support pages at the following sites:
- https://www.cisco.com
- https://www-china.cisco.com
- https://www-europe.cisco.com
Documentation Feedback
To provide comments about this document, send an email message to the
following address:
contactcenterproducts_docfeedback@cisco.com
We appreciate your comments.
Cisco.com is a starting point for all technical assistance. Customers and partners can obtain documentation, troubleshooting tips, and sample configurations from online tools. For Cisco.com registered users, additional troubleshooting tools are available from the TAC site.
Cisco.com
Cisco.com provides a broad range of features and services to help customers and partners streamline business processes and improve productivity. Through Cisco.com, you can find information about Cisco and our networking solutions, services, and programs.
You can also resolve technical issues with online technical support and download software packages. Valuable online skill assessment, training, and certification programs are also available.
Customers and partners can self-register on Cisco.com to obtain additional personalized information and services. Registered users can order products, check on the status of an order, access technical support, and view benefits specific to their relationships with Cisco.
Technical Assistance Center
The Cisco TAC site is available to all customers who need technical assistance with a Cisco product or technology that is under warranty or covered by a maintenance contract.
Contacting TAC by Using the Cisco TAC Site
If you have a priority level 3 (P3) or priority level 4 (P4) problem, contact
TAC by going to
https://www.cisco.com/c/en/us/support/index.html.
P3 and P4 level problems are defined as follows:
- P3--Your network performance is degraded. Network functionality is noticeably impaired, but most business operations continue.
- P4--You need information or assistance on Cisco product capabilities, product installation, or basic product configuration.
In each of the above cases, use the Cisco TAC site to quickly find answers to your questions.
If you cannot resolve your technical issue by using the TAC online resources,
Cisco.com registered users can open a case online by using the TAC Case Open
tool at the following site:
https://mycase.cloudapps.cisco.com/create/start/
Contacting TAC by Telephone
If you have a priority level 1(P1) or priority level 2 (P2) problem, contact TAC by telephone and immediately open a case. To obtain a directory of toll-free numbers for your country, go to the following sites:
P1 and P2 level problems are defined as follows:
- P1--Your production network is down, causing a critical impact to business operations if service is not restored quickly. No workaround is available./li>
- P2--Your production network is severely degraded, affecting significant aspects of your business operations. No workaround is available.