> > Prem Sumetpong wrote:
> > > Since SIP doesnt define the interface between the registrar
> > > and location service and leaves it to the implementation
> > >
> > > The assumptions then are
> > >
> > > - registrar and proxy are (must be ??) from the same
> > > vendor. The "how
> > > to" fetch and store from the shared storage is known by both the
> > > registrar (stores) and proxy (fetches).
> >
> > No, not necessarily. The registrar and proxy might just
> > need to be configured with some ODBC Data Source (e.g.,
> > an Oracle DB), or an LDAP Server.
> >
>
> what is the schema or database data dictionary shared
> between the two
> that will be fetched via LDAP or ODBC/JDBC so that a proxy from
> one vendor can
> work with a location server from another vendor ?? If it is not a
> published one
> then how can interoperability be guaranteed.
Sorry, yeah, I don't know what question I was answering
here. There is no well-defined schema / whathaveyou,
so in general interoperability cannot be guaranteed between
vendors X and Y.
> > > Wouldnt that
> > > cause an interoperability problem ??
> >
> > No, not really, unless people wanted to deliver "Location
> > Servers" that didn't talk SIP, but talked some new
> > protocol X.
> >
>
> Assuming the location server talked SIP - would an INVITE to
> location server
> from a registration server cause it to return location
> information in the 200
> OK response ??
Sorry, again my answer wasn't too helpful. When I
talked of a Location Server that talked SIP, I
basically meant a Redirect Server.
Hopefully this time This Helps,
- Jo.
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
