Windows Server

JoeS · Guest

Currently my SIP URI's are requiring the following format:
myname@mydomain.com
I would like to be able to use
Firstname.lastname@emailaddress.com

Has anyone setup anything like this?

JoeS · Guest

Actually let me clarify
If I set the SIP URI to
first.last@emailaddress.com
When I hover over the contact in MOC - it reports
MYLOGINNAME@MYDOMAIN.COM
I want it to display
first.last@emailaddress.com
instead
Thoughts?

"JoeS" wrote:

Jeremy Buch · Guest

This isn't clear to me - what all are you setting up? If your SIP URI is
first.last@emailaddress.com, that is all that MOC will know about. Please
explain in detail what you are doing (or attach screenshots if possible to
clarify).

--
Jeremy Buch (Microsoft)

This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send email to this address, post a reply to this newsgroup.

"JoeS" <JoeS@discussions.microsoft.com> wrote in message
news:1017E375-C015-4C97-8B52-D47C43839C48@microsoft.com...

JoeS · Guest

Jeremy,
My LCS server is in the server.com domain. But my primary email addresses
are first.last@differentemailaddress.com domain. So MOC will not allow me to
use first.last@differentemailaddress.com domain since my LCS server is in
server.com domain. If I use first.last@differentemailaddress.com for the sip
uri, then I am forced to remove automatic configuration from MOC and specify
my LCSserver.server.com address.

I would like to use Automatic configuration in MOC and
first.last@differentemailaddress.com domain.

Joe

"Jeremy Buch" wrote:

Jeremy Buch · Guest

I don't understand how you login properly if you are using your email
address as the SIP URI. If the SIP URI isn't the same as your email
address, I am expecting that you will not be able to use your email address
during configuration.

Use of first.last@differentemailaddress.com won't be possible (for manual or
automatic) because it isn't the SIP URI. If the SIP URI matches the email
address, then you can use it and login fine. If you make the SIP URI the
same as the email address, you can still use automatic configuration to
login your client, but you'll need to publish a client port using a
certificate that is named based on the email address (and SIP URI) domain.

[SOLUTION]
server's actual FQDN: homeserver.server.com
- server needs port 5061 set up with a cert for homeserver.server.com
- set up port 443 (TLS) for clients with a certificate for
homeserver.differentemailaddress.com and then publish DNS SRV and A records
for TLS for this domain and server name to enable autoconfig using this
domain
- (if desired) set up port 5060 (TCP) for clients and then publish DNS SRV
and A records for TCP for this domain and server name to enable autoconfig
using this domain

Hopefully this helps clarify things. If you set up a pool, it gets to be
more involved, but you can publish the VIP with a name in the
differentemailaddress.com domain and then set up certs on all the servers on
the new port.

If you have multiple email address domains, then you are dealing with
multiple domain support - there are plenty of posts on this and the issues
associated with them - look for those (generally from me). Please also note
that if you have multiple domains, supporting outside users and dealing with
enhanced federation can become problematic.

--
Jeremy Buch (Microsoft)

This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send email to this address, post a reply to this newsgroup.

"JoeS" <JoeS@discussions.microsoft.com> wrote in message
news:8AB1B1AA-2796-4B66-9B1F-7614FDA15780@microsoft.com...

	Windows Server Forum Index -> Live Communications Server	All times are GMT
Page 1 of 1