locked
Current defination for the "SIP:" in Skype RRS feed

  • Question

  • Hi,

    I have tried shortly to find answer for the question which has bounced in my mind:

    How the SIP address should be written: with lower case "sip:" or upper case "SIP:"? And I mean on both AD attributes:

    1. msRTCSIP-PrimaryUserAddress

    2. proxyAddresses

    When running the Skype on-premises that has been not a problem, all on lower case. But e.g. when having hybrid with Exchange services, the Exchange Online requires that proxyaddress have sip with upper case.

    So is there a real official document which discribes if that should be lower or upper case?


    Petri

    Wednesday, January 9, 2019 10:25 PM

Answers

  • Hi Petri,

    Yes, we also hope Microsoft will update the document about this in the near future.

    Best Regards,
    Evan Jiang


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    • Marked as answer by Petri X Friday, January 25, 2019 11:15 PM
    Tuesday, January 15, 2019 7:45 AM

All replies

  • Hi Petri,

    We did not find the official document shows the difference between msRTCSIP-PrimaryUserAddress and proxyAddresses. However, based on my research, proxyAddresses and msRTCSIP-PrimaryUserAddress are the corresponding attributes that are used in Exchange and Lync/Skype for Business. They are different. it depends how you integrate the on-premise environment with Office 365.
    1. Office 365 with on-premise Exchange without on-premise Lync/Skype for Business:
    You can add an entry "SIP:xxxxx@domain.com" to the proxyAddresses attribute.
    2. Office 365 with on-premise Exchange and on-premise Lync/Skype for Business:
    Do not modify them manually. The corresponding on-premise Exchange and Lync/Skype for Business management tools will modify the attributes.
    3. Office 365 with on-premise Lync/Skype for Busines without on-premise Exchange:
    You need to manage the proxyAddresses attribute for the email addresses.
    4. Office 365 with local AD only.
    Just manage the proxyAddresses attribute for both email addresses and the SIP address.

    You could refer to the following link to find the details.

    Note: This response contains a reference to a third party World Wide Web site. Microsoft can make no representation concerning the content of these sites. Microsoft is providing this information only as a convenience to you: this is to inform you that Microsoft has not tested any software or information found on these sites and therefore cannot make any representations regarding the quality, safety, or suitability of any software or information found there. There are inherent dangers in the use of any software found on the Internet, and Microsoft cautions you to make sure that you completely understand the risk before retrieving any software on the Internet.


    Best Regards,
    Evan Jiang


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.


    • Edited by woshixiaobai Thursday, January 10, 2019 3:21 AM
    • Proposed as answer by woshixiaobai Friday, January 11, 2019 5:56 AM
    Thursday, January 10, 2019 3:21 AM
  • Hi Evan87,

    That is kind of answer :) But this is a bit surprising that there is are no official statement. And this makes it very hard when you have Skype & Exchange. If you enabling user on-premises, the system (Skype FE) adds the proxy address with lower cases. But now cloud (without document) requires that SIP is written with upper cases. So it should not be a news that there is some space for the confusions =)


    Petri

    Friday, January 11, 2019 7:11 AM
  • Hi Petri,

    Yes, we also hope Microsoft will update the document about this in the near future.

    Best Regards,
    Evan Jiang


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    • Marked as answer by Petri X Friday, January 25, 2019 11:15 PM
    Tuesday, January 15, 2019 7:45 AM
  • Hi Petri,

    Is there any update for this issue? If the reply is helpful to you, please try to mark it as an answer, it will help others who have the similar issue.

    Best Regards,
    Evan Jiang


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Friday, January 18, 2019 6:55 AM