Hi,
Basically OSA is protocol independent architecture, So 1-1 mapping for
many of Sip events to OSA events are not available.
But mapping between SIP request/responses and the OSA events are there in
3gpp specs. This mapping is only limited to
INVITE, 18x , 200, 5xx and BYE. But mapping for other requests UPDATE,
OPTIONS, MESSAGE etc are not there.
You can check this in either release 6 or release 5 docs of 3gpp.
Rgds,
Amar
Mobile: +919886395894
The greatest enemy of best is "good." If you're willing to accept "good"
you'll never be the "Best."
"Sharath Chandra"
<[EMAIL PROTECTED]
et> To
Sent by: <[email protected]>
sip-implementors- cc
[EMAIL PROTECTED]
ia.edu Subject
Re: [Sip-implementors] Doubt
regarding B2BUA
12/08/2005 10:57
AM
Please respond to
[EMAIL PROTECTED]
t
In IMS architecture the interaction between S-CSCF to Application server
(AS) i.e ISC (IMS Service Control Interface) should be SIP. How can
services
based on OSA SCS be triggered. Services like Presence can be supported by
SIP but if i want host some new custom service that is supported by OSA
interface. Should my OSA SCS have a SIP capability. Can somebody help me
understand the type of SIP communication that happens between UE ----
S-CSCF ---- AS
Thank you.
sharath
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Amarendra
Kumar
Sent: Tuesday, August 02, 2005 9:15 AM
To: Dale Worley
Cc: [email protected];
[EMAIL PROTECTED]
Subject: Re: [Sip-implementors] Doubt regarding B2BUA
As per the OSA there can be multiple SCFs and multiple applications
running on top of it.
B2B can be one of such SCFs, all together entire box can be treated as
an application
server. Unlike Proxy B2BUA is 3rd party call controller, thus more
powerful entity to
implement apllications. There may be multiple application interacting
with underlying SCFs for different services. While implenting
application we may need to give control to B2BUA
for further action to be taken.
1. In IMS architechure there is no interface defined to pass reg
info from S-CSCF to
Application server (B2BUA in the core). Thus service that needs
registered contact
info may not be posible to implement. (eg. services that include
forking.)
2. In most of the implentations for B2BUA, always proxy is the next
hop. more over all
registration/contact info will be with Proxy. But Proxy
doesn't have intelligence to take any action based on the
request/responce. Some
of implemntation of B2BUA restrict B2BUA to do forking. So if
this the case in some
of services B2BUA don't have right context to respond to.
On 8/2/05, Dale Worley <[EMAIL PROTECTED]> wrote:
> > From: Paul Kyzivat
> >
> > Amarendra Kumar wrote:
> > > B2B. Is B2B is the right place to implement application like Shared
> > > Call Appearance.
> >
> > Whether it is "the right place",
> > or a good place, is a subject of considerable debate, and depends on
> > your definition of "good". Using a B2BUA may make it possible to use an
> > architecture similar to a traditional PBX. But many consider it
> > inconsistent with the principles and goals of SIP.
>
> I would state it more strongly as "A B2BUA is *almost never* the right
place
> to implement an application."
>
> Dale
>
> _______________________________________________
> Sip-implementors mailing list
> [email protected]
> http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
>
--
Rgds,
Amar
Mobile: +919886395894
The greatest enemy of best is "good." If you're willing to accept "good"
you'll never be the "Best."
_______________________________________________
Sip-implementors mailing list
[email protected]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
*********************** FSS-Unclassified ***********************
"DISCLAIMER: This message is proprietary to Hughes Software Systems Limited
(HSS) and is intended solely for the use of the individual to whom it is
addressed. It may contain privileged or confidential information and
should not be circulated or used for any purpose other than for what it is
intended. If you have received this message in error, please notify the
originator immediately. If you are not the intended recipient, you are
notified that you are strictly prohibited from using, copying, altering, or
disclosing the contents of this message. HSS accepts no responsibility for
loss or damage arising from the use of the information transmitted by this
email including damage from virus."
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
