This case was approved at the LSARC meeting today.
The project team plans to update the libosip man page
to indicate that libsip is the current preferred sip
library on Solaris/OpenSolaris.
Cheers,
Jim
Hi James,
Please check my in line comments below.
cheers,
Simon
James Carlson wrote:
> Simon Sun writes:
>
>> By default, the port 5060 is for SIP use. If two instances of one SIP
>> proxy were started up, the latter one should fail since the default port
>> has been occupied by the first
Jim Walker writes:
> James Carlson wrote:
> > I urge the project team to consider bringing in at least one
> > application that makes use of this library. Libraries without
> > consumers are, in my opinion, just baggage. And in this case, given
> > that the library also represents functional dupl
James Carlson wrote:
> Jim Walker writes:
>> James Carlson wrote:
>>> I urge the project team to consider bringing in at least one
>>> application that makes use of this library. Libraries without
>>> consumers are, in my opinion, just baggage. And in this case, given
>>> that the library also re
James Carlson wrote:
>
>>> Are these being delivered by this or by some other project? And do
>>> any of them work with the existing libsip?
>>>
>> These application will not be delivered by this case and I'm not sure if
>> someone is working on porting them. None of them works with libsip.
>
Simon Sun writes:
> > Please indicate which one of these two will be "preferred" and what
> > the documentation will say.
> >
> I'd express it explicitly in man page of libopsip2 like this:
>
> Solaris provides another library named libsip for SIP development
> purpose. We'd suggest you to co
Hi James,
Please see my in-line comments below.
cheers,
Simon
James Carlson wrote:
> Simon Sun writes:
>
>> James Carlson wrote:
>>
>>> What (if anything) will be done with the existing SIP library and SIP
>>> proxy that are already in OpenSolaris?
>>>
>> Nothing needed for the cu
Simon Sun writes:
> By default, the port 5060 is for SIP use. If two instances of one SIP
> proxy were started up, the latter one should fail since the default port
> has been occupied by the first instance. Same thing will happen to the
> two different proxies. It has nothing do with the libra
Simon Sun writes:
> James Carlson wrote:
> > What (if anything) will be done with the existing SIP library and SIP
> > proxy that are already in OpenSolaris?
> >
> Nothing needed for the current SIP stuff since there's no conflict
> between each other.
What happens if someone tries to use both
Hi James,
Below is my answer to your concern. If there's anything improper, please
let me know. Sorry for the late reply.
cheers,
Simon
James Carlson wrote:
> James Walker writes:
>
>>oSIP is little in size and code and thus could be use to implement IP
>>soft-phone as well as embe
James Walker writes:
>oSIP is little in size and code and thus could be use to implement IP
>soft-phone as well as embedded SIP software. oSIP is not limited to
> endpoint
>agents, and can also be used to implement "SIP proxy".
What (if anything) will be done with the existing SIP lib
I'm sponsoring this familiarity case for Simon Sun. The requested
release binding is minor. The man page has been posted in the
materials directory.
Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI
This information is Copyright 2009 Sun Microsystems
1. Introduction
1.1. Project/Component W
12 matches
Mail list logo
