Subject: [Megaco] Wild carding ephemeral terminations or multiple contexts in ServiceChange for OOS

From: Majeed Arif-P27336 <[email-masked]>
Date: Fri, 11 Apr 2003 09:10:46 -0700

All,

The MG has "n" number of boards for bearer processing. The "board1" has four active calls (but has capacity to handle "m" number of calls). All terminations on the MG are ephemeral and are structured like "Term/board1/term1" to "Term/boardn/termm". The "board1" abruptly goes out of service. Which of the following service change command from MG to MGC is more appropriate or even valid? (Suggestions for improvement are welcomed).

MEGACO/1 [10.1.33.61]: 25000
   Transaction = 4321 {
       Context = * { 
           ServiceChange = Term/board1/* {Services {
               Method=Forced }
               }
        }
   } 

MEGACO/1 [10.1.33.61]: 25000
   Transaction = 4321 {
       Context = 678 { 
           ServiceChange = * {Services {
               Method=Forced }
               }
        }
       Context = 977 { 
           ServiceChange = * {Services {
               Method=Forced }
               }
        }
       Context = 1274 { 
           ServiceChange = * {Services {
               Method=Forced }
               }
        }
       Context = 170 { 
           ServiceChange = * {Services {
               Method=Forced }
               }
        }
   }

Do the MGC have to clear each of above calls with a subtract command (in some out of service situations, the MG does not have time to handle subtract command)?

Arif
_______________________________________________
Megaco mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/megaco