Since INFO is mid-dialog, the endpoints can signal what they support. It does not need to be known a priori
Regards, Jeroen -----Oorspronkelijk bericht ----- Van: "Eric Burger" <[EMAIL PROTECTED]> Aan: "Peili Xu" <[EMAIL PROTECTED]> CC: "sip" <[email protected]> Verzonden: 31-8-07 00:03 Onderwerp: Re: [Sip] INFO Saying, "OK for interworking" does not really say anything. If I come up with a really broken method for interworking, saying that it is for interworking does not make it correct. The problem is, how do the endpoints know they will be able to communicate? For the ISUP/Q.sig/DPNSS/mumble case, the endpoints know they will be able to interoperate because they know a'priori: they are configured to work. However, this means that the devices must be in the same administrative domain and configured properly. Said in a different manner, INFO works fine for non-inter-network use. It would be hard for the IETF to say, "Here is a non-IETF use. We will not use it. You cannot use it with anyone else. You cannot use it between manufacturers, unless you get them to agree to this use." That is a bit more of what we call the toxic waste warning that accompanies 3GPP specifications... On 8/27/07 8:35 AM, "Peili Xu" <[EMAIL PROTECTED]> wrote: > Hi Eric, > > Several cases I encounter to use INFO is for interworking with PSTN signaling, > or simulate PSTN services at SIP entities such as SIP UA or SIP GW, > which require mid-dialog information change. > _______________________________________________ Sip mailing list https://www1.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use [EMAIL PROTECTED] for questions on current sip Use [EMAIL PROTECTED] for new developments on the application of sip
