[Moved to SIP Implmentors.] > it was nice to see that someone was helping me to complete my > work.i have a doubt in the Via Header.Now in one of the mails in > mailing list archive it says that the Matching of Via Header means > matching the Transport,Branch,Protocol Name(SIP),Version(2.0) and > HostName. I'm not sure what context this matching is in, but I'm thinking you might want to incorporate the port and maddr, too. > When u match a Hostname,if the hostname is normal name as in Via > then it should me matched case-insensitivly,if the hostname is IP > Address and the HostName in the Via Field is a String,how should > the matching be done?. Assuming this is related to when to check if a response is destined for this client, I would hope that the client had some idea of the Vias it was generating, thus I would not see this as an issue. However, as an inside, I would never start doing things DNS resolution to check whether Vias were equivalent. So much is asynchronous already, my head hurts; I don't want to have to start dealing with asynchronous parsers. &:) > When Request is Received How does one Check that it is mulicast > or not?. This is surprisingly difficult, which is why maddr is a MUST when a client sends to a multicast address. (6.47.1 in current bis-02). > one more thing,how does a Proxy determine that a Request-URI > of the request it has got is Correct,as seen by the proxy,does > the Proxy maintain a List of Request-URI or what?. Uh, I'm not sure what you mean by correct. An arbitrary proxy can only determine whether a Request-URI is legal, I guess, with nominal parsing. If the proxy needs to determine whether a request is destined for itself, I guess it has to do this by inspecting it's network interfaces and/or some sort of configuration. - Jo. _______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
