Search results for query: *

Thanks y'all. The Main Server Memory Setting was set to Medium. I wasn't looking close enough, since I haven't been changing this setting. Set it to Large and it registered immediately.

Thanks Matt, yes the times and timezones are set the same on the main and LSP.

We recently upgraded a site with 4 LSPs to CM 6.3. The 4 LSPs were upgraded first and registered to the main CM 5.2 with no trouble. After the main was upgraded to 6.3, one of the LSPs would not register. They all have the same patches and the Server Roles entries have been verified. The...

I finally found the right page on the Cisco site. It looks like a VIC2-2FXO gives me two FXO ports and should do the job.

We are on CM 8.5 and normally install remote UCM sites with a 2911 router and a PRI. I have a request for a small site and would like to assign DIDs from another nearby location. If I want to add a single POTS line for 911 access, which module(s) do I need? I would think my equipment list...

We have about 20 sites with Communication Manager server pairs running 5.2.1. Does anyone have any ideas for centralized password management? Is there anything like Cisco's TACACS? Passwords are required to be changed every 45 days and it is inefficient for each administrator to access every...

Wow.

The "IP Telephony Implementation Guide" has not been updated since CM 3.1. For later versions of CM, see "Administering Network Connectivity on Avaya Communication Manager". In several places it states "load-balancing or duplicated TN2602AP circuit packs". So...duplication/load balancing...

From the IP Telephony Implementation Guide page Compas ID 95180: "A single port network can have up to two TN2602AP circuit packs only. As result, the port network can have either two duplicated TN2602AP circuit packs or two load balancing TN2602AP circuit packs, but not both a duplicated pair...

See chapter 4 of "Administration for the Avaya G250 and Avaya G350 Media Gateways" http://support.avaya.com/japple/css/japple?temp.documentID=343144&temp.productID=156182&temp.releaseID=348125&temp.bucketID=159898&PAGE=Document

The primary complaints about early MM were implementation related. The first 2 releases were difficult to install, but once implemented the platform was stable. Another issue was that not many technicians were trained or experienced on it. Release 3 cleaned up many of the implementation...

PSN001052u covers this issue. It was fixed in 3.13. I agree with bsh upgrade to 3.15 or risk having to deal with it again.

Yes, you can do this. Just make sure that Spanning Tree is enabled in the P330.

You need to go to the IP office forum.

LSP mode will continue call processing past 30 days. It's just that after 30 days you won't be able to administer any changes. A gateway in SLS mode will continue to handle calls beyond 30 days. Licenses aren't loaded on gateways, only servers.

If Origination Restriction is set to yes, the user is unable to make (originate) calls from the bridged appearance.

This is old information for long time Linux users, but relevant to those running Communication Manager versions 1.x and 2.x. These CM releases use Linux kernel version 2.4.20. The 2.4.x kernel suffers from an uptime rollover bug. At 497 days of uptime, the uptime counter rolls back to zero...

Your server status shows shadowing is off. Run swversion from the cli on each server...does it look exactly the same on each one, including the order of any patches? If not, the shadowing won't come up and your cluster ID won't appear correctly.

Yes, Avaya calls this feature "high reliability". You may need additional licenses to activate this feature. Your SE should be able to help you with that.

I believe you need v12 or later.