I'm not sure about the webex calling implementation.
In UCM it was intentional to write CMC to CDR and to not write FAC to CDR. That
would be kind of like writing passwords on stickies and posting them in the
hallway.
I think maybe you're referring to "forward maximum hop count". That parameter
is used to guard against call routing loops caused by numbers being forwarded.
There is also a "max hop" parameter for multicast music on hold. That might be
more related to high cpu on boundary devices or failing to
CSCvt97709 was for systems that installed using an older 80GB OVA and then
upgraded.
Partition sizes documented in CSCvt97709:
TotalFreeUsed
Disk/active 14154228K 319736K 13689364K (98%)
Disk/inactive 14154228K
Hello Reto,
This looks like every RTP packet is duplicated.
This could be an artifact of how the packet capture was taken. Was a SPAN or
similar feature used that might duplicate packets? Are the packets truly
duplicates? Sometimes this IP ID field is useful
Otherwise, this could be a
Andy, sounds like a good start:
https://community.cisco.com/t5/ip-telephony-and-phones/disaster-recovery-problem/td-p/2767755
I see 2 other situations that might be relevant:
1. All the same .cop files not installed
2. Attempting to restore a backup of a different version
-Wes
On Feb 19, 2021,
What is the exact error? What do DRS logs show?
I see one report that after re-install dbreplication is not established leading
to "Unable to send network request to master agent. This may be due to Master
or Local Agent being down”
Resolved by resetting dbrepliaction for all nodes.
Thanks,
Not easily. You’d need to join ~4-5 tables to get that information. Any
especial characters would botch record delineation in CLI output.
https://developer.cisco.com/docs/axl/#!12-5-cucm-data-dictionary
-Wes
On Feb 18, 2021, at 2:11 PM, Louis Koekemoer (MEA)
On UCM cli ‘utils diagnose test’ to ensure things look mostly okay from OS and
low level perspective.
After that in UCMadmin ensure system->server shows the correct IP/name for each
server.
After that ensure ccm process restarted (or whole server rebooted). Based on
your description SDL links
As a person who still processes 400+emails per day for more than a few years
now (gulp) I hear you about the abundance of information and communication
channels. I am still working on integrating WxT in my information processing
model. I am still decommissioning my
Upcoming Talk:
https://community.cisco.com/t5/online-tools-and-resources/collaboration-solutions-analyzer-support-talks-event/ba-p/4178251
CSA can help to identify and diagnose issues in Collaboration deployments
including device registration and call failures.
CSA Tool:
Possibly:
https://www.cisco.com/c/en/us/support/docs/conferencing/telepresence-server/118345-probsol-telepresence-00.html
-Wes
On Apr 2, 2020, at 12:11 PM, James Dust
mailto:james.d...@charles-stanley.co.uk>>
wrote:
That’s fixed it thank you Kent,
From: Kent Roberts
Keep on connecting those users:
https://www.cisco.com/c/m/en_us/products/unified-communications/unified-communications-manager-callmanager/obtaining-temporary-licenses.html
-Wes
___
cisco-voip mailing list
cisco-voip@puck.nether.net
When last I looked PUT fulfillment was by electronic posting and download in
countries where that is legal. Some geo’s require physical media and the
creates a shipping limitation.
What inefficiency do you experience with PUT?
Thanks,
Wes
On Feb 6, 2020, at 12:17 PM, Ryan Huff
this.
When last I looked:
PUT does create a sales order which helps address any licensing questions,
re-issues, etc.
‘Upgrade’ media isn’t always the same as install media. PUT gets bootable
install media in case of reinstall or disaster.
And PUT doesn’t get the latest SU. PUT gets latest
Yes, this is still open. Inquiry initiated. Thank you for the reminder. Bonus
points if you can open a case that we can link to the bug.
-Wes
On Oct 3, 2019, at 12:50 PM, Anthony Holloway
mailto:avholloway+cisco-v...@gmail.com>> wrote:
Source:
Adam,
Yes, the reservation appears steep and outside monitors appear ripe for
harvesting underutilized resources.
And 3 things come to mind:
* ccm.bin at its core is a distributed real time state machine. Delays have
serious impacts. Feature are invoked across nodes. See the long history
Correction: it will not be visible.
On Mar 21, 2019, at 2:58 PM, Wes Sisk (wsisk) via cisco-voip
mailto:cisco-voip@puck.nether.net>> wrote:
Whoops, I thought it was. Thanks for the callout Lelio! It should be visible in
24 hours.
https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvh30732
Please note at this point the 8851 product manager has elected not to address
that request. If this feature is important to you then please press your
account representative more.
Regards,
Wes
On Mar 20, 2019, at 5:56 AM, James Dust
mailto:james.d...@charles-stanley.co.uk>>
wrote:
Hi Reto,
Nick,
The features you describe are propagated by both SDL signaling and with a
dependence on database replication.
At casual observation it sounds like database traffic between nodes may not
prioritized and may be delayed or dropped.
The 80 msec is especially important for near real-time
Nick,
The command is invoking database commands that Cisco does not own. They are not
being obtuse; they genuinely do not know.
It will cause a spike in database communication between nodes.
My first guess is very much in line with yours that the burst in traffic
exceeds certain QoS queues.
Working on it.
Until it is resolved, and not the greatest workaround as it contains other
things, try looking under “Cisco Meeting Server”.
For example:
CSCve59084CWMS OVA can not be deployed on vCenter 6.5
-Wes
On Jul 30, 2018, at 2:36 PM, Anthony Holloway
21 matches
Mail list logo
