Which MGC should be contacted first on retransmission timeout?
"Raphael Tryster" <[email protected]>
| Newsgroups | gmane.ietf.megaco |
|---|---|
| Message-ID | <[email protected]> |
Is there a contradiction between 11.5 and F.3.6?
11.5 says:
"If the MG detects a failure of its controlling MGC, it attempts to
contact the next MGC on its pre provisioned list. It starts its attempts
at the beginning (primary MGC), unless that was the MGC that failed, in
which case it starts at its first secondary MGC".
F.3.6 says:
"When the MG has detected a loss and subsequent re-establishment of
communication with the MGC, the MG sends a ServiceChange Command with a
ServiceChangeMethod of 'Disconnected' to the MGC in the current control
association. If the MGC fails to respond, the MG then sends a
ServiceChange Command with a ServiceChangeMethod of 'Failover' and
ServiceChangeReason 909 ('MGC Impending Failure') to each MGC in its
list in turn until it has successfully established a new control
association, or it has exhausted its list of MGCs".
So, suppose MG sent a Notify and failed to receive a reply before
retransmissions timed out. According to 11.5, it would send SC to a
DIFFERENT MGC. According to F.3.6, it would send SC to the SAME MGC,
and only try a different one if the SC also timed out. Which is it?
I am also puzzled by the language of F.3.6. ""When the MG has detected
a loss and subsequent re-establishment of communication with the MGC".
Usually, SC Disconnected is sent as a trial to see whether the MGC will
now reply, and not as a result of re-establishment of communication. Is
some other method of detecting re-establishment of communication being
hinted at here?
Raphael Tryster
**********************************************************************************************
IMPORTANT: The contents of this email and any attachments are confidential. They are intended for the
named recipient(s) only.
If you have received this email in error, please notify the system manager or the sender immediately and do
not disclose the contents to anyone or make copies thereof.
*** eSafe scanned this email for viruses, vandals, and malicious content. ***
**********************************************************************************************