Hi all any one have a idea about Watcher and which RFC is for this
and also any one have/idea of some sample code ..
because i need to implement some watcher application which have following property
1.) Subscription for presence information state changes and notification acceptance .
2..) Subscription for presence information state changes and notification acceptance .
3) Subscription for the watcher information event template package .
4) Subscription for notification of state changes in XML document.
can any one help me regarding this or have a idea any forum related to this
thanks in advance hope getting for some +ve responce.
~Suresh
----- Original Message ----
From: "pjsip-request@xxxxxxxxxxxxxxxx" <pjsip-request at lists.pjsip.org>
To: pjsip at lists.pjsip.org
Sent: Monday, 30 June, 2008 9:30:31 PM
Subject: pjsip Digest, Vol 10, Issue 73
Send pjsip mailing list submissions to
pjsip at lists.pjsip.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
or, via email, send a message with subject or body 'help' to
pjsip-request at lists.pjsip.org
You can reach the person managing the list at
pjsip-owner at lists.pjsip.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of pjsip digest..."
Today's Topics:
1. Re: G723.1 codec Audio problem in pjsip (Nanang Izzuddin)
2. Re: G723.1 codec Audio problem in pjsip (Fabio Pietrosanti (naif))
3. Re: G723.1 codec Audio problem in pjsip (Nanang Izzuddin)
----------------------------------------------------------------------
Message: 1
Date: Mon, 30 Jun 2008 20:40:09 +0700
From: "Nanang Izzuddin" <nanang@xxxxxxxxx>
Subject: Re: G723.1 codec Audio problem in pjsip
To: "pjsip list" <pjsip at lists.pjsip.org>
Message-ID:
<c7f43120806300640m16d75e11oe99721a909b66fc1 at mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
Hi Fabio,
If you mean the G723.1 bitrate setting (actual 6300kbps should be written
6400), then it was bug and it has been fixed in 0.9.0, you should be able to
specify 6300 now. The integer calculation causes flooring, i.e: stream.c
calculates encoded frame size for jitter buffer, it would result 23.xxx
bytes and it is floored to 23 bytes, this may cause decoder get bad input
frame (1 byte in the end is random, since it is not stored by jitter buffer)
and it may cause decoder producing noise or fail to decode.
Regards,
nanang
2008/6/30 Fabio Pietrosanti (naif) <lists at infosecurity.ch>:
> Hi,
>
> implementing a codec means also implementing a customized RTP profile
> for such codec?
>
> Nanang Izzuddin wrote:
> > Hi,
> >
> > Sorry for the late response. The wrapper looks fine except for these
> > parts:
>
> _______________________________________________
> Visit our blog: http://blog.pjsip.org
>
> pjsip mailing list
> pjsip at lists.pjsip.org
> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/attachments/20080630/5518ad43/attachment-0001.html
------------------------------
Message: 2
Date: Mon, 30 Jun 2008 15:53:03 +0200
From: "Fabio Pietrosanti (naif)" <lists@xxxxxxxxxxxxxxx>
Subject: Re: G723.1 codec Audio problem in pjsip
To: pjsip list <pjsip at lists.pjsip.org>
Message-ID: <4868E53F.8030704 at infosecurity.ch>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
No, no
my meaning is, what if i want to implement for example AMR-NB .
Other than the codec interface in pjsip, it's required also to implement
an RTP profile specific for such codec?
Like http://www.rfc-editor.org/rfc/rfc4867.txt (
http://www.cs.columbia.edu/~hgs/rtp/ )
Fabio
Nanang Izzuddin wrote:
> Hi Fabio,
>
> If you mean the G723.1 bitrate setting (actual 6300kbps should be
> written 6400), then it was bug and it has been fixed in 0.9.0, you
> should be able to specify 6300 now. The integer calculation causes
> flooring, i.e: stream.c calculates encoded frame size for jitter
> buffer, it would result 23.xxx bytes and it is floored to 23 bytes,
> this may cause decoder get bad input frame (1 byte in the end is
> random, since it is not stored by jitter buffer) and it may cause
> decoder producing noise or fail to decode.
> Regards,
> nanang
>
>
> 2008/6/30 Fabio Pietrosanti (naif) <lists at infosecurity.ch>:
>
> Hi,
>
> implementing a codec means also implementing a customized RTP profile
> for such codec?
>
> Nanang Izzuddin wrote:
> > Hi,
> >
> > Sorry for the late response. The wrapper looks fine except for these
> > parts:
>
> _______________________________________________
> Visit our blog: http://blog.pjsip.org <http://blog.pjsip.org/>
>
> pjsip mailing list
> pjsip at lists.pjsip..org <mailto:pjsip at lists.pjsip.org>
> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Visit our blog: http://blog.pjsip.org
>
> pjsip mailing list
> pjsip at lists.pjsip.org
> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
>
------------------------------
Message: 3
Date: Mon, 30 Jun 2008 21:59:58 +0700
From: "Nanang Izzuddin" <nanang@xxxxxxxxx>
Subject: Re: G723.1 codec Audio problem in pjsip
To: "pjsip list" <pjsip at lists.pjsip.org>
Message-ID:
<c7f43120806300759p4c7aeb9fpd2255c6b55919b1b at mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
Hi Fabio,
Ah, sorry. It is standard then, not customized profile :) I am afraid it
would be yes, such special payload format needs to be implemented by codec
wrapper.
Regards,
nanang
2008/6/30 Fabio Pietrosanti (naif) <lists at infosecurity.ch>:
> No, no
>
> my meaning is, what if i want to implement for example AMR-NB .
>
> Other than the codec interface in pjsip, it's required also to implement
> an RTP profile specific for such codec?
>
> Like http://www.rfc-editor.org/rfc/rfc4867.txt (
> http://www..cs.columbia.edu/~hgs/rtp/ )
>
> Fabio
>
>
> Nanang Izzuddin wrote:
> > Hi Fabio,
> >
> > If you mean the G723.1 bitrate setting (actual 6300kbps should be
> > written 6400), then it was bug and it has been fixed in 0.9.0, you
> > should be able to specify 6300 now. The integer calculation causes
> > flooring, i.e: stream.c calculates encoded frame size for jitter
> > buffer, it would result 23.xxx bytes and it is floored to 23 bytes,
> > this may cause decoder get bad input frame (1 byte in the end is
> > random, since it is not stored by jitter buffer) and it may cause
> > decoder producing noise or fail to decode.
> > Regards,
> > nanang
> >
> >
> > 2008/6/30 Fabio Pietrosanti (naif) <lists at infosecurity.ch>:
> >
> > Hi,
> >
> > implementing a codec means also implementing a customized RTP profile
> > for such codec?
> >
> > Nanang Izzuddin wrote:
> > > Hi,
> > >
> > > Sorry for the late response. The wrapper looks fine except for
> these
> > > parts:
> >
> > _______________________________________________
> > Visit our blog: http://blog.pjsip.org <http://blog.pjsip.org/>
> >
> > pjsip mailing list
> > pjsip at lists.pjsip.org <mailto:pjsip at lists.pjsip.org>
> > http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
> >
> >
> > ------------------------------------------------------------------------
> >
> > _______________________________________________
> > Visit our blog: http://blog.pjsip.org
> >
> > pjsip mailing list
> > pjsip at lists.pjsip.org
> > http://lists.pjsip..org/mailman/listinfo/pjsip_lists.pjsip.org
> >
>
>
> _______________________________________________
> Visit our blog: http://blog.pjsip.org
>
> pjsip mailing list
> pjsip at lists.pjsip.org
> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/attachments/20080630/13bc57b1/attachment-0001.html
------------------------------
_______________________________________________
pjsip mailing list
pjsip at lists.pjsip.org
http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
End of pjsip Digest, Vol 10, Issue 73
*************************************
Bring your gang together. Do your thing. Find your favourite Yahoo! group at http://in.promos.yahoo.com/groups/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/attachments/20080701/60189f7e/attachment-0001.html
