locked
can not make call to voice mail through lync client while connected through edge RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    I have setup an Edge server and published it. External users are able to login from outside the network i.e. internet external users can make PSTN calls and able to receive pstn call but when i click on call voice mail it never connects it stucks on connecting call then disconnects after few seconds and it gives me following error

    the call could not connect due to network issues  try logging out of lync logging back in, or try again later.

    is there some one who can tell me that do i need to open any ports through edge to um or um to edge do i have to do some extra things i am not able to see any thing on the internet. My exchange is 2007 SP1 please help me out in this regard.

    if i call from pstn to voice mail it connects but there is a 10 second delay and if i use the call voice mail option from lync client while connected internally it works great please help me out.

    Regards,

    SKHATRI
    Tuesday, August 9, 2011 4:37 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    Well now your answers are quite descriptive. Remote the external IP from UM. as Edge internal interface should connected to UM directly. As you mentiond that there is no firewall between um and edge internal interface then every thing should work perfectly fine.

    If all is working fine internally then i have a suggestion to upgrade your exchange to 2010. In my environment it didnt work and i have to upgrade out environment to exchange 2010 SP1.

    Please mark it as answer if this answers your question | MCITP Microsoft Lync | My Blog: http://salahuddinkhatri.wordpress.com

    SKHATRI

    • Proposed as answer by ITEC Support Thursday, February 23, 2012 12:50 PM
    • Marked as answer by SKHATRI Thursday, February 23, 2012 1:29 PM
    Thursday, February 23, 2012 11:37 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Does this work for internal users? 

    Do you see an error on your Exchange UM server when the call fails?

    Can you log S4 and SIPStack (all flags) on the Lync FE server and post the results here?

    Mark King | MVP: Lync Server | MCTS:UC Voice | MCITP x3 :Lync, Enterprise Messaging 2010, EA | MCSE: Messaging | blog.unplugthepbx.com | Twitter: @unplugthepbx
    Tuesday, August 9, 2011 5:26 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    Yes it does work perfectly for internal users, how ever when i connect to UM through PSTN there is some kind of delay, we have integrated the lync with avaya so the call first come to avaya then avaya sends it to Lync and then lync sends it to UM the delay is between 5 to 10 sec

    when ever i establish a call to UM through Lync client by using call voice mail option it doesnt matter the user is internal or external i receive the following warning on UM Servers

    he Telephony Manager declined a call with Call Id 'eaedb23341b3439d9f1368504264547a' for the following reason in component telephony session: 'The media description received from the remote SIP peer has an invalid content type 'multipart/alternative'.'.

    Further trace information for support personnel follows:

    Microsoft.SpeechServer.Core.InvalidMediaException: The media description received from the remote SIP peer has an invalid content type 'multipart/alternative'.
       at Microsoft.SpeechServer.Core.MediaNegotiation..ctor(LoggingContext loggingContext, ContentDescription rtcRemoteMediaOffer)
       at Microsoft.SpeechServer.Core.TelephonySessionInbound.CreateMediaNegotiation(ContentDescription rtcMediaDescription, SessionInfo sessionInfo, CallInfo callInfo, IPEndPoint sipPeerEndpoint)
       at Microsoft.SpeechServer.Core.TelephonySessionInbound.Initialize(SessionInfo sessionInfo, SessionReceivedEventArgs e, CallInfo callInfo, EventSerializer serializer, SpeechSession speechSession, Boolean isTlsConnection)
       at Microsoft.SpeechServer.Core.TelephonySessionInbound..ctor(SessionInfo sessionInfo, SessionReceivedEventArgs e, CallInfo callInfo)
       at Microsoft.SpeechServer.Core.TelephonyManager.CreateSession(Int32 inviteReceivedTickCount, SessionReceivedEventArgs e)
       at Microsoft.SpeechServer.Core.TelephonyManager.SignalingSessionReceived(Object sender, SessionReceivedEventArgs e)

    event id 32768 source Microsoft exchange speech

    when i see the lync client configuration information i find one thing which is UCS Connectivity State;Exchange connection Down

    could any one please help i m very frustrated with this behaviour of exchange.

    i have fetched the logs on FE but i cant post it here becuase there are lots of confidential information in it can u share the email address with me so that i will email you directly.

    Thanx for your help.

    SKHATRI
    Wednesday, August 10, 2011 10:56 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    You can ignore the "'The media description received from the remote SIP peer has an invalid content type 'multipart/alternative'" error, that is a known issue with Lync and Exchange 2007. 

    If you run trace for S4 and SIPStack on the Lync FE do you see anything obvious when you analyze the file with snooper?  If you do not know how to do this look here: http://blog.schertz.name/2011/06/using-the-lync-logging-tool/

     

    Mark King | MVP: Lync Server | MCTS:UC Voice | MCITP x3 :Lync, Enterprise Messaging 2010, EA | MCSE: Messaging | blog.unplugthepbx.com | Twitter: @unplugthepbx
    Wednesday, August 10, 2011 1:47 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    when i do the s4 and sipstack on the Lync FE i can see one error which is unsupported media type and another one i have found is internal error. Any idea what does these error means

    Regards,

    SKHATRI
    Wednesday, August 10, 2011 3:44 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi - not enough information with that.  Can you send the log to kingma10 at live dot com and I will take a look?  you can do a find/replace for private information if you wish.

    Mark

    Mark King | MVP: Lync Server | MCTS:UC Voice | MCITP x3 :Lync, Enterprise Messaging 2010, EA | MCSE: Messaging | blog.unplugthepbx.com | Twitter: @unplugthepbx
    Wednesday, August 10, 2011 7:26 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    hi,

    I have sent you the logs from the email address khatri_shehzad@hotmail.com kindly look in to this i will be very great full to you. One more thing is that some one told me that i have to enable the following ports between edge and UM is it true

    From  any endpoint on the inside (EXUM, FEPOOL, A/V and Clients alike) to the edgeserver inside interface, you need to allow SRTP/RTCP: 60000-64000 (TCP and UDP), STUN/TCP_443 and STUN/UDP_3478.

    From the edgeserver inside interface to any endpoint on the inside (EXUM, FEPOOL, A/V and Clients alike), you need to allow SRTP/RTCP: 60000-64000 (TCP and UDP), STUN/TCP_443 and STUN/UDP_3478.

    Signalling port 5060 (or 5061 as it should be with TLS) should go through the FE as you describe. I would, just for testing, open up for 5060 and 5061 to and from the UM/Edge just in case.

    Thanks

    SKHATRI
    Wednesday, August 10, 2011 9:09 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,SKHATRI,

    Have you told Exchange UM server to use the Edge authenication listening port at 5062 on the Edge internal interface with the following Exchange cmdlet.

    Set-UMServer ExchangeUMServer -SIPAccessService edgeinternal.domain.local:5062

     (Note:There may need 24h for replication completed to make this effect.)

    And here is another similar thread,hope it can give you some hints.

    http://social.technet.microsoft.com/Forums/da-DK/ocsucintegration/thread/bb7a8c75-ac1a-4925-80ed-98f6c7b66fe0

    Also,you can compare your Exchange UM and Lync configuration with this integration guide.

    http://blog.schertz.name/2010/11/lync-and-exchange-um-integration/

    Regards,

    Sharon


    Thursday, August 11, 2011 3:16 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    i think this command relates to exch2010 is this correct

    is there any port which i have to open from edge to um and um to edge i have exch 2007 sp1

     

    thanx

    SKHATRI
    Thursday, August 11, 2011 6:39 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,SKHATRI,

    I just noticed that your exchange version is Exchange 2007 SP1,the earlier version of Exchange 2007 SP2 is compatible with Lync 2010 but do not support the full degree of integration,so would you please upgrade your Exchange server to SP2?

    http://technet.microsoft.com/en-us/library/gg398806.aspx

    http://technet.microsoft.com/en-us/library/gg412817.aspx

    Regards, 

    Sharon


    • Edited by Sharon.Shen Friday, August 19, 2011 9:35 AM typo
    • Proposed as answer by Sharon.Shen Monday, August 22, 2011 1:47 AM
    Friday, August 19, 2011 9:34 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,SKHATRI,

    Any updates here?

    If you have fixed the issue please kindly share us the solution.Thanks!

    Regards,

    Sharon

    Thursday, August 25, 2011 2:23 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    hi sharon,

     

    the problem is still the same, Mark has asked to share the logs i have shared all logs with him 2 weeks ago but have not received any reply from him as well.

    Regarding exchange upgradation, we can not upgrade the exchange just like that. Is there any other possibililties which we have to look in to.

     

    Rgards,

    SKHATRI
    Thursday, August 25, 2011 8:35 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi SKHATRI,

    We have the same issue, have you managed to find a resolution with-out upgrading to Exchange 2010?

    The voicemail UM works fine with Lync if you're internal or dialling in through the PSTN but it doesn't work externally.

    Regards,

    Shaun

    Tuesday, February 21, 2012 1:39 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Shaun,

    Which version of exchange are you using Exchange 2007 SP2 or SP3 if it is SP1 it will never work from outside. You have to upgrade your exchange to 2010. However before upgrading server can you answer me the following

    How many network cards are there on Lync Edge server it should be two interfaces one for the external another one for internal. Also please open ports between edge server and UM server.

    Thanks

    SKHATRI

    My Blog: http://salahuddinkhatri.wordpress.com

    MCITP Microsoft Lync

    • Edited by SKHATRI Wednesday, February 22, 2012 7:01 AM wanted to add the footer
    Wednesday, February 22, 2012 6:59 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi SKHATRI,


    Thanks for gettings back to me, we're running Exchange 2007 SP2 (Version: 08.02.0247.002).

    We're using virtual servers for Lync so we can add interfaces on Edge if needed, though currently we have two interfaces (external and internal). We don't have a perimiter firewall yet, so the internal interface on Edge is on the same range as the other Lync servers. The rest of the domain (inc UM server) is on a different subnet which is connected though a VPN, but all ports here are open.

    I've added the external IP of our UM server to be allowed (all ports) on the external interface for Edge. I've run a Wireshark trace and can see that I try to communicate with the internal IP of our UM server even though I'm connected externally through Edge, I then establish communication with the external IP of the UM server (HTTPS) but after that it fails. It works fine internally and there's nothing I can see in the way of logs on the UM server which could be of any use to us.

    Have you got any ideas?

    Regards,

    Shaun

    Wednesday, February 22, 2012 9:00 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    As what i have understood from your answer is that ther are two interfaces on Edge servers but they both are on the same subnet and you do not have any firewall yet. Scenarios some thing like yours where both Edge interfaces are connected but are able to route with each other is not supported by Microsoft as External interface and Internal interface should not route with each other.

    you have talked about VPN here which means you either have a two sites in which one site have Edge server and another site have UM servers correct? or users connect their lync client from outside using VPN? if users are connecting from outside through VPN then Edge servers doesnt come in the picture.

    What do you mean by your external IP of your UM, there should be only one IP of UM, we dont publish UM servers, please explain this in more details. your scenario sounds you are doing some thing wrong.

    Keep in mind Edge internal interface should communicate with the UM server(UM server's internal IP there is no external IP, this IP should be the same IP when users connect their Lync client to UM internally) on specific ports and here you are talking about only https. also instead of wireshark use Lync logging tool when you start communication between lync client and um.

    Do you have subscriber and AA number. Are you able to call to AA and SA number from your mobile or land line, if yes then does it connect immidiately or there is a delay as well. What is your IP PBX.

    SKHATRI
    My Blog: http://salahuddinkhatri.wordpress.com

    MCITP Microsoft Lync

    SKHATRI


    • Edited by SKHATRI Wednesday, February 22, 2012 7:11 PM Wanted to ask more questions
    Wednesday, February 22, 2012 7:08 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi SKHATRI,

     

    Thanks for getting back to me; I've laid out my response to each question so it's easier to digest.

     

    -------------

     

    Question

    As what i have understood from your answer is that ther are two interfaces on Edge servers but they both are on the same subnet and you do not have any firewall yet. Scenarios some thing like yours where both Edge interfaces are connected but are able to route with each other is not supported by Microsoft as External interface and Internal interface should not route with each other.

     

    Answer

    We have one external interface (46.31.xxx.xxx) on the Edge server and one internal (192.168.100.xxx) interface, they are on different subnets. We have an external firewall which protects external interfaces, but no perimeter firewall (internal) at the moment so all the other internal Lync servers are on the same subnet (192.168.100.xxx) though all ports are open at the moment between the external Lync users and Edge.

     

    -------------

     

    Question

    you have talked about VPN here which means you either have a two sites in which one site have Edge server and another site have UM servers correct? or users connect their lync client from outside using VPN? if users are connecting from outside through VPN then Edge servers doesnt come in the picture.

     

    Answer

    The UM server and the rest of the domain (192.168.0.xxx) are connected through a site to site VPN, users connect to Lync externally using the Edge server (external interface).

     

    -------------

     

    Question

    What do you mean by your external IP of your UM, there should be only one IP of UM, we dont publish UM servers, please explain this in more details. your scenario sounds you are doing some thing wrong.

     

    Keep in mind Edge internal interface should communicate with the UM server(UM server's internal IP there is no external IP, this IP should be the same IP when users connect their Lync client to UM internally) on specific ports and here you are talking about only https. also instead of wireshark use Lync logging tool when you start communication between lync client and um.

     

    Answer

    The internal IP of the UM server was already allowed on Edge, you mentioned that we need to open ports between Edge and UM server so I've also allowed the external IP of the UM server but if we don't need this then I'll remove it.

     

    When I connect to Lync internally UM works fine as do the AA's, but externally when I call the Voicemail service or AA's it says connecting for 2 minutes then eventually fails. We can see that Lync trys talking with each of the internal IPs of the UM server which will never work externally, before finally establishing communication over HTTP using the external IP of the UM server.

     

    The UM server encapsulates MAPI over HTTPS for external users.

     

    -------------

     

    Question

    Do you have subscriber and AA number. Are you able to call to AA and SA number from your mobile or land line, if yes then does it connect immidiately or there is a delay as well. What is your IP PBX.

     

    Answer

    Yes we do and they work fine if we call the numbers from a mobile or landline, it connects immediately. We don't have an IP PBX, there's a trunk between the Lync Front End Server and an external SIP Provider.

     

    -------------

     

    I've followed everything that should have been done so we're running out of ideas, it seems the Edge server is referring external Lync users to the UM server rather than establishing the communication it's-self is this correct?

     

    Regards, Shaun

    Thursday, February 23, 2012 11:30 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Well now your answers are quite descriptive. Remote the external IP from UM. as Edge internal interface should connected to UM directly. As you mentiond that there is no firewall between um and edge internal interface then every thing should work perfectly fine.

    If all is working fine internally then i have a suggestion to upgrade your exchange to 2010. In my environment it didnt work and i have to upgrade out environment to exchange 2010 SP1.

    Please mark it as answer if this answers your question | MCITP Microsoft Lync | My Blog: http://salahuddinkhatri.wordpress.com

    SKHATRI

    • Proposed as answer by ITEC Support Thursday, February 23, 2012 12:50 PM
    • Marked as answer by SKHATRI Thursday, February 23, 2012 1:29 PM
    Thursday, February 23, 2012 11:37 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi SKHATRI,

    Thanks for your input, I had already begun to draw to the conclusion that we need to upgrade to Exchange 2010 but thought I would have one last attempt to find a solution.

    You've been a great help.

    Regards, Shaun

    Thursday, February 23, 2012 12:50 PM