Lync Calling Integration

Hi,
I am wondering if someone could perhaps shed some light on this matter.
Over the past few days we have tried using various Voip/Sip C# applications in attempt to
initiate a call from these applications to a user running Lync. We are testing against a active Office 365 account that
has various accounts with Lyn enabled.
All DNS settings have been verified and other users running Lync or even Skype are able to initiate calls and messaging to the account mentioned above.
What are we missing?
Regards
Louis

This is a development issue, you can post your question in the following forum:
http://social.msdn.microsoft.com/Forums/lync/en-US/home?forum=communicatorsdk
Lisa Zheng
TechNet Community Support

Similar Messages

  • Lync 2013 integration with Avaya Communication Manager Version 5.2 and Avaya Session Manager 6.3

    Hi Team,
    I have a situation, We have done integration between Avaya Communication Manager Version 5.2, Avaya Session Manager 6.3 and Lync 2013.
    I’m able to make lync to lync call via extension number but not lync to avaya extension vice versa and lync to mobile calls. Will appreciate your help.
    A PBX gateway has been marked as less-preferred.
    Gateway name: sm.contoso.com
    Response Code: 400
    Consecutive Failure occurrences: 29
    Cause: The gateway responded with the same failure response multiple consecutive times and is being marked as less-preferred.
    Resolution:
    Verify that the gateway is functioning correctly.

    Did you add Avaya Session Manager as a PSTN gateway in Lync Topology?
    Did you create dial plan and related normalization rule for extension in Avaya telephone system.
    Which guide did you use to integrate Avaya Aura Session Manager with Lync Server?
    You can check the following deployment guide:
    http://www.microsoft.com/en-hk/download/details.aspx?id=41152
    Lisa Zheng
    TechNet Community Support

  • Lync to Lync calls not working when users outside of network. But calls from Lync to external numbers do work.

    Hello,
    We are having the following issue: when our lync users are outside of our network, just connected to their home internet or a public WiFi  and not on VPN, they cannot place calls to other
    Lync users inside our network. They get a poor network connection message on the call window. But they are able to make calls from Lync to external numbers without a problem.
    Inside our network, Lync to Lync calls work perfectly fine, the same for calls from Lync to external numbers.
    Does anybody know what could be the cause of our issue? Perhaps I'm missing a setting on our Edge server. What should be the first thing I should check on my Lync servers?
    Thanks for any help!

    Have you opened up ports on your firewall from your internal clients to the edge on UDP/3478 and TCP/443?  This sounds like you might have a problem there.  Can you internal clients properly route to this subnet and resolve the pool name of your
    edge pool? 
    Ports and protocols poster, check out in A/V section client traffic to edge showing UDP/3478 and TCP/443:
    http://www.microsoft.com/en-us/download/details.aspx?id=39968 
    Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer".
    SWC Unified Communications
    This forum post is based upon my personal experience and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

  • Url to call Integration engine from Webserver

    Hi All,
    Please let me know what is the url to call INtegration engine from Webserver
    I know below is url which we will use to call Adapter engine..But i need direct call to Integration engine
    http://server:50100/XISOAPAdapter/MessageServlet?channel=:R3_DEV:R3_CHANNEL_sender
    Thanks and Regards
    Suma S
    Edited by: Suma S on May 3, 2011 5:51 PM

    the url will have the format of
    http://hostname:8000/sap/xi/adapter_plain?type=entry&sap-user=xisuper&sap-password=******&namespace=<namespace>&interface=<interfacename>&service=<servicename>

  • New lync contacts default to cell phone for lync call button (part 2)

    The problem is that when a Lync 2013 user adds a new contact, and then tries to place a call in Lync, the default option for the Lync call button to that newly added contact is that contact's cell phone (if that contact has added a cell phone number). 
    The default should be a Lync call, not a cell phone number.
    Others (thank you very much!) have answered very similar questions here: http://social.technet.microsoft.com/Forums/lync/en-US/80fde051-1d3c-495e-aa32-63e93e5e4104/change-the-default-oneclick-audio-call-option-on-lync-clients?forum=ocsvoice
    and here: http://social.technet.microsoft.com/Forums/lync/en-US/cd05243c-bbcf-46f4-9269-045d9c31867b/how-to-set-the-default-number-on-a-lync-contact-to-lync-call-instead-of-work?forum=ocsclients
    So I understand one possible solution is to: Set-CsClientPolicy -Identity Global -EnableVOIPCallDefault $true
    However, here's the odd issue I'm having and why I'm posting:  I ran Get-CsClientPolicy across three different, independent Lync servers (all for completely different orgs/domains that are managed separately) that I have access to, and the EnableVOIPCallDefault
    is set to false for all of them.    However, this problem behavior is only affecting one of the orgs, the other two, when a new contact is added, the call button in the  Lync client defaults to a Lync call, not a cell number.
    So why, if across three independently managed Lync servers, if the EnableVOIPCallDefault is set to false, would it only be defaulting to cell phones in one?  I compared the results of the three Get-CsClientPolicy, and could not find a logical pattern
    in any of the settings that could explain.
    The only thing that I can think of is that the org that is affected, the line uri is a 4 digit extension, not a full 10 digit phone number.  In the other two orgs (including the one that I am a user in), it's a full 10 digit phone number.

    EnableVOIPDefault is only the default option for the first click-to-call for a contact, once a different number is selected it becomes the default and the policy has no effect.
    Take a look at Richard Brynteson's blog about Controlling Click-to-Call: http://masteringlync.com/2014/01/27/controlling-click-to-call/ 
    Please mark posts as answers/helpful if it answers your question.
    Blog
    Lync Validator (BETA) - Used to assist in the validation and documentation of Lync Server 2013.

  • Lync 2013 click to call from Outlook 2013 does not have the option for Lync call

    Hello,
    We are currently migrating from OCS 2007 r2 to Lync 2013. We are on office 365, but Lync is on premise. After migrating several users the option in Outlook to click to call someone only shows one option, which is to call the person's desk phone. Before there
    was a dropdown where you could choose desk phone, mobile or Lync call. This issue isn't happening to everyone. We are using Office 2013 and Office 2010. Please let me know if you have suggestions or if you need more info.
    Not sure if this is related, but some people have lost the option to view their contact's pictures. 
    Thank you in advance,
    Mitch

    Hi,
    Please see the image below, are we talking about this?
    If a contact doesn't have a phone number, we surely can't call him.
    You can try updating the Offline Address Book to see the result:
    http://www.howto-outlook.com/howto/oabupdate.htm
    If I got anything wrong, feel free to post back.
    Regards,
    Melon Chen
    TechNet Community Support

  • Using incorrect information when trying to make a lync call

    In outlook 2010, when I right click on one of the Frequent contacts in the to-do bar area and click on the phone to call the contact. I get a popup saying "The calling feature is disabled." This is because instead of placing a lync to lync call
    it's trying to call their phone. Is there a way to get the default action to make a lync to lync call instead of trying to place a lync to phone call?
    BTW not sure if this is the correct forum to place this into. Please feel free to move to the correct forum or let me know and I'll post in another forum.

     Hi,
    Would you please elaborate your Lync Server environment?
    Did the issue also happen if you call the user in Lync client interface?
    Please check if the user you want to call enable Lync or not. If not, the Lync Server need to deploy Enterprise Voice, and you need to enable Enterprise Voice function to support it.
    Best Regards,
    Eason Huang
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
    Eason Huang
    TechNet Community Support

  • Lync calls routing wrongly

    Hi All,
    I'm sorted of stumped at the moment.
    The Scenario :
    Lync 2013 deployment
    Client has 4 sites - the sites are connected via vpn tunnels and has firewalls at each site.
    User calls form site D to Site C and they experience one way audio. User calls from site C to site D and the call is fine.
    User calls from site A to site C and the call is fine. User calls from site C to site A and one way audio might occur. User calls from site a to site D and there is one way audio. User calls from site D to site A and call is fine.
    Devices uses - vvx410 phones.
    Problem - can't see QoE on reporting as the vvx phones don't provide it.
    So over to logging it seems that calls from site D is trying to come form the internal ip of the edge server's private ip to the user in site C. So it seems that during the call setup that UDP to UDP peer to peer is not happening and then uses the edge server
    to route the call through. No at site D hairpinning on the edge server is not allowed. From sites A-C it seems that the call is hairpinning via the edge's public ip as that is allowed.
    There are firewall restrictions in place between the sites and what the client tried was to open full ip to ip on the phones between the sites as that should in theory allow UDP to UDP, but that does not seem to happen.
    Could this be a routing issue between the sites? We have booked a network engineer and firewall engineer to troubleshoot this issue. On the lync side I've not restricted any ports.
    Will be greay if someone had this issue before.
    Regards
    Danie

    Hi Greg/Anthony
    Thanks for your replies so far.
    The Lync setup consists only out of 1 Lync Edge server and 4 Lync Standard Edition server that is spread across the WAN. The lync static route to the inside nic does cover 172.18.0.0, in which all the subnets between all the sites are covered. The vvx phones
    are located in a voice vlan (we recently had a issue with vvx phones losing their ip addresses and got the network engineer to reconfig the one site to create smaller subnets and then the issue was traced to 4 3COM switches). Their used to be only one voice
    vlan, which is still the case at 3 sites, but the one site has quite a few voice vlans now to cater for all the subnets that were created, but I don't think this is the root of the problem. The one unfortunate thing is that on the lync reporting server you
    can't see any QoE info apart from when a call is made from a vvx to a cx600 phone and usually when it is cross site the report will show that the vvx phone is coming from the external private ip of the lync edge servers AV nic. Today I did ask the client to
    test by doing a lync to lync call, but since they are remote I can't foresure say that they did it correctly as the one user had a cx600 connected to his desktop and I wanted them just to use headsets and make the lync calls - I will get to try that out next
    week when we will be at the client with a FW and network engineer to troubleshoot.
    I also used the centralized logging tool in lync, but I don't seem to be able to locate the section where it shows the final candidate paring for a particular call, so I can't verify what the final candidate paring is. I can however see the initial candidate.
    From the vvx410 phone is always uses a 22** port on UDP as the 1st candidate - I'm not sure if that is a fault as I would expect it to be in the 50,000 - 59,999 range as that is what the firewall engineer is seeing on his side.
    I will also be able to do a wireshark trace - we have a port mirrored permanently on the one switch for the one user.
    The main issue here is that there does not seem to be a peer to peer udp connection between the clients, so the edge server should never come into play here as the clients are inside the same WAN, alltough they are separated by 2 firewalls between 2 sites,
    but connected via a vpn tunnel between the 2 firewalls.
    Lync calls from the internet is working without any issues by the way.
    Regards
    Danie

  • Default setting to "Lync Call"

    Everyone,
    I am trying to find a policy or regedit that will always default the calling methong to "Lync Call"  I know you can set the initial default using the below command, but need to find a way to always default to "Lync Call"
    Set-CsClientPolicy -Identity Global -EnableVOIPCallDefault $true
    Any help would be greatly appreaciated.
    Dan Peters

    Hi Dan,
    You can mark answers to close this post. You can also try to use "Give us feedback online" in Lync client help menu or go to Microsoft feedback website to give your comments
    on the product. Microsoft will consider to add the feature if it’s  a valuable or most customers concerned it.
    Regards,
    Kent

  • QoS values to match Lync-calls

    A customer of ours is tuning QoS for Lync for better voice-quality. The wired network works fine, but on the wireless it looks like there are some “drops” from time to time.
    The Lync-calls are tagged with AF41.
    There are 4 types of QoS on the WLC. At the moment SSID is configured as Silver, but should it be Gold (instead of Silver) to match AF41?
    Based on this document, Gold is AF41. Is that correct?
    Is there anything else we could adjust and will they benefit from that QoS change?
    Thank you!

    Prior to configuration optimization, you need to ensure you have sufficient wireless coverage (20% overlap) & preferably clients are connecting in 5GHz band. This design guide cover most of topics (Voice, QoS, Multicast,etc) & read it thoroughly to see whether your wireless deployment adheres to those recommendation.
    http://www.cisco.com/en/US/docs/solutions/Enterprise/Mobility/emob73dg/emob73.html
    With respect to QoS here is my suggestions.
    1. QoS profile to configured Platinum with 802.1p=6 (this will allow proper voice packets comes with 802.11e UP of 6 passthrough without capping the QoS value)
    http://mrncciew.com/2012/12/02/understanding-wireless-qos-part-3/
    2. WMM (under WLAN -> QoS ) to be set as "Required" to avoid non-WMM traffic get prioratised.
    http://mrncciew.com/2013/07/30/wmm-qos-profile/
    3. If all local mode APs, you need to configure the QoS trust boundaries as below
    - AP connected switchport : DSCP
    - WLC connected switchoport : CoS
    - inter switch trunks : DSCP
    4. Makesure WLC management interface is not on native vlan (in otherwords on a tagged vlan) in order to proper QoS functionality.
    http://www.cisco.com/en/US/tech/tk722/tk809/technologies_tech_note09186a0080c01d2c.shtml
    5. If you are using AVC, better you mark up this traffic as EF, so your wired network will properly treat this traffic as Voice. Otherwiese this traffic will treat as video & will not get required priority within your network.
    Additionally make sure priority queue "priority-queue out interface config" enabled for your access layer switchports. Below QoS guide help you to verify your switch QoS configuration, see whether you configured in inline with this guide recommendation
    http://www.cisco.com/en/US/docs/solutions/Enterprise/Video/qoscampuscat3xxxaag.html
    HTH
    Rasika
    **** Pls rate all useful responses ****

  • Join conference via Lync call rather than Call Me At

    We have deployed Lync Server 2013 and are just beginning to deploy it in small doses to portions of the organization.  We are using a combination of Lync 2010 and 2013 for clients.  This post is regarding the Lync 2013 client.
    We use Lync with Cisco telephony via Remote Call Control.  We do have PC-to-PC calling enabled in addition to RCC (the Telephony setting in Lync Control Panel on the user accounts is "Remote Call Control").  We are not using Enterprise
    Voice.
    After deploying Lync as simply an IM + telephony client, we have begun to focus on rolling out the web conferencing functionality.  In doing so, we have noticed strange behavior which I describe below.
    Let us assume that someone other than me creates web conference by selecting two people, including me, in their Lync contacts list in the client, right clicks, and selects "Start a conference all" and then chooses "Lync call".  I
    see a Lync toast notification appear, inviting me to a conference.  It says the conference organizer's name and says "Conference Call".  If I click the toast to accept the conference, my Cisco telephone extension immediately begins to ring. 
    In the meantime, in the Lync conference in the client I see "Join Conference Call" and "Other".  If I answer answer my telephone extension or push the Join Conference Call button, I am successfully joined to the Lync audio conference
    and can speak with anyone else that joined the conference, whether they are using Lync audio or Cisco telephony.
    The problem is that there are cases where we want to do a video conference.  I am aware that can only be done if using Lync audio rather than the Cisco telephony.  I can disconnect from the conference call by hanging up my Cisco extension. 
    When I do so, the Lync conference in the client shows a notification that gives me the option to rejoin the conference.  The "Rejoin" button has a down arrow, and if I expand it I can select "Rejoin using Lync Call" and if I do that
    I can now see others' webcams and can share my own webcam with the conference.
    My question is: how can I elect to join the conference in the first place with a Lync call rather than having the Lync conference bridge dial my Cisco extension?  There does not seem to be a way to do this that we can get to work.  For instance,
    I mentioned that after I have clicked the Lync toast notification after being added to the conference and my Cisco phone begins ringing that I see the options "Join Conference Call" and "Other" in Lync client.  If I open the Other
    options, I see "Join using Lync Call" as an option.  If I select that option, my Cisco phone answers the call and I am joined to the Lync audio conference with my Cisco phone and not Lync audio.
    Please note that I already checked the Phone section in the Lync 2013 client options and the box "Before I join meetings, ask which audio device I want to use" is checked and the "Join meeting audio" drop-down box is set to "Lync".

    Sorry, I misread your question and now see that I did not pre-emptively answer it.  I just tested it and unchecked the box "Before I join meetings, ask which audio device I want to use" and made sure "Join meeting audio" was set to "Lync".  Even
    after doing so, the behavior is the same:  the Cisco phone automatically rings and any action to join the conference results in the Cisco phone extension being picked up.
    Basically, it seems that if you use that "Start a Conference Call" option from the Lync contacts list, the Lync preferences set in the recipients' Lync clients are ignored.  If you schedule a Lync conference via Outlook or people use the Lync meeting
    URL in their Internet browser, it does respect the preferences correctly.  It seems like it might be a bug.
    I would be interested if any other Lync Server 2013 users with Lync client 2013 and using RCC could repeat my tests and see if they have the same issue.

  • Cannot Video Conference or Lync call with users outside of the Firewall

    I am having the following issues:
    Internal users can video conf and call each other fine.
    User A internally can Lync call user B externally and voice is ok
    User B externally calls user A and user A sees no toast or anything
    User A internal tries to video call user B External but it says starting video
    User B external tries to video call user A internal and no toast appears
    I have eliminated the firewall to my external edge interface as I have temporarily added an ANY rule to make sure no ports are being blocked.
    I have 1 public IP with
    AV edge using 443
    Web Conf using 444
    and SIP using 5061
    because I cannot "toast" and internal user from external with
    either video call or lync voice call the common traffic is:
    A/V Edge ICE/STUN:443 Stun/UDP:3478
    A/V Edge SRTP:443,3478 TCP 50,000-59,999
    Does anyone have any ideas what the issue might be or what I can do to test?
    1 Lync 2010 Edge Server 1 Lync 2013 FE Server
    ***Don't forget to mark helpful or answer***

    The traffic is getting to the front end server as I monitored SIP stack on the front end and got this from the log after initiating the call request...
    TL_INFO(TF_PROTOCOL) [1]131C.2280::05/15/2014-15:41:51.239.00000020 (SIPStack,SIPAdminLog::ProtocolRecord::Flush:ProtocolRecord.cpp(265))[4195629786] 
    $$begin_record
    Trace-Correlation-Id: 4195629786
    Instance-Id: 30A7
    Direction: outgoing
    Peer: 10.1.5.98:58292
    Message-Type: request
    Start-Line: INVITE sip:10.1.5.98:58292;transport=tls;ms-opaque=69ab187213;ms-received-cid=15400 SIP/2.0
    From: "Mitch King"<sip:[email protected]>;tag=de00273c69;epid=0bf6878c0e
    To: <sip:[email protected]>;epid=2c737c11a8
    Call-ID: e5bf68f84e0643839d3fc3524bf0a925
    CSeq: 1 INVITE
    Contact: <sip:[email protected];opaque=user:epid:K2EhWwgpmFyEPyRPWajS8wAA;gruu>
    Via: SIP/2.0/TLS 10.1.3.106:5061;branch=z9hG4bKEAAC5ABA.63098DB96B0459CF;branched=FALSE;ms-internal-info="ccNiK2JF2ymTwz69iEJ-Koh9KulADFeojTs5M7Oy7Yteq5jQljcydysgAA"
    Via: SIP/2.0/TLS 172.16.4.5:49216;branch=z9hG4bK0A64EEE1.72E873C44EADB9CF;branched=FALSE;ms-received-port=49216;ms-received-cid=14D00
    Via: SIP/2.0/TLS 172.20.10.7:49185;received=213.205.233.99;ms-received-port=47938;ms-received-cid=1500
    Record-Route: <sip:JNBSKV06.domain.co.uk:5061;transport=tls;opaque=state:T:F:Ci.R15400;lr;ms-route-sig=fas5y5A_Hi8kKMcMSekbcP058TEzxR0PC0fCKvEXCZO8S5jQljkAzQcAAA>;tag=A4CC2A746138BB8B2479B24FCDD3009C
    Max-Forwards: 68
    Content-Length: 4662
    Content-Type: multipart/alternative;boundary="----=_NextPart_000_001F_01CF705C.920384C0"
    Message-Body: ------=_NextPart_000_001F_01CF705C.920384C0
    Content-Type: application/sdp
    Content-Transfer-Encoding: 7bit
    Content-ID: <[email protected]>
    Content-Dis; handling=optional; ms-proxy-2007fallback
    v=0
    o=- 0 0 IN IP4 181.39.65.34
    s=session
    c=IN IP4 181.39.65.34
    b=CT:99980
    t=0 0
    m=audio 59182 RTP/SAVP 114 9 112 111 0 8 116 115 4 97 13 118 101
    a=candidate:RbmFhQT26e8jfmCHHNDiiSm4NNjv3BrThjDipLYc9fQ 1 lW66uiImb0jhBi7NTpWyFg UDP 0.830 172.20.10.7 12252 
    a=candidate:RbmFhQT26e8jfmCHHNDiiSm4NNjv3BrThjDipLYc9fQ 2 lW66uiImb0jhBi7NTpWyFg UDP 0.830 172.20.10.7 12253 
    a=candidate:a1v6y+uA7x0DXU+4yO610jGEhZlHstMX+bFcj3G9/JY 1 iLWi/RPFsw/i/z5MX2n6+w TCP 0.190 181.39.65.34 54566 
    a=candidate:a1v6y+uA7x0DXU+4yO610jGEhZlHstMX+bFcj3G9/JY 2 iLWi/RPFsw/i/z5MX2n6+w TCP 0.190 181.39.65.34 54566 
    a=candidate:lJEokTFI5l/qLQ4yb72D2US/uQtgJN9F5UNNlN+wsYU 1 5iW2Mv+VRFVMpZVS6glc6Q UDP 0.490 181.39.65.34 59182 
    a=candidate:lJEokTFI5l/qLQ4yb72D2US/uQtgJN9F5UNNlN+wsYU 2 5iW2Mv+VRFVMpZVS6glc6Q UDP 0.490 181.39.65.34 51845 
    a=candidate:u2uHk5L+RctPvbqIA6asJAT5h0kjBj0L06I8bKwUr9I 1 6y3UI2Y5SmfiROa+dCxgDA TCP 0.250 213.205.233.99 10012 
    a=candidate:u2uHk5L+RctPvbqIA6asJAT5h0kjBj0L06I8bKwUr9I 2 6y3UI2Y5SmfiROa+dCxgDA TCP 0.250 213.205.233.99 10012 
    a=candidate:WawePotOSAKzTE3UjFxrFaULbrWoKE+8azhkahUlBvQ 1 L0TZQvD2nRP1kIR6SFEbMQ UDP 0.550 213.205.233.99 10015 
    a=candidate:WawePotOSAKzTE3UjFxrFaULbrWoKE+8azhkahUlBvQ 2 L0TZQvD2nRP1kIR6SFEbMQ UDP 0.550 213.205.233.99 10016 
    a=cryptoscale:1 client AES_CM_128_HMAC_SHA1_80 inline:gtklU/YbidFvHH7yktIG1IgAJYmdEQfpOKCbhs1t|2^31|1:1
    a=crypto:2 AES_CM_128_HMAC_SHA1_80 inline:dKGa1f82DCYMtzMzQFYr/c2HYvpWHCkkSSBZTDzw|2^31|1:1
    a=crypto:3 AES_CM_128_HMAC_SHA1_80 inline:JjNTaKZwo9xX+ebB4bXV1n+JkKDWaLk98qjfH+uB|2^31
    a=maxptime:200
    a=rtcp:51845
    a=rtpmap:114 x-msrta/16000
    a=fmtp:114 bitrate=29000
    a=rtpmap:9 G722/8000
    a=rtpmap:112 G7221/16000
    a=fmtp:112 bitrate=24000
    a=rtpmap:111 SIREN/16000
    a=fmtp:111 bitrate=16000
    a=rtpmap:0 PCMU/8000
    a=rtpmap:8 PCMA/8000
    a=rtpmap:116 AAL2-G726-32/8000
    a=rtpmap:115 x-msrta/8000
    a=fmtp:115 bitrate=11800
    a=rtpmap:4 G723/8000
    a=rtpmap:97 RED/8000
    a=rtpmap:13 CN/8000
    a=rtpmap:118 CN/16000
    a=rtpmap:101 telephone-event/8000
    a=fmtp:101 0-16
    a=encryption:required
    ------=_NextPart_000_001F_01CF705C.920384C0
    Content-Type: application/sdp
    Content-Transfer-Encoding: 7bit
    Content-ID: <[email protected]>
    Content-Dis; handling=optional
    v=0
    o=- 0 0 IN IP4 181.39.65.34
    s=session
    c=IN IP4 181.39.65.34
    b=CT:99980
    t=0 0
    m=audio 57869 RTP/SAVP 114 9 112 111 0 8 116 115 4 97 13 118 101
    a=ice-ufrag:V8SO
    a=ice-pwd:cPfWCmdBZf5ok2wzZmhGw4iJ
    a=candidate:1 1 UDP 2130706431 172.20.10.7 22964 typ host 
    a=candidate:1 2 UDP 2130705918 172.20.10.7 22965 typ host 
    a=candidate:2 1 TCP-PASS 6556159 181.39.65.34 50574 typ relay raddr 213.205.233.99 rport 10013 
    a=candidate:2 2 TCP-PASS 6556158 181.39.65.34 50574 typ relay raddr 213.205.233.99 rport 10013 
    a=candidate:3 1 UDP 16648703 181.39.65.34 57869 typ relay raddr 213.205.233.99 rport 10014 
    a=candidate:3 2 UDP 16648702 181.39.65.34 57495 typ relay raddr 213.205.233.99 rport 10017 
    a=candidate:4 1 UDP 1694235647 213.205.233.99 10014 typ srflx raddr 172.20.10.7 rport 20732 
    a=candidate:4 2 UDP 1694234110 213.205.233.99 10017 typ srflx raddr 172.20.10.7 rport 20733 
    a=candidate:5 1 TCP-ACT 7076351 181.39.65.34 50574 typ relay raddr 213.205.233.99 rport 10013 
    a=candidate:5 2 TCP-ACT 7075838 181.39.65.34 50574 typ relay raddr 213.205.233.99 rport 10013 
    a=candidate:6 1 TCP-ACT 1684797439 213.205.233.99 10013 typ srflx raddr 172.20.10.7 rport 25165 
    a=candidate:6 2 TCP-ACT 1684796926 213.205.233.99 10013 typ srflx raddr 172.20.10.7 rport 25165 
    a=cryptoscale:1 client AES_CM_128_HMAC_SHA1_80 inline:gtklU/YbidFvHH7yktIG1IgAJYmdEQfpOKCbhs1t|2^31|1:1
    a=crypto:2 AES_CM_128_HMAC_SHA1_80 inline:dKGa1f82DCYMtzMzQFYr/c2HYvpWHCkkSSBZTDzw|2^31|1:1
    a=crypto:3 AES_CM_128_HMAC_SHA1_80 inline:JjNTaKZwo9xX+ebB4bXV1n+JkKDWaLk98qjfH+uB|2^31
    a=maxptime:200
    a=rtcp:57495
    a=rtpmap:114 x-msrta/16000
    a=fmtp:114 bitrate=29000
    a=rtpmap:9 G722/8000
    a=rtpmap:112 G7221/16000
    a=fmtp:112 bitrate=24000
    a=rtpmap:111 SIREN/16000
    a=fmtp:111 bitrate=16000
    a=rtpmap:0 PCMU/8000
    a=rtpmap:8 PCMA/8000
    a=rtpmap:116 AAL2-G726-32/8000
    a=rtpmap:115 x-msrta/8000
    a=fmtp:115 bitrate=11800
    a=rtpmap:4 G723/8000
    a=rtpmap:97 RED/8000
    a=rtpmap:13 CN/8000
    a=rtpmap:118 CN/16000
    a=rtpmap:101 telephone-event/8000
    a=fmtp:101 0-16
    a=encryption:required
    ------=_NextPart_000_001F_01CF705C.920384C0--
    $$end_record
    ***Don't forget to mark helpful or answer***

  • Lync call goes on hold when I touch the mouse or keyboard

    Hi
    I have an issue when I am on a lync call that if I touch the keyboard or mouse the call is put on hold. Very frustrating and I can find nothing about it. Anyone else encountered this issue, or better still have a resolution?
    Lync 2013 is being used. 
    Thanks
    Steve

    Hi,
    Did the issue happen only for you or for multiple users?
    You can test the issue on other computer Lync client with your Lync account.
    Please delete user profile on your local computer with the following path:
    %UserProfile%\AppData\Local\Microsoft\Office\15.0\Lync
    And check if Lync client update to the latest version, if not, update Lync client and then test again.
    Best Regards,
    Eason Huang
    Eason Huang
    TechNet Community Support

  • Lync Call while leaving wireless network

    Hello Everyone,
    I am sure this is a common question however I cannot seem to find a straight forward answer.  Let's say we have a full Lync 2013 UC deployment with voice and a users mobile phone (with the Lync client installed) starts a Lync call (to an outside
    person or another Lync contact) while connected to the wireless network.  While still on the call they leave the office and start driving home.  What happens when that person leaves the wireless network?  Does the Lync call drop and reconnect? 
    Will the end users notice?
    Thanks for any information.

    Lync 2013 Mobile does not support handover between wifi and cellular networks for active calls. Take a look at:  http://www.pro-exchange.be/blogs/lync2013/archive/2013/03/14/lync-2013-mobile-and-handover-support.aspx
    Please mark posts as answers/helpful if it answers your question.
    Blog
    Lync Validator - Used to assist in the validation and documentation of Lync Server 2013.

  • Cisco Tandberg VCS Lync 2010 integration with SBA

    Hello All,<o:p></o:p>
    situation: three Lync 2010 central sites (pool plus
    directors) and one VCS Lync gateway (two VCS clustered together).<o:p></o:p>
    Having said that a part from slightly changing what
    said in CISCO literature (configuring pool FQDN in VSC Lync gateway rather than
    the director) everything is running fine.<o:p></o:p>
    The problem arose when the customer introduced a SBA
    in the configuration. Users homed on it are not able to enjoy the integration
    features (basically video calls from Lync clients and Tandberg stations do not work).
    Can you please advise on the above?
    Thank you in advance
    beppe
    giuseppe

    Hello Michael,
    error log is quite vague
    04/28/2013|05:50:14.427 F58:F5C INFO  :: Data Received - 195.68.79.115:443 (To Local Address: 192.168.1.11:51038) 933 bytes:
    04/28/2013|05:50:14.427 F58:F5C INFO  :: SIP/2.0 403 Forbidden
    ms-user-logon-data
    : RemoteUser
    Authentication-Info
    : TLS-DSK qop="auth", opaque="F7400E1E", srand="04D08FB0", snum="227", rspauth="3973379f551073e0dee64a0bb16029a555dd8e0c", targetname="LyncDIRLU1.global.sys", realm="SIP Communications Service", version=4
    Via
    : SIP/2.0/TLS 192.168.1.11:51038;received=109.214.195.106;ms-received-port=51038;ms-received-cid=4CD6F00
    Call-ID
    : c1c2cd9deb854ec0aea5de7e5b4f5a3c
    CSeq
    : 1 SUBSCRIBE
    From
    : "SURNAME name" <sip:[email protected]>;tag=4d71bb0d17;epid=95a505c526
    To
    : <sip:[email protected]>;tag=67be8543cd326c63
    Allow
    : INVITE,ACK,BYE,CANCEL,INFO,OPTIONS,REFER,SUBSCRIBE,NOTIFY
    Server
    : TANDBERG/4352 (X7.1-b2bua-1.0)
    Content-Length
    : 0
    ms-diagnostics
    : 1033;reason="Previous hop server component did not report diagnostic information";Domain="videosipdomain.org";PeerServer="vcs-lync.contoso.it";source="SBARI1.global.sys"
    04/28/2013|05:50:14.427 F58:F5C INFO  :: End of Data Received - 195.68.79.115:443 (To Local Address: 192.168.1.11:51038) 933 bytes
    As a matter of fact I'd like to know if somebody got it working when SBAs are involved (as said no problem with normal pools).
    Cheeers
    beppe
    giuseppe

Maybe you are looking for