XMPP to gmail - Accept invitations

All Replies

• Friday, September 09, 2011 3:04 AM

  Moderator

   

   
  

  0

  Hi Vindryn,

  I suggest you to test connectivity by using the XMPP gateway console.

  To test SIP connectivity from the Microsoft Management Console (MMC):

  1.        In the left pane, click SIP Configuration.

  2.        Click the Validate Connection tab.

  3.        Select your SIP domain in the list next to Allowed Domain. This will test a SIP over TLS connection from your XMPP gateway to your Edge Server.

  Next, test the XMPP connectivity to the federated XMPP domain:

  1.        In the left pane, click XMPP configuration.

  2.        Click the Validate Connection tab.

  3.        Select the XMPP domain in the list next to Allowed Domain. This will test XMPP connectivity from your XMPP gateway to the federated XMPP domain.

  If you run into issues, see the “Troubleshooting” and “Additional Resources” sections in Interoperability with XMPP Systems Using the XMPP. Hope helps.

  • Reply
  • Quote

   
• Friday, September 09, 2011 6:10 AM

   

   
  

  0

  Hi Noya,

  Thanks for your answer.

  I already test both as the first step of my troubleshooting. Both results are fine : 

  "The Connection to 'domain.com' was successful"
  -------
  The Connection to 'xmpp-server.l.google.com' was successful
  The Connection to 'alt1.xmpp-server.l.google.com' was successful
  The Connection to 'alt2.xmpp-server.l.google.com' was successful
  The Connection to 'alt3.xmpp-server.l.google.com' was successful
  The Connection to 'alt4.xmpp-server.l.google.com' was successful

   

   

  The XMPP server seems to be fine, I just have some routing problem with the Edge. If a gmail user try to initiate the connexion, by sending me an IM, the connection fail.

  It seems that it is a problem with the routing on the Edge server :

  ( 0000000003FD5770 ) routedByApplication [0x00000000(false)], routeHeadersValidated [0x00000000(false)], sourceTrusted [0x00000000(false)]. TrustedForRouting = 0x00000000(false)
  *******************
  ( 3195726454 )( 0000000003FD5770 ) Exit - untrusted request that is ineligible for static routing. Returned 0xC3E93C5E(SIPPROXY_E_ROUTING)
  *******************
  $$begin_record
  LogType: diagnostic
  Severity: warning
  Text: Non-trusted source with a request URI that is not eligible for static routing
  Result-Code: 0xc3e93c5e SIPPROXY_E_ROUTING
  SIP-Start-Line: INVITE sip:localuser@domain.com:5061;maddr=lync-edge.domain.local;transport=Tls SIP/2.0
  SIP-Call-ID: f8aa6a28ae7c4412ac76a1da675e87b9
  SIP-CSeq: 55 INVITE
  Data: destination="sip:localuser@domain.com:5061;maddr=lync-edge.domain.local;transport=Tls";user="localuser@domain.com"
  $$end_record

  **********************
  ( 3195726454 )( 00000000035E7F58 ) Exit - failed to route the Request-URI. Returned 0xC3E93C5E(SIPPROXY_E_ROUTING)

   

  on the XMPP : 
  TL_INFO(TF_PROTOCOL) [0]07F8.09E0::09/08/2011-12:58:48.687.00000927 (S4,SipMessage.DataLoggingHelper:58.idx(581))
  <<<<<<<<<<<<Incoming SipMessage c=[<SipTlsConnection_342C81C>], 192.168.111.92:49273<-192.168.111.91:5061
  SIP/2.0 504 Server time-out
  FROM: <sip:xxxxxxxx@gmail.com>;tag=66fe429675
  TO: <sip:localuser@domain.com>;tag=1720B7781DAB53014AA9C0AA782D5D5E
  CSEQ: 55 INVITE

   

   

  I have these errors each time a user from gmail try to initialise the connection. If I send a message to gmail from Lync and the gmail user answer this is fine.

  
  
  

  • Edited by Vindryn Friday, September 09, 2011 6:11 AM
  •  
  • Reply
  • Quote

   
