Re: Problem in ADD request.

Hi John,

I feel we should return an error with the termination in the added context. I have seen atleast one MG (Mediatrix Line GW, I believe) behave this way to an error with in an ADD command.

Thanks,
Sriram

-----Original Message-----
From: [email protected] on behalf of John Wainwright
Sent: Fri 8/22/2008 10:18 PM
To: [email protected]
Subject: [Megaco] Problem in ADD request.
 
 

My apologies if this is repeated but I seem to be having issues trying
to post to the Megaco list

 

If I get a message such as the following to create a new context and ADD
a specific termination into it 

 

C=${

A=AALN/1{

M{

O{MO=RC}},

SG{ALERT/RI{PATTERN=1}},

E=38463393{AL/OF{STRICT=FAILWRONG}},

}}}

 

What should I return for the context ID if the line is already offhook
and should the termination get added to a new context?

 

Should I return an error message for a specific context that was just
created with AALN/1 now in this context such as shown below, or should I
return an error message for the null context and the termination has not
been added to any context?

 

REPLY = 65234524 {

  CONTEXT = 5 {

    ERROR = 540 { "Unexpected initial hook state" },

    ADD = AALN/1

    }

  }

}

 

Thanks

John

 


****************************************
The information contained in this message may be confidential, privileged or protected from disclosure. If you have received it by mistake, please let us know by e-mail reply and delete it from your system; you may not copy, disseminate or disclose the contents of this message to anyone.

_______________________________________________
Megaco mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/megaco