Answered Lync Integration Direct SIP to Siemens

  • 2 พฤษภาคม 2554 11:27
     
     

    Has anyone had any luck with integrating Siemens Hipath to Lync with direct SIP. There was an integration for OCS does this mean it will work for Lync and it has just not gone through the approval process?

    Thank you

ตอบทั้งหมด

  • 3 พฤษภาคม 2554 23:38
     
     คำตอบที่เสนอ

    Yes - if direct SIP worked with OCS it will work with Lync.

    I don't know regarding the approval process...

    Regards

    Paul Adams

     


    pauladamsit.com
  • 5 พฤษภาคม 2554 2:08
    ผู้ดูแล
     
     

    Hi,

    You can refer this article in the section of the table "Supported Lync 2010 PBX Systems"

    http://www.agileit.com/Consulting/Unified-Communications/Pages/Microsoft-Lync-2010-OCS-VOIP-RTC-Consulting.aspx

    Regards,

    Sharon

     


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    • เสนอเป็นคำตอบโดย Sharon.ShenMicrosoft, Moderator 5 พฤษภาคม 2554 2:08
    • ยกเลิกการนำเสนอเป็นคำตอบโดย JelBoy 6 พฤษภาคม 2554 19:05
    •  
  • 6 พฤษภาคม 2554 19:05
     
     

    I was looking for some real world feedback. I know that if things worked under OCS they should under Lync however as the OIP did not just carry them over and I have heard stories of other PBXs not working the same between OCS and Lync I was looking for some positive feedback.

    The Agile IT link doesn't give a list of direct SIP  connections some of those PBXs listed don't even have SIP so the list will include VoIP gateway connected PBXs.

  • 8 พฤษภาคม 2554 16:53
     
     คำตอบ

    Compared to connection via fully tested and qualified gateways there are quite some areas where IP-PBXs have restrictions when connected directly via SIP. Some examples of possibly unsupported functions:

    • media bypass
    • comfort noise generation
    • REFER
    • call hold/transfer may not work in all situations
    • DNS load balancing
    • failover to secondary mediation server
    • RTCP protocol
    • early media
    • ringback tone

    ...and others. Examples can be found at http://technet.microsoft.com/en-us/lync/gg131938.aspx#tab=2

     


    Johann Deutinger | MCITP Lync 2010 | MCTS Exchange 2010, OCS | ucblog.deutinger.de | http://twitter.com/jwdberlin
    • เสนอเป็นคำตอบโดย jwdberlin 10 พฤษภาคม 2554 10:15
    • ทำเครื่องหมายเป็นคำตอบโดย JelBoy 13 พฤษภาคม 2554 15:25
    •  
  • 13 พฤษภาคม 2554 13:02
    ผู้ดูแล
     
     

    Hi,JelBoy,

    Please check if these links below meet your request

    http://technet.microsoft.com/en-us/lync/gg131938.aspx

    http://www.mitel.com/DocController?documentId=28140

    http://voipnorm.blogspot.com/2011/01/voice-migration-strategies-cucm-to-lync.html

     

    Regards,

    Sharon


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    • เสนอเป็นคำตอบโดย Sharon.ShenMicrosoft, Moderator 13 พฤษภาคม 2554 13:03
    • ยกเลิกการนำเสนอเป็นคำตอบโดย JelBoy 13 พฤษภาคม 2554 15:30
    •  
  • 13 พฤษภาคม 2554 13:43
     
     

    I'm currently evaluating the deployment of a Unified Communication solution for our company (SMB).

    Telcat, one of the major players in Germany (besides German Telekom T-Systems) when it comes to telecommunication, offered me a Siemens HiPath solution including Siemens UC solution called OpenScape. T-Systems basically offered me the same solution.

    Unfortunately none of these companies seemed to have much experience with Lync Server 2010 or no experience at all.

    Since there are basically no reports from the real world, the chance that I'm going to interconnect Siemens HiPath with Lync Server 2010 on my own risk is very little. So I have go with the OpenScape solution they offered me.

  • 13 พฤษภาคม 2554 15:29
     
     

    Hi Sharon

    There is nothing on any of those links on the Siemens integration so not help really.

    Thanks for looking

  • 13 พฤษภาคม 2554 15:32
     
     
    Despite lack of any detail we went ahead and connected Lync to the Siemens and at the moment everything appears to work but there is still a lot of testing to do. The Siemens engineer just created the trunk and after troubleshooting on both sides we were able to make calls. We did some limited testing and were happy with the results so far.
  • 13 พฤษภาคม 2554 23:15
     
     
    Great! Don't give up on Lync - it's a great product! If you find any problems you could contact me (I'm in Germany): johann at deutinger dot de.
    Johann Deutinger | MCITP Lync 2010 | MCTS Exchange 2010, OCS | ucblog.deutinger.de | http://twitter.com/jwdberlin
    • เสนอเป็นคำตอบโดย EDV Sprungbrett 18 พฤษภาคม 2554 7:18
    • ยกเลิกการนำเสนอเป็นคำตอบโดย EDV Sprungbrett 18 พฤษภาคม 2554 7:18
    •  
  • 14 พฤษภาคม 2554 8:36
     
     
    I'm not giving up on Lync, in fact the poor support and information from Siemens is a great selling point for Lync. Almost every other PBX vendor out there shares information on the integration in detail. With Siemens we are left in a cloud of confusion which is justification enough to senior management that the Siemens should be phased out and Lync be used instead.
  • 18 พฤษภาคม 2554 7:18
     
     

    I'm currently building a Lync lab, and I have arranged a meeting with a Siemens consultant today. I'm curios what he has to say about Lync integration with Siemens HiPath.

  • 20 พฤษภาคม 2554 8:44
     
     
    So, even though Siemens demonstrated HiPath + Lync in action at CeBit this year. The consultant told me Lync is currently not available for Siemens customers. So I have to go with Siemens OpenScape.
  • 20 พฤษภาคม 2554 8:46
     
     
    You could use a qualified gateway to connect Lync to Hipath. Some gateways can be installed between PSTN and PBX so nothing on the PBX needs to be changed in that case.
    Johann Deutinger | MCITP Lync 2010 | MCTS Exchange 2010, OCS | ucblog.deutinger.de | http://twitter.com/jwdberlin
  • 4 เมษายน 2555 5:55
     
     
    Despite lack of any detail we went ahead and connected Lync to the Siemens and at the moment everything appears to work but there is still a lot of testing to do. The Siemens engineer just created the trunk and after troubleshooting on both sides we were able to make calls. We did some limited testing and were happy with the results so far.

    Is there any key configuration points you might be able to share as I am going through the same exercise. It was apparently working at some stage by according to the Siemens guy but I cannot see anything wrong on the Lync side. I had a Wireshark session running and can see a connect is attempt from either the Siemens or Lync server but drops again. I cannot get much out of the Siemens guy as he says that from his side it is just a small configuration change. Odd thing is I am able to make Lync to Lync calls via number but that does not seem to go through the Siemens equipment.

    Is there any type of tracing one can do in cases like that to verify that the Lync side of things is set up properly?

  • 13 เมษายน 2555 9:51
     
     

    Hi Naraka

    You should start up Snooper (lync Server Logging Tool), on the mediation server and start the trace from there.

    it will give you a good indication of what's going on, and why the call fails. (could be a matter of Encryption not set to supported).

    There is a good introduction on snooper right here: http://blogs.technet.com/b/drrez/archive/2011/01/17/microsoft-lync-server-2010-resource-kit-tool-snooper.aspx

    is it a Direct SIP between the HiPath and the Mediation server, or do you have a Gateway in place ?

    Br

    Steffen

  • 20 เมษายน 2555 9:43
     
     คำตอบที่เสนอ

    Yes it works even if it is not "supported". We have install it from a Lync entreprise to Two Siemens PABX

    Rgds

    JMF

    • เสนอเป็นคำตอบโดย FRANCOIS Jean-Marc 20 เมษายน 2555 9:43
    •  
  • 21 เมษายน 2555 15:08
     
     
    Works is relative, I can put cheap tyres on my lamborghini drive it at 200mph but when the tyre explode and the car crashes no one is going to support me as I didn't use the proper approved tyres. Likewise Siemens seem to have no interest in their customers and are not providing a fully tested and approved solution. Other major manufacturers put their systems through the approval process but Siemens don't bother nor offer any support. Best route as I've discovered is as you've found get it up and running and but instead of looking at a coexistance stand solution, plan the removal of the Siemens asap.
  • 23 เมษายน 2555 14:54
     
     

    Our client is a company with more than 10000 users, has some Siemens PABX, Cisco Call Manager,...e nd they also use Lync for IM (everyone) and for Voice around 1000 users.

    The Sip trunk between Lync and Siemens is  working 100 % even if it is not supported.  The client took the decision to install like it because they can't just throw away the Siemens PABX....

  • 23 เมษายน 2555 15:16
     
     

    So for example tomorrow Lync voice through the Siemens stops working and you have 1000 users with no phones. Who do you get support from neither Microsoft or Siemens will support you, it is not a comfortable place to be in. How many days is acceptable to find a solution so those users can make a call again? Or is it how many hours?

    Siemens have left their customers exposed by not continuing support. If you intend to keep the Siemens running long term you need a gateway so they can support you should the link break. Alternatively if it is an acceptable risk for voice for 1000 users to be on an unsupported environment you are in an unusual position.

  • 25 เมษายน 2555 11:56
     
     

    What means support?

    I prefer to have an "unsupported" solution that works than a "supported" solution that doesn't work.

    If you always install solutions that are completely "supported" from A to Z you are lucky.  We speak here about a sip trunk between two environment , don't say me that this trunk will have issues one day and  will never work again...

  • 25 เมษายน 2555 18:35
     
     
    You are unlikely to have supported solutions that work, but quite likely to have unsupported solutions that stop work for some reason. I don't think this discussion is going anywhere useful for anyone, your final sentence I could just as easily respond to say can you guarantee you will never have any problems with the trunk. No one can say you will or will not have a problem I think experience shows we always get problems but sometimes you are lucky.
  • 27 เมษายน 2555 11:36
     
     

    Thanks for the reply and sorry for my late reply - the connection is a Direct SIP connection o the HiPath's module. I used however Wireshark to look at the SIP traffic between the Mediation/FE server and Hipath and notices that the number that is forwarded to the Hipath is in a format that it does not understand. Got it eventually right with the Trunk Translation rules.

    Also looks like we going to extend the pilot now to all the branches and also get Lync enabled phone devices. To date I have not found any concrete document on highlighting the shortcoming of running Lync 2010 with a HiPath 4000. Would this be a call to do a internal assessment (Local IT effort)before moving the whole project to full on production?

  • 7 พฤษภาคม 2555 14:03
     
     

    Can you please share the SIP configuration? We use a gateway solution that does not work so well all the time.

    Thank you

  • 7 พฤษภาคม 2555 14:04
     
     

    Can you please share the SIP configuration? We use a gateway solution that does not work so well all the time.

    Thank you

  • 28 พฤษภาคม 2555 8:06
     
     

    What SIP configuration exactly do you need? If it is from the HiPath then I cannot help immediately as it is out of my administrative control.

  • 4 กรกฎาคม 2555 11:01
     
     

    Hi

    Nice that you have installed Lync and connected with siemens. I have few questions....

    how did u Realize PICK UP Groups

    in Hipath 4000 we have pickup groups like when a call comes it will ring simultaneously to all the users who are in a Pickup group and if a call was to user A then  USER B also has the oppurtunity to takeover the call.

     Do you have any idea and can you please give me some tipps.


    thanks

  • 11 มีนาคม 2556 12:19
     
     
    Hello, Is there any doc or a guide on how to configure Siemens Hipath / HG 1500 to connect to Lync 2010/2013 using SIP trunk?
    Many thanks
  • 16 มีนาคม 2556 8:05
     
     

    Hi,

    Okay, despite lack of documentation I decided to go trying to implement that..

    My environment is: Lync 2013, Siemens Hipath 3800 V7 H3K_V7_R6.9.0_14 and HG1500 V7 SAPP HI-G15.75.004.S

    Configuring Lync side is relatively easy, PSTN gateway, routes, dial plan, etc.

    I configured the HG1500 in the 'Voice Gateway' panel with new node is Lync IP address, LAN Trunking protocol is Native SIP. Then creatin new Routing with the first digest of my Lync extensions. From my understanding this is all needed to accept call from Lync to Siemens Hipath extensions.

    Unfortunately, when I make a call from lync client to hipath extension, it does not ring in the phone and when I enabled tracing in HG1500 I got the following errors:

    (EVTLOG tEvtLogTask 0x2f1ecf8 "03/16/2013 08:21:06.736175" cevtlogsvc01.cpp 932)
    EventLogEntry from SIP_SA (SipEngine "03/16/2013 08:21:06.735503" CSipSessionMgr.cpp 1341):
      EventType: Information
      EventCode: SIP_INVALID_PARAMETER_VALUE
      EventText: Username lenght 0!

    FYI, I configured SIP trunking successufully between Lync <-> Asterisk and also Asterisk <-> Hipath but I m stuck for Lync <-> Hipath.

    Any help is really appreciated.

    Cheers,