Search results for query: *

problem solved.... somehow our digit absorption was changed from absorbing 6 to 0. Does anyone know how this could have happened?

Our setup: 3 sites: NY, DE, FL NY Site has moved. PRI's cutover 3300 mxe shutdown, moved, etc everything was cutover and turned up. internal dialing among all the offices operational. Our problem: inbound calls on the PRI fail. we can see the calls hitting the pbx thru ccs trace: 11:39:17...

we changed from dtmf to mai tai....

excellent. the default is 24. I appreciate the assistance on this one! Will let you know next weekend if this did the trick

This has been a problem for a month or so now and I can't seem to pinpoint exactly the cause. Here is the situation.... if you receive a voicemail on Friday, your phone set will blink indicating a new voicemail waiting.... when you arrive Monday morning, the MWI no longer is blinking despite...

I contacted our partner who could not get me answer other then not until October this year at the earliest. With that being said, does any one know if Unified Communicator Advanced 3.1 supports office 2010? I tried installing UC 3.0.21 with office 2010 and received a message stating Outlook was...

that did it... thank you.

I am somewhat perplexed and need a brainstorming partner. Here is a description of the setup: Our main line is a speed call #. The speed call number points to a device on the system (ext. 4000). Ext. 4000 is set to ALWAYS reroute to a HG (hg#4900); HG4900 members include 5 lines for incoming...

Here is the resolution: Following the lead on this discussion: http://www.tek-tips.com/viewthread.cfm?qid=1503503&page=68 I decided to change the following setting in COS of the IP Trunk: suppress simulated ccm after isdn progress This setting was changed from YES to NO. Conferencing and...

could this be the same issue?? http://www.tek-tips.com/viewthread.cfm?qid=1503503&page=68

ok. thank you for the time. I will certainly post the resolution if we get one

Ok. I am holding off on doing the ARS only because I get lost once I reach the digit absorption part.

maybe we are on to something here... When adding an entry to Sys-A or Sys-B, is the termination type ROUTE, LIST, or PLAN? What determines the appropriate setting? My assumption is: ROUTE = will follow route assignment form LIST = will follow route list assignment (optional) form PLAN = will...

I am somewhat new to Mitel, so some of the knowledge i have is what I have read through help files and various other documentation. My understanding of the COS option was to display that information between VM systems (we do have resiliency and a backup VM system in Sys-B) Record a call is set...

Why wouldn't we set COV VM port to YES for the IP Trunk? Don't we want the VM system to uniquely identify the party receiving a message? This I agree with and is easy enough to change.

no worries... I had to leave for the day myself and just performing some catch-up here. We can definitely touch base tomorrow. I appreciate your help on this; I am stumped. This is set to NO on the PRI COS This is set to YES on the IP COS This is set to NO on the PRI COS I assume this should...

I will repost as CSV... thats not a problem at all! see links: http://www.mediafire.com/file/grzdwiijzo2/cos13-ip.csv http://www.mediafire.com/file/myxfukhzvnu/cos-12-pri.csv http://www.mediafire.com/file/mmz1ndymxzd/cos-20-stna.csv

Sys-A Stn assigned COS/COR of IP Trunk. Local conference successful under cos -- public trunk = NO COS of PUBLIC TRUNK, LOCAL PRI, AND Sys-A Stn follows: <let me know when downloaded so I may remove these files from the hosting site - thank you>...

YES YES It appears that whenever I utilize the IP trunk w/ the remote systems PRI, conferencing fails. Another test I just performed was a Sys-B Stn hotdesked into Sys-A. Stn-B could not conference when dialing out the Sys-B PRI from login location Sys-A. Stn-B also could not conference...

I appreciate your timely responses.... .........Success......... Here are additional steps and the results Local set - Local PRI - Local PRI - Success Local set - Local PRI - Remote PRI - Failure Local set - Remote set - Local PRI - Success - conferencing is functional on the 5330's until i...