That statement means that when the SIP element is acting as a redirect
server for a given transaction, it does not forward/proxy the request on to
another SIP element. There is no rule that says a given element is only a
redirect server. These names "proxy server", "redirect server" are just
"roles" that a SIP element can take. They can choose their role on a
per-transaction basis. Your server could send the request on to another
server that could handle the request. It would then be a proxy for that
transaction. For another request that it has the necessary information it
would respond as a redirect server.

When a client sends a request to a SIP element, it should not assume that it
is a redirect server or proxy server or user agent server.

cheers,
(-:bob

Robert F. Penfield
Chief Software Architect
Acme Packet, Inc.
130 New Boston Street
Woburn, MA 01801
[EMAIL PROTECTED]

----- Original Message -----
From: "Manish S. Jalan" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, December 06, 2001 11:08 PM
Subject: [Sip-implementors] Redirection v/s DNS


>
> Hello,
>
> I am trying to co-relate redirection in SIP with DNS in http.
>
> Redirect server helps in getting the location of any desired destination.
> DNS server, also does a similar kind of job in http.
>
> Redirect server, will search in its db to get contact details of the
destination we want to reach.
> When it finds one, provides us that contact. When its unable to find one,
informs us about it.
> Fine.
>
> DNS server, on the other hand, if cannot reslove the address on its own,
queries another DNS server for reachability.
>
> All SIP rfc/bis drafts state, Redirect server does not issue requests of
its own.
>
> Now, my question is:
> --------------------
> Plain reply from the Redirect server, that i don't know, will not help the
client.
> Instead, we would desire, that the Redirect server if unable to resolve a
url, should consult another redirect server, just as DNS servers do.
>
> Wouldn't this mechanism be great?
>
> But, Redirect server has been handicapped by the fact, that "It should not
generate any request of its own.".
>
> Shouldn't this constraint be removed?
>
> Don't we need a mechanism to identify, what servers are Proxy, what are
Redirect in the SIP network? Don't we as a client need to be able to say,
that this particular server is Proxy or a Redirect? Wouldn't this knowledge
help the uac in forwarding its requests?
>
> Regards,
> -Manish
>
> _______________________________________________
> Sip-implementors mailing list
> [EMAIL PROTECTED]
> http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
>

_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors

Reply via email to