locked
PAP2T for analogue devices with Lync? RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    Has anyone successfully used a device like a Linksys PAP2T to provide Analogue lines for Lync?

    We have migrated from OCS 2007 R2 to Lync, and use a Cisco 2801 as our PSTN gateway.  We are still running our legacy VOIP PBX via the same router to look after analogue lines.  That PBX uses Linksys PAP2T's to provide the analogue connection.  I am trying to get the same device working with Lync, but with no success.

    The PAP2T appears to be dialing out correctly :

     Calling:663@lyncmediation.domain.com:5060
    [0:0]AUD ALLOC CALL (port=16472)
    [0:0]RTP Rx Up
    RSE_DEBUG: reference domain:lyncmediation.domain.com
    [0]SIP:ICMP Error -1 (a330149:5060, 3)
    RSE_DEBUG: getting alternate from domain:lyncmediation.domain.com
    [0:0]AUD Rel Call
    CC:Failed w/ Calling
    Sess Terminated

    but nothing appears in the Lync Mediation server logs.  By the same token Lync mediation logs appear to be sending the correct information to the correct IP, however nothing comes up in the PAP2T debug logs.

    From the Lync logs:

    $$END-MEDIATIONSERVER
    TL_INFO(TF_COMPONENT) [0]0EB4.112C::03/14/2011-03:53:14.255.00027e6c (MediationServer,MediaSessionAgent.NotifyMediaReceived:mediasessionagent.cs(5257))(00000000020784D1)$$START-MEDIATIONSERVER
    MediationCall: 5a65c369e89645e38accbebcc8d0a49a
    CallId: 916725d5bc0c4579997ced71c1f292dc
    From: sip:user@domain.com
    To: sip:f3193736-4e37-4b6f-b4d8-fee9881b7614@domain.com
    Direction: Outbound
    Start-Line:  Notifying application of first media received, reason: EarlyMediaReceived
    $$END-MEDIATIONSERVER
    TL_ERROR(TF_COMPONENT) [0]0EB4.112C::03/14/2011-03:53:16.469.00027e6d (MediationServer,GatewayCall.GatewayParticipateComplete:gatewaycall.cs(1838))(0000000001ED18C6)Cannot connect to gateway. SocketError: ConnectionRefused, Address 10.51.1.27
    TL_ERROR(TF_COMPONENT) [0]0EB4.112C::03/14/2011-03:53:16.497.00027e6e (MediationServer,GatewayCall.GatewayParticipateComplete:gatewaycall.cs(1853))(0000000001ED18C6)$$START-MEDIATIONSERVER
    MediationCall: 5a65c369e89645e38accbebcc8d0a49a
    CallId: 389585a2-e13f-4547-bd5c-d794882a32e2
    From: sip:+#######665;ext=665@lyncmediation.domain.com;user=phone
    To: sip:+#######663@10.51.1.27;user=phone
    Direction: Outbound
    Start-Line: Exception: Microsoft.Rtc.Signaling.ConnectionFailureException:Unable to establish a connection. ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 10.51.1.27:5060
       at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)
       at Microsoft.Rtc.Internal.Sip.TcpTransport.OnConnected(Object arg)

    Start-Line: Terminating Proxy side call with session state: Incoming, sip-response: 504, ms-diag: 10000, ms-diag reason: Gateway returned a SIP failure code.

     

     

    Monday, March 14, 2011 11:03 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    Turns out the PAP2T uses UDP for SIP and Lync uses TCP / TLS for SIP. 

    Got my analogue lines working by pointing the PAP2T at our Cisco 2801 router which has our PSTN lines going into it and can handle SIP as both TCP for Lync and UDP for the PAP2T.  I just use a voice dialplan on the Cisco to send traffic there and Lync is not aware of it at all.  Not ideal and not as easy to manage, particularly for normalisation, but atleast its working.

    • Marked as answer by James Bellaart Wednesday, March 16, 2011 9:03 PM
    Wednesday, March 16, 2011 9:01 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Which device is 10.51.1.27:5060?

    It refuses the connection.

    Technical Specialist Microsoft OCS/Lync & UC Voice Specialisation - http://www.uwictpartner.be
    If you think my post is the answer to your question, please mark it as answer so future visitors can easily find it.
    Wednesday, March 16, 2011 7:42 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    You should talk to mediation server TCP port 5068 - can you configure that in your device? Or you might consider using Cisco 2801 as a SIP B2BUA to translate between Lync and Linksys.
    Johann Deutinger | MCTS Exchange 2007/2010 / OCS 2007 | ucblog.deutinger.de
    Wednesday, March 16, 2011 11:02 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I also trying to use a FAX and a Wireless Phone over PAP2T to my Lync Mediation Server. But I can't connect it to the Lync Server. Always the same status on the Linksys PAP2T: Can't connect to login server. Which configuration settings you made on the PAP2T? I created a contact for the fax with the Lync Management Shell. Here my settings on Line 1 (FAX):

     

      Proxy: 10.46.58.47> Use Outbound Proxy: Yes
      Outbound Proxy: 10.46.58.47    
      Register: Yes    
      Register Expires: 60    
             
             
             
    Subscriber Information            
      Display Name: FAX User ID: fax_netree@netree.ch
      Password: don't have one Use Auth ID: Yes
      Auth ID: fax_netree@netree.ch    
         
           

     

    Wednesday, March 16, 2011 12:55 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Some Lync qualified gateways, such as our product, support usage of locally registered SIP devices like ATAs with analog ports.
    Johann Deutinger | MCTS Exchange 2007/2010 / OCS 2007 | ucblog.deutinger.de
    Wednesday, March 16, 2011 1:32 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Turns out the PAP2T uses UDP for SIP and Lync uses TCP / TLS for SIP. 

    Got my analogue lines working by pointing the PAP2T at our Cisco 2801 router which has our PSTN lines going into it and can handle SIP as both TCP for Lync and UDP for the PAP2T.  I just use a voice dialplan on the Cisco to send traffic there and Lync is not aware of it at all.  Not ideal and not as easy to manage, particularly for normalisation, but atleast its working.

    • Marked as answer by James Bellaart Wednesday, March 16, 2011 9:03 PM
    Wednesday, March 16, 2011 9:01 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    You can define your analog devices using Lync management shell (there is a post on that on my blog - see signature). Then you can direct all analog calls via your 2801 to Lync and it will take care of number normalization, policies and routing.
    Johann Deutinger | MCTS Exchange 2007/2010 / OCS 2007 | ucblog.deutinger.de
    • Proposed as answer by jwdberlin Thursday, March 17, 2011 8:57 AM
    Thursday, March 17, 2011 8:57 AM