Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

Unable to send messages to federated contacts

Posted on 2013-12-02
1
Medium Priority
?
598 Views
Last Modified: 2013-12-17
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
Comment
Question by:Adeste
1 Comment
 
LVL 24

Accepted Solution

by:
Mohammed Hamada earned 2000 total points
ID: 39697695
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

Featured Post

How to Use the Help Bell

Need to boost the visibility of your question for solutions? Use the Experts Exchange Help Bell to confirm priority levels and contact subject-matter experts for question attention.  Check out this how-to article for more information.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Yahoo Messenger is one of web's most popular free IM (Instant Messenger) services. Yahoo messenger is very popular with teens who like to use it everyday to be in contact with their friends and family members. It has become a part of the daily life …
Back in July, I blogged about how Microsoft's new server pricing model, combined with the end of the Small Business Server package, would result in significant cost increases for many small businesses (see SBS End of Life: Microsoft Punishes Small B…
The goal of the tutorial is to teach the user how to instant message and make a video call in Skype.
This lesson discusses how to use a Mainform + Subforms in Microsoft Access to find and enter data for payments on orders. The sample data comes from a custom shop that builds and sells movable storage structures that are delivered to your property. …
Suggested Courses

783 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question