• Tuesday, September 13, 2011 8:28 PM

   

   
  

  0
  I am having this exact same issue, would be very interested in an answer as well
  • Reply
  • Quote

   
• Wednesday, September 14, 2011 8:41 AM

   

   
  

  0

  Vyndryn,

  
  >> Make sure you have following SRV record created correctly
  _xmpp-server._tcp.<domain>.com

  You can test that as follows

  C:\nslookup
  > Server 4.2.2.2
  > set type=srv
  > _xmpp-server._tcp.<sip-domain>

  The Result should look as follwos

  Server:  [4.2.2.2]
  Address:  4.2.2.2
  Non-authoritative answer:
  _xmpp-server._tcp.<sip-domain>     SRV service location:
            priority       = 20
            weight         = 0
            port           = 5269
            svr hostname   = xmpp-server.<sip-domain>

  >> If the Srv record is correct then
     take a Network Monitor Trace.

     Please note Google and Jabber XCP 5.4 uses TCP dialback for federation with XMPP servers.

  http://technet.microsoft.com/en-us/library/ff394138.aspx
  http://www.ietf.org/rfc/rfc3920.txt

   

  -Sanotsh

  ---

  Microsoft Unified Communications Team
  • Reply
  • Quote

   
• Wednesday, September 14, 2011 2:26 PM

   

   
  

  0

  Hi,

  All that results seems to be fine.

  I am actually dealing with Microsoft to fix the issue. It seems to be a problem with the certificate. On the "CAPI" event log of the Edge there is some error messages about the CN name that diffear from the name sent.

  I will keep you in touch when the problem is solved.

  • Reply
  • Quote

   
• Wednesday, September 14, 2011 2:34 PM

   

   
  

  0

  Hi,

  All that results seems to be fine.

  I am actually dealing with Microsoft to fix the issue. It seems to be a problem with the certificate. On the "CAPI" event log of the Edge there is some error messages about the CN name that diffear from the name sent.

  I will keep you in touch when the problem is solved.

  • Reply
  • Quote

   
• Thursday, September 15, 2011 10:30 PM

   

   
  

  0

  Vindryn,

  I worked with Microsoft as well and got my issue resolved. 

  In the event viewer on the XMPP gateway i was getting an error is the system log that the certificate could not be trusted from the sender.  After having Microsoft look at it we had to Export from our Lync Edge Server our Geo Trust Global CA cert, the intermediate GeoTrust cert and our Internal CA cert, our public certs for Lync were issued by Geotrust.  We then imported them on the XMPP gateway into the appropriate location. 

  Those errors immediately stopped.  We then verified the connectivity and then pointed out the the XMPP server needs to hit the Edge Server sip address.  in our case it was Sip.<domain name>.com and we just added a hosts entry to point to the DMZ interface of the Edge Server.  We restarted the Services and all is working now.

  hope this info is somewhat helpful

  • Marked As Answer by Vindryn Friday, September 16, 2011 11:44 AM
  •  
  • Reply
  • Quote

   
• Friday, September 16, 2011 11:44 AM

   

   
  

  0

  Hello,

  Yesterday our DC that was hosting the certification authority crashed. The Lync certificates and XMPP certificates was generated from that authority.

  I installed a new certificate authority and re-created my lync certificates. It seems that was not the issue.

  The issue was the configuration of the OCS XMPP Gateway. The Host Name of the Edge Server used in the SIP configuration was "lync-edge.domain.local" and I changed it by "sip.domain.com", the XMPP work fine now.

  The FQDN "lync-edge.domain.local" is related to the internal network of the edge server and the XMPP gateway was trying to talk to the External network of the Edge with the internal name.

  Thanks for your help :)

  • Marked As Answer by Vindryn Friday, September 16, 2011 11:44 AM
  •  
  • Reply
  • Quote