Output of sipxproc got lost, sorry.
Here it is:
# sipxproc
{"FreeSWITCH"=>"Disabled",
"sipXmrtg"=>"Disabled",
"SIPRegistrar"=>"Disabled",
"ParkServer"=>"Disabled",
"ConfigAgent"=>"Disabled",
"CallResolver"=>"Disabled",
"ACDServer"=>"Disabled",
"SIPStatus"=>"Disabled",
"ConfigServer"=>"Disabled",
"CallResolver-Agent"=>"Disabled",
"SipXbridge"=>"Disabled",
"MediaServer"=>"Disabled",
"sipXivr"=>"Disabled",
"PageServer"=>"Disabled",
"PresenceServer"=>"Disabled",
"ResourceListServer"=>"Disabled",
"SipXrelay"=>"Disabled",
"SIPXProxy"=>"Disabled"}
René
2009/7/7 Rene Pankratz <[email protected]>
> Hello list members,
> as I installed today from the current stable ISO
> (sipfoundry-4.0.1-015823-i386.iso) I ran again into the same issiu when
> setting up a distributed Server. So I post again on this thread.
>
> Same problem as before:
> - I Installed master
> - Added distributed server to config
> - Installed distributed server
>
> And this time again the distributed server shows all services in disabled
> state.
>
> I attached output of spixproc in distributed server and sipxconfig.log on
> master.
>
> René
>
> 2009/5/3 Rene Pankratz <[email protected]>
>
> As I needed a running system I just tried an update to unstable
>> (4.1.0-015335) , which solved the problem.
>>
>> The SIP domain was the fully qualified hostname in our DNS but i had also
>> added some aliases before adding the second server. Two of these aliases are
>> the IPs of Master and Slave, so that these aliases do not point to both
>> servers.
>> But as I read http://track.sipfoundry.org/browse/XX-5606 that does not
>> exactly match to that issue I think?
>>
>> I added the sipxconfig.log from master server. I hope the log is still
>> useful after the update process.
>>
>> René
>>
>> 2009/4/30 Scott Lawrence <[email protected]>
>>
>>> On Thu, 2009-04-30 at 02:33 +0000, James R wrote:
>>> > David Saint <dsaint <at> nortel.com> writes:
>>> >
>>> > > Does your secondary server status show "Registered"?
>>> > >
>>> > > Also you will have to re-run sipxecs-setup on the secondary server
>>> > > if the certificates have been changed on the primary server.
>>> > >
>>> > > Dave.
>>> > >
>>> >
>>> >
>>> > I have the exact same problem except my secondary server is Call Center
>>> role
>>> > only. Both of my servers (primary and secondary) show "registered".
>>> I've
>>> > tried rebooting & restarting both boxes.
>>>
>>> You may be hitting this:
>>>
>>> http://track.sipfoundry.org/browse/XX-5606
>>>
>>> is your SIP domain the same as the fully qualified host name? If not,
>>> the ACD bug above is going to keep it from working
>>>
>>> _______________________________________________
>>> sipx-users mailing list
>>> [email protected]
>>> List Archive: http://list.sipfoundry.org/archive/sipx-users
>>> Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
>>>
>>
>>
>
_______________________________________________
sipx-users mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
sipXecs IP PBX -- http://www.sipfoundry.org/