Scott Lawrence wrote:
> On Wed, 2009-04-01 at 13:17 -0400, M. Ranganathan wrote:
>>>> Send Profile to the HA server from sipxconfig. As discussed on #sipx,
>>>> I think we may want to rework it so that step is not necessary (
>>>> confused the daylights out of me ).
>>> Be more explicit... rework _what_ so that _what_ step is not necessary?
>>>
>>> If the version number is not set (which what matches your symptoms),
>>> then it's because something is _broken_.  We need to figure out what
>>> that something is and fix it.
>>>
>>>
>> Sorry. To be more explicit :
>>
>> During install of a secondary server, when the tar.gz file that is
>> generated by sipxconfig is transported from the primary to secondary
>> server, it can also include whatever configuration information is
>> necessary so that it will not be necessary to subsequently do a "send
>> profile" to the secondary server.
> 
>> The current situation is that you see a gree REGISTERED indication but
>> the secondary server is not configured until you push profiles to it
>> by selecting that server and sending the profiles.
> 
> Correct.  The goal of the initial configuration tar file is to configure
> the minimal information needed to make the new distributed system
> manageable.  All service configuration should be then added using the
> normal distributed configuration mechanisms.  
> 
> Whether or not an explicit user interface step should be required is a
> UI issue.  The actual configuration steps on the wire should not change.
> 

Ideally sipXconfig would monitor the server after it registers and push
profiles once automatically once the supervisor is up.
I do not think this is how it's implemented today though: even if
sipXconfig tries to push profiles directly after registering location it's
probably  failing since the supervisor on the secondary server might not be
running yet.
So we might be stack with a manual push for 4.0
D.

_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev

Reply via email to