Export-CsConfiguration <folder path>
route add <rede address> mask <mascara of identificação> <IP gateway> if <identificação board <Network-p
thank you for all your work on Lync.
Are you very sure the internal edge interface HAS TO BE ABLE to directly communicate with the internal clients (and vice versa)?
I understand the internal edge interface communicates with the front end server (and then the front end server communicates with the internal clients).
In every tutorials i've seen about configuring the edge server, people set up a permanent static route so the internal edge interface can communicate with the front end server. But in the case the internal clients are in multiple ip subnets (that might be common in large organizations i guess, anyway it's our case), do we have to configure a static route to every subnet where we might have internal lync clients? (and so on the firewall rule)
I checked on our firewall, I found no packet log of clients trying to access directly the internal edge interface (and vice versa).
I'm asking this because our Lync system working well (internally and externally in all possible ways, with webApp, Attendee, we usee public certfs, etc). Except that we can't make audio/video/sharing working with a federated organization (but presence and IM are working!).
Our main log error message is following:
federated call failed to establish due to a media connectivity failure where both endpoints are internal
and we cannot figure what the problem does come from....
Hi, I'm glad to help.
The client must be enable to access the internal Edge Server Nic to prevent the error: social.technet.microsoft.com/.../7459.troubleshooting-limited-external-calling-in-lync-client.aspx
In your case I don't think that is the problem, for media sharing you should configure the ports
50,000-59,999: Media exchange, Application sharing/desktop sharing and File transfer
You can see a nice doc about this in the Lync portal
If this fails, open a thread on Lync Forum so we can help you.
Bye (sorry if my english is a little rought, still learning )
could you show me how to generation cerificate?
"Copy the certificate to the internal network and make the generation of the digital certificate in the certification. Copy the certificates to the final server Edge Server"
You can use this guide.
Fernando boa tarde;
Estou tendo um problema para publicar o meu Edge.
Quando eu termino todo o processo de configuração e vou realizar os testes por um cliente externo eu não consigo acessar por erro no DNS, em alguns passos do seu procedimento o meu ficava diferente, EX: na hora de fazer a solicitação do certificado aparecia o meu sip interno e não o externo.
O erro que ocorre no cliente justamente é o do id 3 source lync.
Meu domínio interno tem o nome diferente do externo.
Você tem alguma dica para me ajudar ?