An Error Occurred While Transferring A Call To
Contents |
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) Home20132010Other VersionsLibraryForumsGallery Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: Call cannot be transfered from Exchange 2010 Auto Attendant to Lync 2010 Enterprise Voice users with Local Numbers Lync Server , Lync > Lync 2010 and OCS an error occurred while preparing your information for transfer - Enterprise Voice and Telephony Question 0 Sign in to vote I hope anyone can an error occurred while preparing your information for transfer windows migration assistant help me. I ha a consolidated Exchange 2010 server (with MBX, CAS, HUB, UM on it) and a Lync 2010 infrastructure. My
A Framing Error Occurred During Transfer
Lync 2010 infrastructure has a FE/Mediation and Edge Server architecture. All my Lync users (ex. User1 has a local of 1000 and User2 has a local of 2000) are configured with local numbers. I have a DID assigned
Transfer Error Occurred Pje
to my Exchange 2010 Auto Attendant. I have configured my Lync 2010 Dial Plan first, then configured Exchange UM Dial Plan next. I plan to use the Exchange Auto Attendant to be my Auto Attendant for calls coming from both external (PSTN) and internal (Lync users). My Exchange 2010 Dial Plan is set to 4 digits, SIP URI, and Secured options. I'm not sure if this has to Telephone Extension or E.164 format. I also an error occurred while trying to call created allow normalization rule in the all in the Dialing Rules of UM. If I dial in 1000 (XXXX), UM dial plan would translate it to +1000 (+XXXX). Here is the problem. When a user, whether both from internal or external, dials in to the Exchange Auto Attendant, and tries to transfer a call to a specific Lync user by saying the name (if speech enabled) or if typing the extension number (if not speech enabled), the calls do not connect to the Lync client. The Auto Attendant would say "The call cannot be transfered...." When I checked my event viewer, I keep on seeing the error below. Event 1136 from UMCore An error occurred while transferring a call to "1000". Additional information: The call transfer type is "Blind.", the transfer target is "phone number" I would appreciate any help or information to resolve this. Thanks! :) vinceq Sunday, January 23, 2011 3:17 PM Reply | Quote Answers 1 Sign in to vote Hi Drago, Thanks for the inputs... I started trying to solve Event ID 1400 by first checking the Exchange server. I replaced the certificate for the UM server role since the original certificate was using owa.domain.com instead of the FQDN of the exchange server. For Event 1400, here is what i did... Symptom UM Cannot make a TLS connect
to local numbers assigned in Lync 2010 users this past weekend, and at last today, I was able to make it work with the help of some researching, stock knowledge and some help from local
An Error Occurred While Trying To Call The Requested Method Lookup Software
MS guys.Here is the situation in one of my deployments. The client is looking an error occurred while calling the callback for an IVR feature or Auto Attendant basically. So we are trying to configure Exchange 2010 AA to route calls an error occurred while calling the callback onload visio to Lync users. The reason is simply because the client prefers to use local numbers instead of DIDs for most of their users.We have a consolidated Exchange 2010 server (with MBX, CAS, HUB, UM https://social.technet.microsoft.com/Forums/office/en-US/69341a2b-ce62-442a-a375-22c0da003ad0/call-cannot-be-transfered-from-exchange-2010-auto-attendant-to-lync-2010-enterprise-voice-users-with?forum=ocsvoice on it) and a Lync 2010 infrastructure. My Lync 2010 infrastructure has a FE/Mediation and Edge Server architecture. All my Lync users (ex. User1 has a local of +1000 and User2 has a local of +2000) are configured with local numbers. I have a DID assigned to my Exchange 2010 Auto Attendant. My Lync and Exchange dial plans have exactly the same name. We are configuring the Exchange Auto http://understoodtechnology.blogspot.com/2011/01/exchange-2010-auto-attendant-not.html Attendant (as Attendant/IVR) for calls coming from external (PSTN).My Exchange 2010 Dial Plan is set with 4 digits, SIP URI, and Secured options. ExchUCUtil.ps1 was ok. OCSUMUtil.exe was ok. I also created normalization rule in the Dialing Rules Group and set it in the Dialing Restrictions of UM (Though I'm not sure if this is necessary as I just saw it recommended in one of the forums). The idea was, in the Auto Attendant, if I dial in 1000 (XXXX), UM dialing rule would translate it to +1000 (+XXXX).Here is the problem. When a user, whether both from internal or external, dials in to the Exchange Auto Attendant, and tries to transfer a call to a specific Lync user by saying the name (if speech enabled) or if typing the extension number (if not speech enabled), the calls do not connect to the Lync client. THE CALL IS NOT TRANSFERED!When the Auto Attendant asks me to enter the extension of User1, using the keypad in Lync client, I type in 1000. The Auto Attendant dials in, and after a few seconds, it says call "THE CALL CANNOT BE TRANSFERRED. RETURNING TO THE MAIN MENU."What?? Wait, you have to transfer my call! As i
- CertificateIssue Posted on December 1, 2011 by Peter Symptom I recently came across an interesting issue when trying to integrate Lync Server 2010 with Exchange Server 2010 SP1 Unified Messaging. The https://rockyprogress.wordpress.com/2011/12/01/lync-server-2010-exchange-server-2010-um-integration-certificate-issue/ symptom was that, whenever we tried to transfer a call from the Auto https://forums.slipstick.com/threads/73457-exchange-um-key-mapping-to-extension/ Attendant to a Lync Server telephone extension, we would get two warning messages logged in the Application log on the Exchange UM server, that were similar to the following: Event 1079, MSExchange Unified Messaging The VoIP platform encountered an exception Microsoft.Rtc.Signaling.OperationFailureException: An exception was detected that the platform was not expecting. This may error occurred be because of abnormal shutdown, lack of resources, or failure of application code. --> System.Security.Cryptography.CryptographicException: Invalid provider type specified. Event 1136, MSExchange Unified Messaging An error occurred while transferring a call to "test1@bongo.com". Additional information: The call transfer type is "Blind.", the transfer target is "phone number", and the caller ID is: "6c53752d10394feeab50e8656010afdd". The first warning message was the key to our issue. Some an error occurred background information When we created certificates for the Exchange UM and Lync servers, we did so using a modified Version 3 Web Server template from an Enterprise CA running Windows Server 2008 R2, Enterprise Edition. Traditionally, Windows applications have used a cryptographic API called CryptoAPI. CryptoAPI makes use of providers called cryptographic service providers (CSPs). CSP's typically implement cryptographic algorithms and provide key storage. Windows Server 2008 introduced a new cryptographic API called Cryptography Next Generation (CNG). CNG is the long term replacement for the CryptoAPI. Unlike CryptoAPI, CNG separates cryptographic providers (algorithm implementation) from key storage providers (key storage). Key storage providers (KSPs) can be used to create, delete, export, import, open and store keys. When you create a certificate for Exchange Server 2010 Unified Messaging with SP1, using a modified Version 3 Web Server template, it is quite possible that a KSP is used instead of a CSP. This is what happened in our case. For the Unified Messaging server, this is not an issue because CNG support was introduced with Exchange Server 2010 SP1. Unfortunately, several applications, including Lync Server 2010, have issues with certificates created using a KSP. Verifying the Issue We ran the following command from an administrative co
Key Mapping to Extension Discussion in 'Exchange Server Questions' started by Kris Garbet, Sep 8, 2010. Previous Thread Next Thread Loading... 0/5, 0 votes Kris Garbet Guest We are running an Exchange 2010 SP1 Unified Messaging Server connected to an OCS system Everything seems to be running just fine (has since Exchange 2007 and we upgraded to 2010 then to 2010 sp1 we think) after the 2010 sp1 upgrade we lost the Key mapping to extension. Key mapping to another AA works fine, but as soon as we put an extension or DID it"s a no go. For example we have an AA that has the options “press 2 for sales 3 for tech support” etc. 2 goes to extension 302. Option 3 goes to 303. When a caller hits any option that is key mapped to an extension or DID they get "The call cannot be transferred, returning to the main menu" and event ID 1136 is logged on the UM server Application Log: An error occurred while transferring a call to "302". Additional information: The call transfer type is "Blind.", the transfer target is "phone number", and the caller ID is: "798d347b-f3cf-487e-aacb-a01718ddb615". (note the above error message has not been altered it actually says “phone number&rdquo don"t know if that helps Doing some digging i found this article and seems to be exactly the same issue, but his solution didn't work for me http://ucmadeeasy.wordpress.com/2010/08/29/exchange-um-auto-attendant-key-mappings-not-transferring-calls-after-sp1/ Any thoughts out there? Thanks, Kris Sep 8, 2010 Flag Post #1 Share Kris Garbet Guest Anyone? Sep 10, 2010 Flag Post #2 Share Savi Thomas Guest I too have the same issue Oct 11, 2010 Flag Post #3 Share Previous Thread Next Thread Loading... (You must log in or sign up to reply here.) Show Ignored Content Loading... Similar Threads Outlook 2010 Receiving work/Exchange email to my personal email Lori Grady, Aug 29, 2016, in forum: Using Outlook Replies: 2 Views: 99 Lori Grady Aug 30, 2016 Outlook 2016 Outlook 2016 - How to change password in MS Exch