hi
I'm looking at implementing some routing logic in a Proxy Server
if P1 is a proxy server I am implementing as an Outbound Proxy for
endpoint E1,
can I, on receiving an INVITE request from E1, get P1 to initiate a
REGISTER transaction with the local domain Registrar for the "To:"
addressee
it seems to me that the Registrar should support a REGISTER request
WITHOUT a "Contact:" header in order to query a given Address of Record
and I need this functionality to be able to decide whether or not to
redirect the caller to a local Gateway
my concern then is about the specific parameters of the REGISTER request
sent from P1 to the Registrar
1) would (and should) this be considered a unique transaction unrelated
to E1's initial INVITE
(hence the included Via field would have a unique "branch" ID?)
2) what would the Call-ID and CSeq be? presumably, something
specific/unique to P1 (and not E1)
3) I can populate the REGISTER request's "To:" field from the INVITE,
what about the "From:" field?
4) would a Registrar want to authenticate any aspect of such a REGISTER
query request? if so, how could (or even could) the proxy authentic the
request without consulting the endpoint?
to summarize, I'm thinking of something like this, with a redirection to
the local gateway (GW) sent in reply from P1 to E1 if it turns out the
addressee is not known at the Registrar...
E1 P1 R GW
| | | |
| | | |
INVITE (1)
----------->
REGISTER (query)
---------->
OK (with Contact info) - or possibly 404 Not Found
<----------
Moved Temporarily (Contact GW)
<-----------
INVITE (2)
------------------------------------->
this should all be transparent to E1
so is this doable and what would those fields hold?
cheers in advance
m
The information contained in this e-mail message is PRIVATE. It may contain
confidential information and may be legally privileged. It is intended for the
exclusive use of the addressee(s). If you are not the intended recipient, you
are hereby notified that any dissemination, distribution or reproduction of
this communication is strictly prohibited. If the intended recipient(s) cannot
be reached or if a transmission problem has occurred, please notify the sender
immediately by return e-mail and destroy all copies of this message.
Thank you.
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
