|
Issue
(1)
You can't send commands from the MG such as
notify without having a Control Association in
place.
An example of a time that you may find yourself wanting
to do this is when you have a non-empty default events
descriptor
provisioned on a termination, and this events
descriptor is applied when the Terminations restart at a Cold
Boot.
In this case I think that you should only apply
the termination descriptors and property defaults at the time when Control
Association
Establishment completes, so that the termination is
discarding events whilst the ServiceChange is in progress.
If the Control Association stalls, or is explicitly
taken away by Management Action then the MG should wait until it is
fully re-established
or a new one established (Service Change is
Completed) before issuing any other commands.
Issue (2)
You should not to transmit Notify Requests whilst
the Control Association is incomplete, as this is
illegal
Steve
Hi All:
I need some clarifications on
issues which are described below:
Issue
1:
1)
Media gateway initiates service
change request, and waiting for a response.
2)
When Notify events occur in this
period how should we handle them?
Should we send out the notify requests to the MGC to which we have initiated the
SVC? Or queue them until the control association is
established?
Issue
2:
If we decide to transmit
notify requests while waiting for service change response, then how do we handle
Notify response timeouts?
Moreover, when we fail to
establish Control association to the Primary MGC and failover to the secondary,
what should be done to the
Notify requests that were
being transmitted to the primary? Should we abort all those transactions or
should the same be retried on the secondary?
Thanks and
Regards,
Arvind
|