Search results for query: *

M2008 and M2616 work just fine with CS1000 7.5 and 7.6. I'm assuming the CS1K is staying in place alongside the new Aura CM. M2000 series digital sets do not work on the CM itself.

I was thinking about the short code option, I just can't figure out in my head how to make it do exactly what I want. From the available features that you can assign, I could do a BLF key which would show if someone was actively on a line, but if they pressed the key, it would speed dial that...

Thank you intrigrant, I reviewed the link that you provided previously, and again in case I missed something. Unfortunately, neither the Polycom (KIRK) or the Grandstream DP-715 offers physical buttons for the 4 line appearances that this customer requires like that of the 3910. The Avaya...

Hey guys, i have a sort of special needs customer that is looking for a wireless handset solution for their executives. Here's the issue, they don't like the smaller form factors that have come out recently because some of them are older folks, and the smaller keys are hard on them. They...

300 Seats on CCM6 W/ cs1k. Trying to find a report that indicates if we are ever maxing out all 300 licenses in CCM6. Wanting to add additional agents but need to verify if we are ever getting close to the maximum concurrent calls. Thanks for any assistance

The phones get their DSCP config from the QOS Configuration Section of the Node Configuration in Element Manager. By default, layer 3 QOS is enabled with those values with layer 2 COS as an option.

The phones get their DSCP config from the QOS Configuration Section of the Node Configuration in Element Manager. By default, layer 3 QOS is enabled with those values with layer 2 COS as an option.

If you upgraded to 7.X, then the media cards will need to join the security domain in order to communicate with the sig server properly. Once joined to the security domain, you can push the node info, and they should come right on.

It works well. The migration from NRS to Session Manager is straightforward. My only problem is that you no longer have "dynamic endpoints". The endpoints don't register, so you lose the visual status of the systems talking correctly.

We have tested it, and it works properly. The only reason that it is not supported is the lifecycle of TM. From sources that I have talked to, Avaya did not want to continue testing on a product that was not very profitable is anything.

I have seen that inventory response before: PRI, 36, <Unavailable> PRI, 37, <Unavailable> PRI, 40, <Unavailable> PRI, 41, <Unavailable> And it was when dealing with AA vintage cards.

I am having a problem getting all of my station's to be updated in the CND databse. I have seen several other posts about this, but no one has really answered the question. When I run the CND sync, only the sets/names in Station Admin that have been "Assigned to Employee" in the directory...

I think I remember problems in 4.5 where the bandwidth calcualtions were not resetting properly. I am pretty sure that patch MPLR26226 worked out this issue, but you can also have the PBX reset the calcualtion every night by adding LD 44 to the MIDN. This problem was definately corrected in 5.X.

Yes. It does show "Link Up" and it recognizes the server type as CP PM when looking in Element Manager, and while doing "stat serv".

Anyone come up with anything for this?

Check the Default Gateway configured on the remote PBX to make sure it knows how to respond back: LD 117 =>prt route Should show you the default route.

The PBX time is correct. The CPPM Sig Servers' time is not syncing with the PBX like the ISP1100 Sig Servers do. I am very aware of the PBX time "drift" issues, but this seems to be something diffrent.

Does anyone know if the CP PM Signaling Servers (5.50.12)are supposed to be getting time from the PBXs? All of my ISP1100 servers are staying in sync, but the CPPMs have to be manually updated at least once a week. Is there a fix for this? NTP is not an option for this site. Thanks in advance.

You should not have to do anything on the PBX to clear the leader/ip info on the MC32 card itself. If you have tried the NVRClear / clearLeader commands, and it is still coming up as the leader, it could be that you have issues on the TLAN. It may be that the IP info is being cleared, but...

I have always used NVRClear, followed by clearLeader, then reboot the card.