I have a few sites with a small staff of around 10 people. We use centralized call processing and SRST as a backup. Recently, our backup kicked in at two sites due to a network outage. Everything seemed to work fine, except for one thing. The main number that comes into the office is set up as a 'shared line' on everyone's phone. This line produced a busy signal to anyone calling in. Being that this was the main number, it wasn't good. Has anyone seen this, or maybe Dave has heard of this from others?
What kind of a gateway and what kind of interface are you using for the outside callers to dial in? Is this the same interface/GW you use when things aren't in SRS mode?
A guess would be that you have plar configured on an FXO port to a certain number that exists during regular operation (i.e. it's this is being sent to the callmanager) but not in SRS mode. It would be good to see a 'show ephone' in SRS mode to look at all the numbers that the router knows about and then to see what number is being received (either look at the 'connection plar' statement, or 'debug isdn q931' or something) when the call comes in.
I'm assuming that the way you fixed this was by getting the WAN back up (i.e. rebooting the phone or router or something didn't fix it).
No PLAR configured. The gateway is simply an ISDN PRI in a 4224. Rebooting it did in fact fix this problem on one occasion.
The following error appears 30 to 40 times in a row as soon as the phones try to home to the 4224. It does this on all of my 4224's.
3d20h: %DIALPEER_DB-3-ADDPEER_MEM_THRESHOLD: Addition of dial-peers limited by available memory
There is a total of 20 phones in this office and 46 DN lines total.
Let me throw this at you. The following represents two phone calls. The first call was a simple long distance call placed directly to the main number of the office. The second call was a call to an 800 number that is pointing to the same exact number as the first. The only difference is that while dialing the 800 number, I received no ringback, even though it was in fact ringing on the other end. This only occurs while in SRST mode.
The issue with the DIALPEER_DB-3 ADDPEER_MEM_THRESHOLD message has to do with memory. The router won't allow you to add more dial-peers (and therefore consume more memory) if more than 75% of available processor memory is used up (you can get the amount of processor memory via the 'show mem sum' command). These dial-peers are built only during failover; they are dynamically created as DN's register to the SRS router.
As for the 2nd problem (ringback), check out the progress indicators for the respective calls and take a look at:
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...
This document describe how DST changes and how time changes are
implemented in DST. Daylight Saving Time (DST) is the practice of
setting the clocks forward 1 hour from standard time during the summer
months, and back again in the fall, in order to make b...