I'm fairly new to CUCM and was looking for some guidance. I recently inherited CUCM 10 and have gotten the basics down, but am still learning the rest.
There is an external 1(877) number (OpenVoice Conference Number), and is the only 877 number we cannot call. When we dial it, there is only silence and then the call automatically ends. I am able to call the number from my cell phone, so I know it's a working number. Here is the list of our call routes for 18XX numbers.
As you can see, there are some routes that are made to refuse the call. I made a route that is specified for the number (See "Conference Call Number" in the picture), and am still not being put through. But when I dial other 877 numbers, I have no issue.
I tried to use DNA, and although I'm not entirely sure that I am putting the information in correctly, these were the results:
I've contacted our phone service provider and opened a ticket with them to make sure that the number isn't dropping on their end.
Any help would be greatly appreciated as I'm a little lost on what I could be doing to fix this.
This guide will explain how to check where a particular directory resides within the filesystem in terms of physical disk, logical volume, volume group, etc by taking a look at where the install repository actually resides on an NCS5500.
According to the RFC 7432:
Extended Community enables split-horizon procedures for multihomed sites. The ESI Label field represents an ES by the advertising PE, and it is used in split-horizon filtering by other PEs that are connected to th...
In scaled EVPN deployments it can be wise to name ESI that way to represent the site/physical port/etc it is attached to. Thus on some remote location you can easily verify where particular route/MAC is coming from. Similar to phone numbers, where...
Want to enable Feature EPFT with “routing-protocols-enable”. However ,it is throwing an error and ask to configure the following command: “non-subscriber-interfaces mac” which once enabled drops the traffic without any penalty.
XR-vm - CLI's
look for any process crash, review time stamp[if it is too old, then no immediate action needed]
verify if standby state is Ready and NSR-Ready
show proc cpu | exclude " 0%"