[cisco-voip] CUMA managed server wont start

[Dane Newman]

perfect thanks a ton once again Ryan

On Thu, Dec 3, 2009 at 12:57 PM, Ryan Ratliff <rratliff at cisco.com> wrote:

> The name should be the external ASA name.  It doesn't have to resolve to
> something with IP connectivity from CUMA, as long as it resolves.
>
>  -Ryan
>
>  On Dec 3, 2009, at 12:44 PM, Dane Newman wrote:
>
> Yup Ryan you rock that's what it was...I had the proxy host name configured
> to something that didn't resolve the way my dns was setup.   Let me ask you
> should the proxy host name resolve the the rfc 1918 address or the public
> address from the cuma server point of view?
>
> Dane
>
> On Thu, Dec 3, 2009 at 12:36 PM, Ryan Ratliff <rratliff at cisco.com> wrote:
>
>> Did you really name your CUMA server localhost?
>>
>> The only time I've seen that before is with CUCM servers when you enable
>> DHCP on the server and it can't pull a hostname from DNS or the DHCP server.
>>  The platform will set localhost to the hostname and this breaks all kinds
>> of things.
>>
>> The most common cause of the managed service not starting is that the
>> "Proxy Host Name" won't resolve via DNS.  Check System Management->Network
>> Properties.
>>
>> -Ryan
>>
>> On Dec 3, 2009, at 12:28 PM, Dane Newman wrote:
>>
>> As shown in the screen shot the managed server service wont start up.  I
>> have went through each of the enterprise adapters and verified each one is
>> working correctly with the test button.  I have even tried deleting them to
>> get it to come up but it refuses to come up.   Does anyone have any advice?
>>
>> Dane
>> <start.jpg>_______________________________________________
>> cisco-voip mailing list
>> cisco-voip at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20091203/5efbe8f5/attachment.html>