Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
SIP Trunking - OCS Supported Providers (ITSP) RRS feed

 > 

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote
    What you are saying is impossible.
    Mediation Server configuration resides in Active Directory so that would be almost impossible for any service provider to integrate with
    Mediation server also translates RT-Audio and other codecs into G7.11
    - Belgian Unified Communications Community : http://www.pro-exchange.be -
    Tuesday, September 1, 2009 12:02 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    Mediation server is a requirement!
    - Belgian Unified Communications Community : http://www.pro-exchange.be -
    Thursday, August 20, 2009 8:38 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    hi
    Agree with Deli. You can learn about the Sip Trunking Topology for your deployment refer to below link:
    http://technet.microsoft.com/en-us/office/dd425087(office.13).aspx 

    Sorry about i do not know which itsp vendors support the connection with your mediation server role.
    But, i think it is supported by most ITSP normally.

    Regards!
    Sunday, August 23, 2009 3:11 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Okay, I am trying to fully grasp the full requirement to run OCS Standard version on a network. My thoughts are that all of OCS 2007 R2 services will fit and run well on a single hardware configuration including the media server that talks to third-party voip or ITSP via SIP. If not, can someone please explain why the mediation server may require its own separate hardware (although I know voice less tolerant of latency but many voice solutions out there have everything integrated including the media server with no issues). 

    Okay, so I know I need OCS 2007 R2 and CALs, Windows 2003 Server, and one set of 64-bit hardware to run all OCS components including coomunicating with VoIP/PSTN solutions. I will appreciate if someone can clarify if I need anything else, perhaps separate mediation server stuff.
    Wednesday, August 26, 2009 6:58 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    The easiest response to having a separate Mediation server is that it's the only supported configuration.

    The technical reason why has more to do with how OCS communicates with the Mediation server. Port 5061 is used by both independent systems. If it was collocated it wouldn't be able to use the same port on the same system.

    From my observations about "load" on the Mediation server in a voice deployment, it's less about performance and more about how the software is designed.

    If you want a fully built out Enterprise Voice infrastructure the best place to get this information is TechNet: http://technet.microsoft.com/en-ca/library/dd441292(office.13).aspx. This link will give you all the necessary information about what you need for the various deployment scenarios.

    My advice is to stick with the supported topologies. :)

    ______________________________ MCITP: EA, MCTS: OCS, MCSE, CCA: NetScaler Long View Systems (www.lvs1.com) Infrastructure Architect
    Wednesday, August 26, 2009 8:08 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thanx for the response. So there is no choice other than to implement OCS 2007 R2 Standard and a Mediation Server on at least two separate 64-bit hardware? Sounds like a pretty expensive venture. 

    By the way, where does this "Mediation Server" come from, where does one get it? Does it come bundled on OCS 2007 Standard R2 CDs/DVDs?
    Also, what SIP handsets for users' desks are compatible with OCS 2007 Standard R2 (I'm assuming any SIP handset will do or is there any way at all to register SIP handsets)?
    • Edited by techiegz Wednesday, August 26, 2009 8:45 PM
    Wednesday, August 26, 2009 8:30 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    You can install a mediation server from the OCS 2007 Standard DVD, and or enterprise. as far as SIP phones OCS does not support many of the standard sip phones. snom, and polycom, and nortel all make phones that can be used with OCS
    Mitch Roberson |MCITP:Enterprise Server Admin, Messaging |MCTS:OCS with Voice Achievement |MCT
    Wednesday, August 26, 2009 10:19 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I recall the phones by the manufacturers you mention but they are so expensive and I am unsure what other Snom phones are OCS-compatible other than Snom 870 and MeetingPoint. Nothing about Snom 820 mentions OCS-compatibility. Do you have any ideas about it?
    Thursday, August 27, 2009 1:22 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    SNOM also has sub 100$ phones like the 320 up to the 370.
    The 820 and 870 should also be compatible with OCS

    You need to load different firmware than the standard firmware.  It's OCS specific firmware

    Check out this link
    http://www.snom.com/products/unified-communications/microsoft-ocs/snom-ocs-edition-at-a-glance/
    - Belgian Unified Communications Community : http://www.pro-exchange.be -
    Thursday, August 27, 2009 10:49 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thank you all for responding to this thread. All started when I read this (see bullet 8 at http://technet.microsoft.com/en-us/office/dd441250(office.13).aspx?ppud=4): "With Office Communications Server 2007 R2, you can use SIP trunking instead. SIP trunking allows your IP network to transmit voice data that used to be carried over standard phone lines. People on your Enterprise Voice network will be able to call people on the regular old telephone network (the so-called Public Switched Telephone Network, or PSTN), and people on the PSTN network will be able to call people on your Enterprise Voice network. That's nice, but the cool thing is that it does all this without requiring additional hardware like IP-to-PSTN gateways or Mediation Servers. Instead, all you need is an account with a SIP trunking service provider." If a mediation server is indispensible, this Microsoft statement “…all this without requiring additional hardware like IP-to-PSTN gateways or Mediation Servers” is at least misleading. How can one consider the OCS R2 system, if it is accompanied inaccurate documentation? Could somebody from Microsoft respond with a clarification?
    Thursday, August 27, 2009 5:45 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    @Deli Pro-Exchange, according to my research, only Snom 870, 820, and MeetingPoint offer OCS compatibility. The others are open-standard SIP and too ugly. Who can blame the manufacturers for not using SIP sometimes, it seems SIP cannot handle the tight integration of the various features they put together so they opt for proprietary protocols for endpoints while only using SIP external applications.

    @ JohnSeven, I'm sure they meant that "if you intend to go pure VoIP" otherwise they know that those well-versed in telephony know that no matter the product if you want to go analog, TDM, hybrid, or anything other than pure VoIP you need either a gateway or an interface card if the gateway software is already inbuilt. I also think I saw that Microsoft has some Dialogic and other manufacturer gateway products, so I will not necessarily interpret that statement as you have.
    Thursday, August 27, 2009 10:09 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Sorry but we are using the SNOM 320 and 370 with OCS so they definately work with OCS specific firmware
    Presence for these phones works great and they also support ICE so you can even use them over the internet althow they only use the G7.11 codec not the RT-Audio codec

    Wether they are ugly or not is a personal issue, but they are very cheap to use with OCS for users who only want a phone!
    - Belgian Unified Communications Community : http://www.pro-exchange.be -
    Thursday, August 27, 2009 11:19 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello JohnKSeven,

    I also read the bullet number 8 you are referring to, and find it confusing as well, also look at page 17 of the OCS R2 Resource kit under "SIP Trunking":

    "This capability, a variety of what is known in the telecommunications industry as SIP trunking, enables enterprises to not deploy Internet Protocol (IP)-PSTN gateways, with or without Mediation Servers, to enable PSTN connectivity."

    But as  far as I understad you will always need the Microsoft mediation server on the OCS side, even if some service providers now offer "OCS compliant SIP trunking".

    /mk

     

    Friday, August 28, 2009 8:53 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    @ Deli Pro-Exchange, When I checked the details for other Snom phones other than the 820, 870, and MeetingPoint, there was no information about OCS. Even in the firmware downloads page they did not make mention of OCS-compliance but did with the 820, 870, and MeetingPoint so I assumed they do not support it. They really should make this clear.

    @ JohnKSeven, Sincerely I don't know ahy Microsoft decided to design this solution the way they did with tons of confusion for everyone. And to make things worse, there are really no clear cut details from Microsoft but extremely lengthy literature that easily discourages anyone that may be doing a quick research on requirement and deployment options and how-to @ http://technet.microsoft.com/en-ca/library/dd441292(office.13).aspx . As a result, I'm trying to create a solution proposal with OCS and I don't even know where to start. WTF.
    • Edited by techiegz Friday, August 28, 2009 3:03 PM
    Friday, August 28, 2009 3:00 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thank you for your input techiegz and Kressmark. Look, all I want is to build scalable apps for OCS requiring just one 64-bit server. Why is it so difficult?

    If OCS R2 talks over the SIP/CSTA layer, and the mediation server translates it to SIP, there should be two ways of eliminating the mediation server: one, offer an option in OCS to communicate by SIP (no CSTA), two, have VOIP Internet providers support SIP/CSTA. I’m under an impression that Microsoft was hoping for the latter (VOIP providers doing mediation on their side), but no such providers have emerged as of yet. New standards for CSTA XML over SIP were recently approved (uaCSTA) and maybe now we’ll see the mediation service provided on the Internet. All of this is purely speculative and conjectural on my part, and one way to abate the frustration would be for Microsoft to just say it as it is.

    Friday, August 28, 2009 4:25 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    What you are saying is impossible.
    Mediation Server configuration resides in Active Directory so that would be almost impossible for any service provider to integrate with
    Mediation server also translates RT-Audio and other codecs into G7.11
    - Belgian Unified Communications Community : http://www.pro-exchange.be -
    Tuesday, September 1, 2009 12:02 PM