3300 to Lync 2010 direct SIP trunks

[Waldosworld]

3300 MXeIII
MCD 5.0 (11.0.0.102)

Client originally started the programming the SIP link but on review had just match the example in the documentation so I deprogrammed the link and started from scratch.
Now have
system name mitel3300
domain name corp.companyname.com
dns entries are there 2 servers
network element Lync2010 other with FQDN lyncmed.companyname.com
sip peer transport TCP 5060
sip peer label Lync for network element Lync2010
the FQDN mitel3300.corp.companyname.com
The peer profile setting match the mitel documentation. 11-4940-00161_2

maintenance log
Fail to get IP for fqdn[lyncmed.companyname.com]
check DNS server.

Ping from 3300 using IP address or FQDN of Lync server OK.
Client configured the Lync server and DNS.

 

[wireman50]

Is it local DNS or out in the wild world. If its local could be a reverse dns problem or its not set up to resolve local names locally.....

 

[Waldosworld]

local DNS, will get the client to check
thanks

 

[Waldosworld]

client configured to resolve any reverse dns issues and the server is set up to resolve local names locally.
still no joy.

 

[Waldosworld]

Customer moved the Lync server to the same network as the 3300 and using IP address instead of a FQDN able to establish link. However the programming in the Lync option is FQDN only.
Anyone have this working with 5.0 and if so what SP, suspecting upgrade required as site is at 5.0 pre any release updates and documentation date is well after SP2 release.
Can ping from 3300 using the IP address or FQDN of Lync however as soon as you try to establish setup using FQDN it pooches.

 

[SXWizard]

Running vMCD to Lync for voicemail with SIP trunks and IP address not FQCN in SIP peer profile. vMCD is 5.0 SP2 PR 1.

 

[Waldosworld]

Thanks for the info SXWizard. Did you have to change any settings in the sip profile than using IP address to what is specified in the doc.?

 

[Waldosworld]

Update,
Issue resolved after upgrading to MCD 5.0 SP2 PR2