Subject: Re: Fw: [Megaco] Need clarifications on SVC's initiated from media gateway..

From: Ujjwal Wadhawan <[email-masked]>
Date: Mon, 2 Apr 2007 19:10:57 +0530

Hi Arvind

The handling of Notify request by the MG, that is awaiting ServiceChange 
response, depends on the two mentioned ServiceChange request scenarios: -

·       MG initial registration
Media Gateway should not process a Notify request since no events have 
been enabled. (Control association has not been established with MGC). 

·       MG Lost Communication 
When a Media Gateway detects a loss of communication it tries to 
re-establishes the association with MGC. In this case the Notify requests 
received should be buffered until the control association has been 
restored. The buffered requests should be retransmitted when the control 
association has been re-established.

Regards, 
Ujjwal Wadhawan

"Arvind Charanyan" <[email-masked]> 
04/02/2007 03:19 PM

To
<[email-masked]>
cc

Subject
[Megaco] Need clarifications on SVC's initiated from media      gateway..

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 
 _______________________________________________
Megaco mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/megaco

***********************  Aricent-Private   ***********************

***********************  Aricent-Restricted   ***********************
"DISCLAIMER: This message is proprietary to Aricent  and is intended solely for the use of 
the individual to whom it is addressed. It may contain privileged or confidential information and should not be 
circulated or used for any purpose other than for what it is intended. If you have received this message in error, 
please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly
prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility for 
loss or damage arising from the use of the information transmitted by this email including damage from virus."
_______________________________________________
Megaco mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/megaco