hi, take a look at the logging module in pjsua (pjsua_msg_logger, pjsua_core.c) however, TLS is used to encrypt the SIP, its the standard way to do it, On Fri, Nov 27, 2009 at 11:54 AM, Sudhakar Singh <luwangsudhakar at yahoo.com>wrote: > Hello everybody, > > Can anyone please help me to find out exactly from which file the SIP > packets are created in the PJSIP.I'm in urgent need to encrypt the packets > before transmission over internet.Actually my idea is to encrypt the SIP > packets & encapsulate in the HTTP packet & then transmission over internet > to connect to the Asterisk server.If anyone have any idea how to do it, > please share with me. > > > Actually I've no practical idea, where the SIP packets are created in PJSIP > code.Any help will be of great value.. > > Thanks in advance, > > Regards, > > Sudhakar Singh > > --- On *Thu, 26/11/09, pjsip-request at lists.pjsip.org < > pjsip-request at lists.pjsip.org>* wrote: > > > From: pjsip-request@xxxxxxxxxxxxxxx <pjsip-request at lists.pjsip.org> > Subject: pjsip Digest, Vol 27, Issue 71 > To: pjsip at lists.pjsip.org > Date: Thursday, 26 November, 2009, 11:30 PM > > Send pjsip mailing list submissions to > pjsip at lists.pjsip.org<http://in.mc948.mail.yahoo.com/mc/compose?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<http://in.mc948.mail.yahoo.com/mc/compose?to=pjsip-request at lists.pjsip.org> > > You can reach the person managing the list at > pjsip-owner at lists.pjsip.org<http://in.mc948.mail.yahoo.com/mc/compose?to=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. APS Direct on s60 5th edition devices (Jerry Monteiro) > 2. Version 1.5 is released (Benny Prijono) > 3. Re: SDP negotiation: Call hold problems (Benny Prijono) > 4. Re: Version 1.5 is released (Italo Andrea Lisi) > 5. Re: SDP negotiation: Call hold problems (Rafael Maia) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 26 Nov 2009 11:19:28 +0800 > From: "Jerry Monteiro" <jerrym@xxxxxxxxxxxxxxxxxxxxxxxx<http://in.mc948.mail.yahoo.com/mc/compose?to=jerrym at matrixconsultants.com.au> > > > Subject: APS Direct on s60 5th edition devices > To: <pjsip at lists.pjsip.org<http://in.mc948.mail.yahoo.com/mc/compose?to=pjsip at lists.pjsip.org> > > > Message-ID: <3C8F378104EA402E92795A08F84BB591 at matrix1> > Content-Type: text/plain; charset="us-ascii" > > Hi guys > > > > I'm having an error message when installing apsserver2.sisx on a 5800 > xpress > device (5th ed model). I know I can use VAS but the app is actually > targeting s60 3rd and 5th ed models. > > The error message is "application not compatible with phone" if I proceed > with installation the app still works fine. its just the error message I'm > trying to get rid of. > > Does anyone have a solution or workaround? > > > > Regards > > > > Jerry > > > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/attachments/20091126/c819a6b6/attachment-0001.html > > > > ------------------------------ > > Message: 2 > Date: Thu, 26 Nov 2009 10:54:57 +0700 > From: Benny Prijono <bennylp@xxxxxxxxx<http://in.mc948.mail.yahoo.com/mc/compose?to=bennylp at teluu.com> > > > Subject: Version 1.5 is released > To: pjsip list <pjsip at lists.pjsip.org<http://in.mc948.mail.yahoo.com/mc/compose?to=pjsip at lists.pjsip.org> > > > Message-ID: > <49a4be80911251954j1ed71529tba57b1dc7dfedad8 at mail.gmail.com<http://in.mc948.mail.yahoo.com/mc/compose?to=49a4be80911251954j1ed71529tba57b1dc7dfedad8 at mail.gmail.com> > > > Content-Type: text/plain; charset=ISO-8859-1 > > Please see http://blog.pjsip.org for more detailed info. > > As usual, many many thanks for all the comments, questions, > suggestions, bug reports, and patches. Keep them coming! (and I'll try > to keep up with them as much as I can :) > > -- > Best regards, > > Benny > > > > ------------------------------ > > Message: 3 > Date: Thu, 26 Nov 2009 13:48:11 +0700 > From: Benny Prijono <bennylp@xxxxxxxxx<http://in.mc948.mail.yahoo.com/mc/compose?to=bennylp at teluu.com> > > > Subject: Re: SDP negotiation: Call hold problems > To: pjsip list <pjsip at lists.pjsip.org<http://in.mc948.mail.yahoo.com/mc/compose?to=pjsip at lists.pjsip.org> > > > Message-ID: > <49a4be80911252248y26cb1048n7a4a8932690b4208 at mail.gmail.com<http://in.mc948.mail.yahoo.com/mc/compose?to=49a4be80911252248y26cb1048n7a4a8932690b4208 at mail.gmail.com> > > > Content-Type: text/plain; charset=ISO-8859-1 > > On Wed, Nov 25, 2009 at 10:44 PM, Rafael Maia <rmaia_lcm at hotmail.com<http://in.mc948.mail.yahoo.com/mc/compose?to=rmaia_lcm at hotmail.com>> > wrote: > > Hi, > > i am having problems debugging an SDP negotiation related to call hold. > > > > I receive a an INVITE with the following lines of SDP from an unknown > user > > agent: > > > > ... > > a=sendonly > > m=audio 36884 RTP/AVP 8 101 > > c=IN IP4 10.184.13.134 > > ... > > > > > > PJSIP replies incorrectly with a 200 OK "sendrecv": > > > > ... > > m=audio 57928 RTP/AVP 8 101 > > a=rtpmap:8 PCMA/8000 > > a=sendrecv > > ... > > > > The "sendonly" is replied with a "sendrecv". > > According to RFC 4566 (5. SDP Specification, page 10), if a "a=sendonly" > is > > put at a session level it affects all media sessions ("m="). > > > > Can anyone tell me if PJSIP supports the "a=sendonly" at session level ? > > > > We support call hold with sendonly/recvonly. As usual, to find out > what the problem is, please state the PJSIP version that you're using > and send us the log. > > Cheers > Benny > > > > ------------------------------ > > Message: 4 > Date: Thu, 26 Nov 2009 09:21:53 +0100 > From: Italo Andrea Lisi <andreablade@xxxxxxxxx<http://in.mc948.mail.yahoo.com/mc/compose?to=andreablade at gmail.com> > > > Subject: Re: Version 1.5 is released > To: pjsip list <pjsip at lists.pjsip.org<http://in.mc948.mail.yahoo.com/mc/compose?to=pjsip at lists.pjsip.org> > > > Message-ID: > <58abd20911260021q483ba146y9b1b20b7c0e642be at mail.gmail.com<http://in.mc948.mail.yahoo.com/mc/compose?to=58abd20911260021q483ba146y9b1b20b7c0e642be at mail.gmail.com> > > > Content-Type: text/plain; charset=ISO-8859-1 > > Thanks to you Benny.. great work on project progress, > many thanks :-) > > > Andrea > > > > 2009/11/26 Benny Prijono <bennylp at teluu.com<http://in.mc948.mail.yahoo.com/mc/compose?to=bennylp at teluu.com> > >: > > Please see http://blog.pjsip.org for more detailed info. > > > > As usual, many many thanks for all the comments, questions, > > suggestions, bug reports, and patches. Keep them coming! (and I'll try > > to keep up with them as much as I can :) > > > > -- > > Best regards, > > > > ?Benny > > > > _______________________________________________ > > Visit our blog: http://blog.pjsip.org > > > > pjsip mailing list > > pjsip at lists.pjsip.org<http://in.mc948.mail.yahoo.com/mc/compose?to=pjsip at lists.pjsip.org> > > http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org > > > > > > ------------------------------ > > Message: 5 > Date: Thu, 26 Nov 2009 14:09:27 +0000 > From: Rafael Maia <rmaia_lcm@xxxxxxxxxxx<http://in.mc948.mail.yahoo.com/mc/compose?to=rmaia_lcm at hotmail.com> > > > Subject: Re: SDP negotiation: Call hold problems > To: <pjsip at lists.pjsip.org<http://in.mc948.mail.yahoo.com/mc/compose?to=pjsip at lists.pjsip.org> > > > Message-ID: <BAY119-W36632A1DD7921E328905A7849B0 at phx.gbl<http://in.mc948.mail.yahoo.com/mc/compose?to=BAY119-W36632A1DD7921E328905A7849B0 at phx.gbl> > > > Content-Type: text/plain; charset="iso-8859-1" > > > Hi, > > i am using version 1.0. > > I already identified and fixed the problem. > > > > According to RFC 4566 (5. SDP Specification, page 10), if we put the > "a=sendonly" before any media line (like "m=audio"), it is at session level > and it affects all media lines. > > > > So the following: > > ... > > a=sendonly > > m=audio ..... > ... > m=video ... > > ... > > > > Is the same as: > > ... > > m=audio ... > a=sendonly > > ... > > m=video ... > > a=sendonly > > ... > > > > I did not check recent versions, but PJSIP 1.0 is not handling correctly > the "a=sendonly" before any "m=audio". > > In order to fix this i changed the function "update_media_direction" of > sdp_neg.c. Every time a "a=sendonly" appears before any "m=audio", i remove > it and put it in all "m=audio" that does not have the "a=sendonly". > > (When i say "a=sendonly" i mean any of the following values: "a=sendrecv", > "a=sendonly", "a=recvonly" or "a=inactive") > > > > My solution is not the best one, but i can provide the patch if requested. > > > > cheers, > > > > Rafael Maia > > > > > > > > > Date: Thu, 26 Nov 2009 13:48:11 +0700 > > From: bennylp@xxxxxxxxx<http://in.mc948.mail.yahoo.com/mc/compose?to=bennylp at teluu.com> > > To: pjsip at lists.pjsip.org<http://in.mc948.mail.yahoo.com/mc/compose?to=pjsip at lists.pjsip.org> > > Subject: Re: SDP negotiation: Call hold problems > > > > On Wed, Nov 25, 2009 at 10:44 PM, Rafael Maia <rmaia_lcm at hotmail.com<http://in.mc948.mail.yahoo.com/mc/compose?to=rmaia_lcm at hotmail.com>> > wrote: > > > Hi, > > > i am having problems debugging an SDP negotiation related to call hold. > > > > > > I receive a an INVITE with the following lines of SDP from an unknown > user > > > agent: > > > > > > ... > > > a=sendonly > > > m=audio 36884 RTP/AVP 8 101 > > > c=IN IP4 10.184.13.134 > > > ... > > > > > > > > > PJSIP replies incorrectly with a 200 OK "sendrecv": > > > > > > ... > > > m=audio 57928 RTP/AVP 8 101 > > > a=rtpmap:8 PCMA/8000 > > > a=sendrecv > > > ... > > > > > > The "sendonly" is replied with a "sendrecv". > > > According to RFC 4566 (5. SDP Specification, page 10), if a > "a=sendonly" is > > > put at a session level it affects all media sessions ("m="). > > > > > > Can anyone tell me if PJSIP supports the "a=sendonly" at session level > ? > > > > > > > We support call hold with sendonly/recvonly. As usual, to find out > > what the problem is, please state the PJSIP version that you're using > > and send us the log. > > > > Cheers > > Benny > > > > _______________________________________________ > > Visit our blog: http://blog.pjsip.org > > > > pjsip mailing list > > pjsip at lists.pjsip.org<http://in.mc948.mail.yahoo.com/mc/compose?to=pjsip at lists.pjsip.org> > > http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org > > _________________________________________________________________ > Hotmail: Trusted email with powerful SPAM protection. > http://clk.atdmt.com/GBL/go/177141665/direct/01/ > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/attachments/20091126/db4863f9/attachment-0001.html > > > > ------------------------------ > > _______________________________________________ > pjsip mailing list > pjsip at lists.pjsip.org<http://in.mc948.mail.yahoo.com/mc/compose?to=pjsip at lists.pjsip.org> > http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org > > > End of pjsip Digest, Vol 27, Issue 71 > ************************************* > > > ------------------------------ > The INTERNET now has a personality. YOURS! See your Yahoo! Homepage<http://in.rd.yahoo.com/tagline_yyi_1/*http://in.yahoo.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 > > -- ??? ?????? ??: 050-3930056 nir.elkayam at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/attachments/20091127/b8550930/attachment-0001.html>
