Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 630
  • Last Modified:

Unable to send messages to federated contacts

We're deploying a Lync 2013 server and we're not able to send IM's to federated contacts. I just finished setting up the edge pool and I started getting these event logs when a contact attempts to send a message to an external contact.

Some requests were rejected as they exhausted the Max-Forwards limit.

In the past 15 minutes, the protocol stack rejected 101 requests that were looping and exhausted the Max-Forwards limit. The last one was this SIP message:

Trace-Correlation-Id: 2197823020
Instance-Id: 3EC36
Direction: incoming
Source: NT-LYNC01.Domain.local
Message-Type: request
REGISTER sip:Domain.local SIP/2.0
Start-Line: REGISTER sip:Domain.local SIP/2.0
From: "Audio Test Service"<sip:RtcApplication-7d4bf173-d1b1-4a0b-b834-ae314d5863d8@Domain.local>;epid=8E60123C6E;tag=5b8c9c047
TO: <sip:RtcApplication-7d4bf173-d1b1-4a0b-b834-ae314d5863d8@Domain.local>
CALL-ID: c52cecd4f9824bb689eb6ce5c5a7b77d
CSEQ: 21933 REGISTER
CONTACT: <sip:NT-LYNC01.Domain.local:5076;transport=Tls;ms-opaque=9bc3ed97e7ab50b6>;methods="Service,Notify,Benotify,Message,Info,Options,Invite";+sip.instance="<urn:uuid:41bad8c1-cbf5-5f91-bf7e-1061c74f37da>";automata;actor="attendant";text;audio;video;image
Via: SIP/2.0/TLS 10.0.1.16:49314;branch=z9hG4bKF842158A.B52389422040B1D6;branched=FALSE;ms-received-port=49314;ms-received-cid=B33000
Via: SIP/2.0/TLS 10.0.1.16:49314;branch=z9hG4bK6F35057E.B57D1682203FB1D6;branched=FALSE;ms-received-port=49314;ms-received-cid=B33000
Via: SIP/2.0/TLS 10.0.1.16:49314;branch=z9hG4bKA5AA6962.AF2A6498203EB1D6;branched=FALSE;ms-received-port=49314;ms-received-cid=B33000
Via: SIP/2.0/TLS 10.0.1.16:49314;branch=z9hG4bK2DECFFAD.CA4D4B37201A91D5;branched=FALSE;ms-received-port=49314;ms-received-cid=B33000
Via: SIP/2.0/TLS 10.0.1.16:49314;branch=z9hG4bK64876477.20D06BBA2019A1D5;branched=FALSE;ms-received-port=49314;ms-received-cid=B33000
Via: SIP/2.0/TLS 10.0.1.16:49314;branch=z9hG4bKF523F898.45137C922019A1D5;branched=FALSE;ms-received-port=49314;ms-received-cid=B33000
Via: SIP/2.0/TLS 10.0.1.16:49314;branch=z9hG4bK34E7D2C8.7D816B702018A1D5;branched=FALSE;ms-received-port=49314;ms-received-cid=B33000
Via: SIP/2.0/TLS 10.0.1.16:49817;branch=z9hG4bK57a33258;ms-received-port=49817;ms-received-cid=B37300
Record-Route: <sip:NT-LYNC01.Domain.local:5061;transport=tls;lr>;tag=7570FE2E7245D9F53110AE3BDE221B76
Record-Route: <sip:NT-LYNC01.Domain.local:5061;transport=tls;lr>;tag=7570FE2E7245D9F53110AE3BDE221B76
Record-Route: <sip:NT-LYNC01.Domain.local:5061;transport=tls;lr>;tag=7570FE2E7245D9F53110AE3BDE221B76
Record-Route: <sip:NT-LYNC01.Domain.local:5061;transport=tls;lr>;tag=7570FE2E7245D9F53110AE3BDE221B76
Record-Route: <sip:NT-LYNC01.Domain.local:5061;transport=tls;lr>;tag=7570FE2E7245D9F53110AE3BDE221B76
Record-Route: <sip:NT-LYNC01.Domain.local:5061;transport=tls;lr>;tag=7570FE2E7245D9F53110AE3BDE221B76
Record-Route: <sip:NT-LYNC01.Domain.local:5061;transport=tls;lr>;tag=7570FE2E7245D9F53110AE3BDE221B76
Record-Route: <sip:NT-LYNC01.Domain.local:5061;transport=tls;lr>;tag=7570FE2E7245D9F53110AE3BDE221B76
Record-Route: <sip:NT-LYNC01.Domain.local:5061;transport=tls;opaque=state:T;lr>;tag=7570FE2E7245D9F53110AE3BDE221B76
Max-Forwards: 0
CONTENT-LENGTH: 0


Cause: This usually indicates an incorrect server configuration or a bad routing rule.
Resolution:
None needed unless the number of reported errors is large (> 100). This usually indicates an incorrect server configuration or a bad routing rule. Check whether all server routing rules are properly configured.

Any idea how I can fix this bad route?
0
Adeste
Asked:
Adeste
1 Solution
 
Mohammed HamadaSenior IT ConsultantCommented:
Please, answer these questions!

1- Have you deployed the public certificate on Edge server?
2- Have you enabled firewall required ports?
3- Did you add Lync Frontend FQDN and Active directory host name to the Host files in Edge server and vice versa in Front end for the edge with the internal NIC IP ?
You can try to ping Front end from Edge and Edge from Front end to see if it's connecting.
4- have you added the Certification authority certificate to the Edge server ?
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now