<

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x

Microsoft LYNC with HP/H3c gateway

Published on
9,741 Points
3,641 Views
1 Endorsement
Last Modified:
Approved
There are no good configuration guides for HP-H3C router to LYNC on the web. :(

Big statement, but we havent been able to find one yet. We did find the following document useful, but the information was not enough to use H3C router for use as a LYNC gateway: https://devconnect.avaya.com/public/download/dyn/HP_MSR-30.pdf

We tested in our LAB, and it is working, here are the settings that you need:

Firstly you need to enable dns


 dns proxy enable
 dns server x.x.x.x
 dns domain fabrikam.com

Open in new window


If you not enabling DNS the incoming calls dropping from LYNC server.

Secondly make VOICE setup:



voice-setup
 cptone country-type HU
 sip
  source-bind signal ipv4 x.x.x.x
  source-bind media ipv4 x.x.x.x
  sip-domain fabrikam.com
 #
 sip-server
  #
  call-rule-set
  #
  call-route 
  #
 dial-program
  default entity fax protocol standard-t38
  default entity fax protocol standard-t38 hb-redundancy 0
  default entity fax protocol standard-t38 lb-redundancy 0
  terminator 
#
  entity 10002 pots
   line 4/0:15
   undo register-number
   send-number all
   description call for ISDN
   match-template .T
   outband nte
   no shutdown
   undo vad-on
   compression 1st-level  g711alaw
   compression 2nd-level  g711ulaw
 #
  entity 10003 voip
   address sip ip 10.10.10.1 port 5068
   transport tcp
   codec transparent
   url sip
   fax baudrate disable
   description inside umbers
   match-template 4...
   outband nte
   undo vad-on
   compression 1st-level  g711alaw
   compression 2nd-level  g711ulaw
  #

Open in new window


Lync working only with RTP NTE DTMF relay, so need to send the calling number via RTP packets. For outbound calls need to configure 'send-number all' command. In the lync we not using +164 numbers.

Most important thing, that you need to protect your device from hackers, you need to put behind a firewall the gateway or need to create access-list for voice devices.

acl number 3101
 rule 100 permit ip source 10.160.114.0 0.0.0.255
 rule 150 deny ip

interface Ethernet0/1
 firewall packet-filter 3001 inbound

Open in new window



If you have any problem with the ISDN you able to debug:
debug isdn q921
debug isdn q931

more informations about ISDN Switch Types, Codes, and Values please refer http://docstore.mik.ua/univercd/cc/td/doc/product/software/ios100/dcr/36305.htm
http://www.h3c.com/portal/products___solutions/technology/wan/technology_introduction/200701/195640_57_0.htm


If you have any problem with the SIP you able to debug:
debug voice sip all
debug voice ccm all

Useful if you mirroring the port of the router and capture the SIP packets, it gives more informations about the problem. For capture data we use wireshark: http://www.youtube.com/watch?v=4joaL0Pks1Q
It is possible to debug in the LYNC server for SIP errors, the LYNC server logging tools installed default, for more informations please refer this page:
http://www.misdivision.com/blog/using-the-lync-logging-tool-to-debug-sip-issues


If you want to view on-line the log you need:
terminal debugging
terminal monitor

TLS and SRTP not working at the latest image.

More informations about H3c voice gateways:
http://www.basis-net.ru/index.php?option=com_content&task=view&id=219&Itemid=218

Here is the lync site where you find the Microsoft certified gateway list:
http://technet.microsoft.com/en-us/lync/gg131938.aspx
1
Comment
0 Comments

Featured Post

Exploring SharePoint 2016

Explore SharePoint 2016, the web-based, collaborative platform that integrates with Microsoft Office to provide intranets, secure document management, and collaboration so you can develop your online and offline capabilities.

Join & Write a Comment

Check How effective MS Exchange Expert thinks Exchange Mailbox Recovery by SysTools IS. Visit the Official site to get detailed information:- https://www.systoolsgroup.com/exchange-recovery.html (https://www.systoolsgroup.com/exchange-recovery.h…
There are many cases found where ScanPST.exe fails to repair corrupt Outlook PST File. When user tries to repair PST using Inbox Repair tool and it throws below error: •      Inbox Repair tool does not recognize the file •      ScanPST.exe hangs in betwee…

Keep in touch with Experts Exchange

Tech news and trends delivered to your inbox every month