pjsip Digest, Vol 24, Issue 30

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

Is there any way to add H263 to PJSIP?

Regards
Joseph

--------------------------------------------------
From: <pjsip-request@xxxxxxxxxxxxxxx>
Sent: Friday, August 14, 2009 11:37 AM
To: <pjsip at lists.pjsip.org>
Subject: pjsip Digest, Vol 24, Issue 30

> 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. configure can't see alsa headers (Peter Hartmann)
>   2. Re: Add video to PJSIP (fcch2k)
>   3. Re: Add video to PJSIP (xutm)
>   4. XCAP client in PJSIP (xutm)
>   5. Re: XCAP client in PJSIP (Sa?l Ibarra)
>   6. a few questions (Tiago Ferreira)
>   7. Re: a few questions (Sa?l Ibarra)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 14 Aug 2009 01:29:53 -0400
> From: Peter Hartmann <ascensiontech@xxxxxxxxx>
> Subject: configure can't see alsa headers
> To: pjsip at lists.pjsip.org
> Message-ID:
> <9bd317560908132229x7be29908m1c167139caaf7b90 at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> I'm having this weird problem where when I try and cross compile, the
> configure script refuses to see the alsa header files in
> /usr/include/alsa.  When I do a native ./configure it does see it.
> What could be happening here?
>
> This is in my environment when cross-compiling:
>
> export BUILD_GCC=gcc
> export CC='/opt/codesourcery/bin/arm-none-linux-gnueabi-gcc '
> export CXX='/opt/codesourcery/bin/arm-none-linux-gnueabi-g++ '
> export AR=/opt/codesourcery/bin/arm-none-linux-gnueabi-ar
> export RANLIB=/opt/codesourcery/bin/arm-none-linux-gnueabi-ranlib
>
> and I configure with this:
>
> ./configure --build=i686-pc-linux-gnu --target=arm-none-linux-gnueabi
> --host=arm-none-linux-gnueabi --disable-oss
>
> Just realized that It seems only to happen when using
> --host=arm-none-linux-gnueabi.  And btw I've cross compiled alsa-lib.
> Other flags like --host=arm-elf-linux crap put in expected ways (since
> i'm not set up for that) but do detect the alsa stuff.
>
> Thanks!
>
> Peter
>
>
>
> ------------------------------
>
> Message: 2
> Date: Fri, 14 Aug 2009 00:10:31 -0700
> From: fcch2k <fcch2000@xxxxxxxxx>
> Subject: Re: Add video to PJSIP
> To: pjsip list <pjsip at lists.pjsip.org>
> Message-ID:
> <2ba6b7910908140010lca1a026w387e3e6319de978b at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Hi Xutm,
>
> How to use the VLC to send video stream behind the NATs?
> The VLC cannot specify the local source port. Here is the link from 
> VideoLan
>
> http://forum.videolan.org/viewtopic.php?f=32&t=63638&p=212608&hilit=source+port%E2%80%A6#p212608
>
>
> On 8/10/09, Shayne O'Neill <shayne.oneill at gmail.com> wrote:
>>
>> It might also be worth looking at the OPAL suite if you need a
>> standards based video solution. OPAL , imho, isn't nearly a complete a
>> SIP implementation as PJSip, which is very acomplished, audio-wise,
>> but it does have video support for H323 , and probably SIP.
>>
>> Its also a lot more work, but if your developing apps, thems the
>> breaks. If you want to port to a mobile app, you'll need to port PTLib
>> which looks to be bit of a task.
>>
>> On 10/08/2009, at 5:35 PM, SIDIMOULAY wrote:
>>> Hi,
>>>
>>> I am a new user of SIP applications, I'm working on a matter of
>>> course that is aimed at adding a video codec to PJSIP (H264), I did
>>> the rounds of the Internet for over a month, I managed to add the
>>> audio codecs but no video.
>>> I'm waiting for all your suggestions and advices
>>>
>>> Regards
>>>
>>>
>>> __________ Information provenant d'ESET Smart Security, version de
>>> la base des signatures de virus 4321 (20090810) __________
>>>
>>> Le message a ?t? v?rifi? par ESET Smart Security.
>>>
>>> http://www.eset.com
>>> _______________________________________________
>>> 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
>>
>> ===================================
>> Shayne O'Neill Development
>> Mobile, Web and Business process integration.
>> shayne.oneill at gmail.com 0400247091
>> Ask me about how Alfresco can help your business grow.
>>
>>
>> _______________________________________________
>> 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: Fri, 14 Aug 2009 15:57:49 +0800
> From: xutm <xutom2006@xxxxxxxxx>
> Subject: Re: Add video to PJSIP
> To: pjsip list <pjsip at lists.pjsip.org>
> Message-ID:
> <44d4322a0908140057y40953319gc1c0f30de625e89f at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hi fcch2k
>
> Exactly VLC use random local source port default. But you can change the
> corresponding code of VLC.
> Indeed, I call method bind before connect in src/network/udp.c to bind my
> local source port , instead of only calling method connect to bind random
> local source port.
> Please view the topic:
> http://forum.videolan.org/viewtopic.php?f=32&t=62140
>
> 2009/8/14 fcch2k <fcch2000 at gmail.com>
>
>> Hi Xutm,
>>
>> How to use the VLC to send video stream behind the NATs?
>> The VLC cannot specify the local source port. Here is the link from
>> VideoLan
>>
>>
>> http://forum.videolan.org/viewtopic.php?f=32&t=63638&p=212608&hilit=source+port%E2%80%A6#p212608
>>
>>
>> On 8/10/09, Shayne O'Neill <shayne.oneill at gmail.com> wrote:
>> >
>> > It might also be worth looking at the OPAL suite if you need a
>> > standards based video solution. OPAL , imho, isn't nearly a complete a
>> > SIP implementation as PJSip, which is very acomplished, audio-wise,
>> > but it does have video support for H323 , and probably SIP.
>> >
>> > Its also a lot more work, but if your developing apps, thems the
>> > breaks. If you want to port to a mobile app, you'll need to port PTLib
>> > which looks to be bit of a task.
>> >
>> > On 10/08/2009, at 5:35 PM, SIDIMOULAY wrote:
>> >> Hi,
>> >>
>> >> I am a new user of SIP applications, I'm working on a matter of
>> >> course that is aimed at adding a video codec to PJSIP (H264), I did
>> >> the rounds of the Internet for over a month, I managed to add the
>> >> audio codecs but no video.
>> >> I'm waiting for all your suggestions and advices
>> >>
>> >> Regards
>> >>
>> >>
>> >> __________ Information provenant d'ESET Smart Security, version de
>> >> la base des signatures de virus 4321 (20090810) __________
>> >>
>> >> Le message a ?t? v?rifi? par ESET Smart Security.
>> >>
>> >> http://www.eset.com
>> >> _______________________________________________
>> >> 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
>> >
>> > ===================================
>> > Shayne O'Neill Development
>> > Mobile, Web and Business process integration.
>> > shayne.oneill at gmail.com 0400247091
>> > Ask me about how Alfresco can help your business grow.
>> >
>> >
>> > _______________________________________________
>> > 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/20090814/52e3b1f1/attachment-0001.html>
>
> ------------------------------
>
> Message: 4
> Date: Fri, 14 Aug 2009 17:00:05 +0800
> From: xutm <xutom2006@xxxxxxxxx>
> Subject: XCAP client in PJSIP
> To: pjsip at lists.pjsip.org
> Message-ID:
> <44d4322a0908140200g39d50853i43255db4a333c2d8 at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hi all,
>
> I think there is no XCAP client in PJSIP. Does someone know how to add 
> XCAP
> client support into PJSIP? Or please give me some advice? Thanks in 
> advance!
>
> Regards,
> xutm
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: 
> <http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/attachments/20090814/d36e9670/attachment-0001.html>
>
> ------------------------------
>
> Message: 5
> Date: Fri, 14 Aug 2009 11:08:08 +0200
> From: Sa?l Ibarra <saghul@xxxxxxxxx>
> Subject: Re: XCAP client in PJSIP
> To: pjsip list <pjsip at lists.pjsip.org>
> Message-ID:
> <34035cf70908140208vacae4a2h81983e6d3d1775ff at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> If you're using C++ you may want to have a look at qjsimple
> (http://www.ipcom.at/index.php?id=560/) sources. If using python check
> xcapclient (http://sipsimpleclient.com/wiki/xcapclient)
>
>
> Regards,
>
>
> -- 
> /Sa?l
> http://www.saghul.net | http://www.sipdoc.net
>
>
>
> ------------------------------
>
> Message: 6
> Date: Fri, 14 Aug 2009 10:28:34 +0100
> From: "Tiago Ferreira" <maiaboy@xxxxxxxxxxx>
> Subject: a few questions
> To: <pjsip at lists.pjsip.org>
> Message-ID: <BLU141-DAV690F38DA098689A9E9F5BBF020 at phx.gbl>
> Content-Type: text/plain; charset="us-ascii"
>
> Hello,
>
>
>
> I just started using pjsip in python and I was wondering if you could 
> answer
> me a few questions.
>
>
>
> 1: I tried sending audio with a wave file but I had no success thus far. 
> Can
> anyone show me a simple audio tutorial or code sample for python?
>
>
>
> 2: I am starting to implement a small script that registers to a server,
> answers calls and receives DTMF signals and acts according to what he
> received. Bui I just saw the FAQ and from what I understood, using pjsip I
> can't interpret the received DTMF signals, is this true?
>
>
>
> Thank you
>
> Tiago
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: 
> <http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/attachments/20090814/95f0d1c0/attachment-0001.html>
>
> ------------------------------
>
> Message: 7
> Date: Fri, 14 Aug 2009 11:36:55 +0200
> From: Sa?l Ibarra <saghul@xxxxxxxxx>
> Subject: Re: a few questions
> To: pjsip list <pjsip at lists.pjsip.org>
> Message-ID:
> <34035cf70908140236j2eca5545y6479a1bbb5c431d9 at mail.gmail.com>
> Content-Type: text/plain; charset=windows-1252
>
> On Fri, Aug 14, 2009 at 11:28 AM, Tiago Ferreira<maiaboy at hotmail.com> 
> wrote:
>> Hello,
>>
>>
>>
>> I just started using pjsip in python and I was wondering if you could 
>> answer
>> me a few questions.
>>
>>
>>
>> 1: I tried sending audio with a wave file but I had no success thus far. 
>> Can
>> anyone show me a simple audio tutorial or code sample for python?
>>
>
> Try this:
>
> player = self.core.lib.create_player("/tmp/ring.wav", True)
> lib.conf_connect(lib.player_get_slot(player), 0)
>
>
>>
>>
>> 2: I am starting to implement a small script that registers to a server,
>> answers calls and receives DTMF signals and acts according to what he
>> received. Bui I just saw the FAQ and from what I understood, using pjsip 
>> I
>> can?t interpret the received DTMF signals, is this true?
>>
>
> I don't think you are able to interpret DTMF tones from the Python API...
>
>
>
> Regards,
>
>
> -- 
> /Sa?l
> http://www.saghul.net | http://www.sipdoc.net
>
>
>
> ------------------------------
>
> _______________________________________________
> pjsip mailing list
> pjsip at lists.pjsip.org
> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
>
>
> End of pjsip Digest, Vol 24, Issue 30
> *************************************
>
>
> __________ Information provenant d'ESET Smart Security, version de la base 
> des signatures de virus 4333 (20090813) __________
>
> Le message a ?t? v?rifi? par ESET Smart Security.
>
> http://www.eset.com
>
>
> 

__________ Information provenant d'ESET Smart Security, version de la base des signatures de virus 4333 (20090813) __________

Le message a ?t? v?rifi? par ESET Smart Security.

http://www.eset.com






[Index of Archives]     [Asterisk Users]     [Asterisk App Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [Linux API]
  Powered by Linux