You can subscribe to this list here.
2005 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
(12) |
Sep
(63) |
Oct
(65) |
Nov
(65) |
Dec
(20) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2006 |
Jan
(43) |
Feb
(73) |
Mar
(81) |
Apr
(89) |
May
(151) |
Jun
(125) |
Jul
(60) |
Aug
(79) |
Sep
(152) |
Oct
(94) |
Nov
(83) |
Dec
(46) |
2007 |
Jan
(103) |
Feb
(164) |
Mar
(122) |
Apr
(73) |
May
(93) |
Jun
(80) |
Jul
(80) |
Aug
(56) |
Sep
(61) |
Oct
(122) |
Nov
(86) |
Dec
(37) |
2008 |
Jan
(105) |
Feb
(94) |
Mar
(62) |
Apr
(88) |
May
(32) |
Jun
(62) |
Jul
(59) |
Aug
(67) |
Sep
(89) |
Oct
(46) |
Nov
(83) |
Dec
(72) |
2009 |
Jan
(157) |
Feb
(127) |
Mar
(116) |
Apr
(47) |
May
(48) |
Jun
(49) |
Jul
(29) |
Aug
(20) |
Sep
(48) |
Oct
(21) |
Nov
(18) |
Dec
(24) |
2010 |
Jan
(41) |
Feb
(22) |
Mar
(42) |
Apr
(16) |
May
(8) |
Jun
(23) |
Jul
(54) |
Aug
(80) |
Sep
(29) |
Oct
(16) |
Nov
(21) |
Dec
(28) |
2011 |
Jan
(51) |
Feb
(14) |
Mar
(42) |
Apr
(40) |
May
(30) |
Jun
(30) |
Jul
(19) |
Aug
(26) |
Sep
(12) |
Oct
(14) |
Nov
(7) |
Dec
(7) |
2012 |
Jan
(3) |
Feb
(12) |
Mar
(20) |
Apr
(1) |
May
(8) |
Jun
(1) |
Jul
(3) |
Aug
(3) |
Sep
(6) |
Oct
|
Nov
(3) |
Dec
(6) |
2013 |
Jan
(2) |
Feb
(2) |
Mar
(19) |
Apr
(6) |
May
(7) |
Jun
(32) |
Jul
(2) |
Aug
(12) |
Sep
(1) |
Oct
(3) |
Nov
(32) |
Dec
|
2014 |
Jan
|
Feb
(2) |
Mar
(1) |
Apr
(6) |
May
(5) |
Jun
(11) |
Jul
(11) |
Aug
(33) |
Sep
(12) |
Oct
(1) |
Nov
(2) |
Dec
(7) |
2015 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(2) |
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2016 |
Jan
(8) |
Feb
(6) |
Mar
|
Apr
|
May
(11) |
Jun
(1) |
Jul
|
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
|
2017 |
Jan
|
Feb
(1) |
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
(9) |
Aug
|
Sep
(1) |
Oct
(2) |
Nov
|
Dec
(1) |
2018 |
Jan
(1) |
Feb
|
Mar
(2) |
Apr
|
May
|
Jun
|
Jul
(2) |
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
2019 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2020 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2021 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
(1) |
2024 |
Jan
|
Feb
|
Mar
|
Apr
(3) |
May
|
Jun
|
Jul
|
Aug
|
Sep
(2) |
Oct
|
Nov
|
Dec
|
From: Andreas W. <a.w...@ya...> - 2024-09-03 06:37:34
|
On 02.09.24 11:59, Souradeep Bera wrote: > Hello, > I need to pass some custom headers from Freeswitch in the 200 OK > response sent for an incoming UPDATE request. But I think the sofia > sip stack is automatically sending the response, not even allowing me > to add any custom headers from mod_sofia. Is there anyway I can > achieve this? > My SIP flow is something like > > Freeswitch Remote Trunk > INVITE ---------> > <---------- 100 (INVITE) > <---------- 183 (INVITE) > <---------- UPDATE > 200 (UPDATE). ----------> > <---------- 200 (INVITE) > ACK ------------> > > I require custom headers in the 200 OK sent from Freeswitch to the > remote trunk for the update request > Hey there, I think you'd have to ask on the Freeswitch mailing list/forum whether that is possible from within Freeswitch. This list is about the SIP stack only, though it's pretty dead nowadays. Best regards, Andreas |
From: Souradeep B. <sou...@gm...> - 2024-09-02 10:00:08
|
Hello, I need to pass some custom headers from Freeswitch in the 200 OK response sent for an incoming UPDATE request. But I think the sofia sip stack is automatically sending the response, not even allowing me to add any custom headers from mod_sofia. Is there anyway I can achieve this? My SIP flow is something like Freeswitch Remote Trunk INVITE ---------> <---------- 100 (INVITE) <---------- 183 (INVITE) <---------- UPDATE 200 (UPDATE). ----------> <---------- 200 (INVITE) ACK ------------> I require custom headers in the 200 OK sent from Freeswitch to the remote trunk for the update request |
From: Ogogon !!! <og...@og...> - 2024-04-15 01:49:12
|
15.04.2024 02:38, Steve Underwood wrote: > FreeSwitch is built on Sofia-SIP. The most up to date Sofia code is in > their git repo. Dear Steve! I am very grateful for your answer, although unfortunately your answer was not on the question what I asked. I know where you can find the current Sofia-SIP distribution, I even know several places. (In the same ports of FreeBSD it is always present fresh and ready for use.) But I don’t know where the developers who use this SIP stack communicate with each other. So that you can find out news, ask a question, ask for advice. I don't know of any forum or chat dedicated to Sofia-SIP. Anticipating a possible recommendation, I will say that the idea of turning to resources related to FreeSwitch is weak and unpromising. The new leaders of the FreeSWITCH project, for unknown reasons, closed the old freeswitch.org forum, which more or less provided community communications. The new forum is empty and requires a bunch of personal data from the participant. It’s not community members who answer on the new forum, but very few SignalWare employees, three weeks later, and without yet understanding the meaning of the question. If you don't mind, I'll ask you a question. Perhaps you can answer. I have always used PJSIP, and now I decided to look into Sofia-SIP to expand my horizons and practical skills. In addition, colleagues told me that if I write my own network daemon that actively uses posix threads, then Sofia-SIP is preferable. My platform is FreeBSD. Without X.org. I installed Sofia-SIP from ports and I'm sure it installed correctly. To look at a working simple application that uses Sofia-SIP, I compiled the sofsip-cli-0.16 package without any problems. Unfortunately, the application does not want to start. That's what it says. > ogogon@devel:/usr/local/src/sofsip-cli-0.16/src# ./sofsip_cli > ** Message: 03:34:42.662: Selecting media implementation: dummy > > (sofsip_cli:91700): GLib-WARNING **: 03:34:49.275: > ../glib/gmain.c:2375: ref_count == 0, but source was still attached to > a context! > > ogogon@devel:/usr/local/src/sofsip-cli-0.16/src# What might he not like and how can I please him? > Steve Ogogon. |
From: Steve U. <cop...@gm...> - 2024-04-14 23:38:41
|
On 14/04/2024 22:36, Ogogon !!! wrote: > Colleagues, please tell me, is there now any really living community > of VoIP developers, who using the Sofia-SIP stack? > > Sincerely, > Ogogon. FreeSwitch is built on Sofia-SIP. The most up to date Sofia code is in their git repo. Steve |
From: Ogogon !!! <og...@og...> - 2024-04-14 21:49:26
|
Colleagues, please tell me, is there now any really living community of VoIP developers, who using the Sofia-SIP stack? Sincerely, Ogogon. |
From: Davide L. <da...@gm...> - 2021-12-07 11:58:04
|
Hi, anyone has noticed about a memory leak in receiving a in-dialog sip options in version 1.12.11 and other newer branches ? If so, please let me know if it was fixed. Best regards. Davide Lampugnani |
From: Olaf A. B. <ola...@we...> - 2021-08-27 11:41:34
|
<html> <head> <meta http-equiv="content-type" content="text/html; charset=UTF-8"> </head> <body text="#000000" bgcolor="#FFFFFF"> Hi Sofia-Sip experts,<br> <br> I am using Sofia-Sip for parsing complex SIP messages as a pre-processing for the codecs in our ETSI TTCN test suites. It works perfectly!<br> <br> The purpose of this mail is to ask whether it is possible to change following code which results in nasty compiler warnings when compiled with gcc -Wall.<br> <br> The culprit code is in msg/sofia-sip/msg_parser.h around line 272:<br> <br> #define MSG_PARAMS_NUM(n) (((n) + MSG_N_PARAMS - 1) & (size_t)(0 - MSG_N_PARAMS))<br> <br> I changed this into:<br> #define MSG_PARAMS_NUM(n) ((n) + MSG_N_PARAMS - 1)<br> <br> and it works fine for me without nasty compiler warnings.<br> <br> Regards,<br> Olaf Alejandro<br> </body> </html> |
From: Ogogon !!! <og...@og...> - 2020-02-16 23:41:14
|
Greetings, colleagues! On the "Sofia-SIP Library" site, there is a "Developing with Sofia-SIP" page (http://sofia-sip.sourceforge.net/development.html). The page has a "Getting started - Info for new developers" section, and it has a link "SofiaTutorial wiki page - Tutorial showing how to develop a simple application". Undoubtedly, this is a very important and interesting section. It is very relevant for anyone who would like to understand programming with using the "Sofia-SIP" library. But alas, there is one unpleasant detail. This link points to the very page on which it is placed (http://sofia-sip.sourceforge.net/development.html). What does this mean? Is this a web designer mistake? Subtle developer humor? Over the years of the successful existence of the library, no one considered it necessary to create this once-planned section? *Tell me, please, is there this information and how to get acquainted with it?* Thanks in advance, Ogogon. |
From: gilles D. S. <gil...@ya...> - 2019-01-03 22:00:12
|
Hello Community, I am trying to implement something with Sofia SIP using VS 2017.Actually I get a lot of Issues. Can Someone help to solve? May be a patch or some hints? I thank you in Advance Kind Regards Gilles |
From: Harish D. <har...@gm...> - 2018-10-09 06:21:17
|
Hello, I am using the sofia-sip library for SUBSCRIBE and NOTIFY messages.The problem here is When i am putting load of subscribe requests, the memory goes to 1.5 megabytes and stays there even if i put the load again with less time difference.. However If i put the load after 1 hour the memory increasing from 1.5 to high. I am a beginner to the Sofia-sip...is there anything i am missing here? Why the memory increasing after 1 hour or so only? Thanks and regards, HarishKumar Dubakula |
From: Grygoriy D. <meg...@gm...> - 2018-07-26 11:33:52
|
Good day, i have encoutered a problem witn an invite parsing sent to sofia lib. Looks like it does not like the following syntax a=rtpmap:8 PCMA/8000/1 The call is refused with the reason 400 bad description, a call is accepted if the rtpmap does not have /1 at the end: a=rtpmap:8 PCMA/8000 As per rfc a=rtpmap:<payload type> <encoding name>/<clock rate> [/<encoding parameters>] Looks like the encoding parameters produce an issue here, encoding parameters are the "channels" you can seem them here: https://www.iana.org/assignments/rtp-parameters/rtp-parameters.xhtml The problem is reproduced on freeswitch and Janus webrtc gateway. The logs i have are not so explicit, so i had to test different scenarios to be sure: soa_set_remote_sdp(static::0x7f54200192d0, (nil), 0x7f542002040a, 583) called nua(0x7f54200102f0): INVITE server: error parsing SDP nua: nua_invite_server_respond: entering tport_tsend(0x7f54200038a0) tpn = UDP/176.222.111.200:5060 tport_resolve addrinfo = 176.222.111.200:5060 tport_by_addrinfo(0x7f54200038a0): not found by name UDP/176.222.111.200:5060 tport_vsend(0x7f54200038a0): 586 bytes of 586 to udp/176.222.111.200:5060 tport_vsend returned 586 nta: sent 400 Bad Session Description for INVITE (780) Any ideas how to solve that ? Gregoriy Dobrovolskyy |
From: Aital, R. <Ravi.Aital@Honeywell.com> - 2018-07-23 06:40:38
|
Hi All, I am trying to receive DTMF using sip_info. I have set NUTAG_APPL_METHOD("INFO") at initialization. I get the nua_i_info callback with status 100. But the tags[] is empty. It doesn't contain the key pressed at the other end. I have verified that the other end is sending SIP-INFO with signal set to the digit key pressed using wireshark. Any suggestions? Regards, Ravi |
From: Chandramouli P <mou...@gm...> - 2018-03-29 06:26:07
|
Hello, Any help would be appreciated. Thank you. Regards, Chandramouli. On Mon, Mar 26, 2018 at 6:02 PM, Chandramouli P <mou...@gm...> wrote: > Hello, > > I tried to get the parameters that should pass to ./configure command > like --build, --host, --target. But, I couldn't find values. Can anybody > explain me how to compile Sofia SIP Stack for Android platform on Ubuntu > 16.04 64-Bit OS for arm, x86, and x64 architectures? > > Thanks in advance. > > Regards, > Chandramouli. > |
From: Chandramouli P <mou...@gm...> - 2018-03-26 12:32:36
|
Hello, I tried to get the parameters that should pass to ./configure command like --build, --host, --target. But, I couldn't find values. Can anybody explain me how to compile Sofia SIP Stack for Android platform on Ubuntu 16.04 64-Bit OS for arm, x86, and x64 architectures? Thanks in advance. Regards, Chandramouli. |
From: Tarik M. <tar...@es...> - 2018-01-23 22:00:39
|
Recently encountered this assertion failure in sip_request_create() when preparing to build an INVITE request and the request-URI is of the form: <user>@<host>:<port> SIP/2.0 The following request-URIs do not have a problem: <user>@<host> SIP/2.0 <user>@<host>;<any text> SIP/2.0 It is just the port specifier that sofia seems to be having trouble parsing, even though it looks to be valid according to RFC-3261 spec. After some digging we found that it fails in _url_d() at: /* Check that port is really numeric or wildcard */ /* Port can be *digit, empty string or "*" */ while (*port >= '0' && *port <= '9') port++; if (port != url->url_port) { if (port[0] != '\0') return -1; } At this point in time, port == "<port> SIP/2.0" . The while loop skips over the digits and stops at the space before SIP/2.0. The next two conditionals pass and function returns -1 which leads to the assertion failure. A working fix for us was to change, if (port[0] != '\0') to, if (port[0] != '\0' && port[0] != ' ' && port[0] != ';') This was in sofia v.1.12.12 . I also cloned the git repo for freeswitch and found that the same issue looks to exist in the sofia code that is help there. -T -- This e-mail transmission, and any documents, files or previous e-mail messages attached to it, may contain confidential information. If you are not the intended recipient, or a person responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, distribution, review, copy or use of any of the information contained in or attached to this message is STRICTLY PROHIBITED. If you have received this transmission in error, please immediately notify the sender by reply e-mail, and destroy the original transmission and its attachments without reading them or saving them to disk. |
From: Harald R. <har...@gm...> - 2017-12-06 09:58:34
|
<html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div>Hi all,</div> <div> </div> <div>I am new to sofia SIP so bear with me pleace if this should be stupid:</div> <div> </div> <div> </div> <div>Two of our SIPP applications (A and B) are supposed to connect to eachother.</div> <div> </div> <div>We set TPTAG_IDLE to 2000 ms and NTATAG_SIP_TIX64 to 8000ms</div> <div> </div> <div>Before our SIP application sends an INVITE to a remote host it does some kind of "SIP port scan" and if successful a "subscriber available" test by sending an OPTIONS request before hand.</div> <div> </div> <div>Now if the host with B running is power cycled, any existing connection is torn down. Now A tries to do the OPTIONS subscriber ping to B which of course fails since B is down. said OPTIONS request</div> <div>results in a secondary tport being created (TCP) and queued in as pending since the transport cannot be established.</div> <div>since the reboot takes longer than 8 secs, the OPTIONS request times out (Timer F) and is removed. The application in this case will start with a periodic port scan on 5060 before sending a new OPTIONS request. The transport however is kept, setting the TPTAG_IDLE does not help since in tport_release() the tport_secondary_timer is not set.</div> <div> <div>Now if the remote host comes up, B sends an INVITE itself, is successful, so far so good.</div> <div> </div> <div>However, upon session setup both sides are expected to exchange INFO messages to set up hgher level configuration parameters. A stillhas a TCP transport to B which is not established,</div> <div>thus the INFO message is queued. if the reboot took sufficiently long enough, the next TCP retransmission is not triggered before the 8 seconds timeout for the INFO request timesout and this in turn</div> <div>leads to a teardown of the corresponding session in A, including sending a BYE to B. Of course this BYE is also not sent to the remote side since the TCP transport is still not established.</div> <div> </div> <div>For now I don't see a way from application level to close/zap the transport on the OPTIONS request timeout explicitly, so I would modify tport_release to set the secondary timer if the port is not connected and no other messages are pending in order to let the timer run into the idle timeout and remove the transport to this remote host.</div> <div> </div> <div>Any suggestions to that?</div> <div> </div> <div>T.I.A.</div> <div> </div> <div>Harry</div> <div> </div> <div> </div> </div></div></body></html> |
From: Andreas E. <an...@ev...> - 2017-10-31 08:21:53
|
Hi, I just added SIP to my PBX project. During debugging I got corrupt UDP frames, which had the SDP body _before_ the SIP header. The problem is caused by aggressive optimization by GCC. Here is the link to a patch that solves this problem: https://github.com/unispeech/unimrcp/issues/168 I suggest to add this patch to the repository, but I am not sure that it is clean. Best regards, Andreas |
From: Antonis T. <ant...@te...> - 2017-10-26 08:03:28
|
Hello, Has anyone come across this issue where specifically for TCP transport Sofia SIP only sends the first REGISTER and then doesn't send any REGISTER refreshes? The exact same scenario works properly for UDP, with the same expiry value. I even tested that with original sofsip-cli sample application in Linux just to make sure it's not our codebase messing things up. Any hints? Thanks in advance -- Antonis Tsakiridis Lead Developer, Mobile SDKs at Telestax www.telestax.com |
From: Antonis T. <ant...@te...> - 2017-09-25 09:14:15
|
Hello again, reaching out to see if you had a look at my draft plan. Best regards, Antonis On Mon, Jul 24, 2017 at 1:00 PM, Antonis Tsakiridis < ant...@te...> wrote: > Hello all, > > Here's a set of steps that come to mind: > > - Move Sofia SIP code to an open source repo. > - I would propose GitHub, as we have been working for it on our OSS > and it provides nice tools for collaboration as well as integrates with > virtually everything we might need. Some examples are Travis for CI, Zenhub > for PM, etc. At this point would be very important to retain history. > - Add CI facilities. > - I would suggest Travis CI that is free for OSS projects. It works > pretty well for Linux projects, and also provides iOS images if we are > interested in cross compilation. I know we do as we use Sofia for iOS. > - Run unit/integration tests as part of CI job. IIRC Sofia SIP > comes with a set of tests, but you guys are probably more knowledgeable on > this > - We can setup CI either for each commit, or for Pull Requests > depending on what we need. > - Potentially store the built libraries somewhere so that they are > available for use. AFAIK Travis CI doesn't provide that sort of > functionality, but we can search around and see what is available. > - Cross-compile for iOS and upload to CocoaPods for easy > distribution to iOS. We can also consider alternatives as CocoaPods are > sometimes difficult to maintain. > > This is a rough list of things that we can build upon, so feel free to > comment as you see fit > > Best regards, > Antonis > > > On Tue, Jul 18, 2017 at 12:51 PM, Antonis Tsakiridis < > ant...@te...> wrote: > >> Ok cool Mike, I can try to come up with a draft of some activities to >> move us in that direction and we can collaborate on that to get things >> going. >> >> Best regards, >> Antonis >> >> On Mon, Jul 17, 2017 at 6:39 PM, Michael Jerris <mi...@je...> wrote: >> >>> Its still on my list…. but still not done. Antonis, yeah, lets >>> coordinate and see if we can figure out what needs to be done to make it >>> happen. >>> >>> Mike >>> >>> On Jul 17, 2017, at 9:14 AM, Antonis Tsakiridis < >>> ant...@te...> wrote: >>> >>> Ok thanks Moises for the useful feedback. I remember I had a discussion >>> with Mike on hosting Sofia source independently of FreeSwitch, but I guess >>> he didn't have time to organize this yet. >>> >>> @Mike, are there any updates on this? >>> >>> I think it would be invaluable to have a single place for Sofia (for >>> example GitHub) where code is buildable and potentially testable (for >>> example using Travis CI). Also with the advent of WebRTC + mobile we could >>> all help in further adoption of Sofia in iOS (using CocoaPods potentially) >>> + Android (potentially using JNI even though JAIN SIP is pretty used in >>> Android world) and make the whole thing modular so that it's more easily >>> usable in many platforms. >>> >>> At Telestax we have already integrated Sofia with iOS and using it with >>> WebRTC for media for quite some time now, so I could definitely help in >>> this effort on my free cycles. >>> >>> Best regards, >>> Antonis >>> >>> On Thu, Jul 13, 2017 at 9:47 PM, Moises Silva <moi...@gm...> >>> wrote: >>> >>>> >>>>> - Can I somehow differentiate commits that have to do with Sofia? >>>>> I see 'mod_sofia' in some commits. Is that it? I guess I could probably >>>>> come up with a git command to only show changes inside libs/sofia-sip, but >>>>> wondering if the Freeswich folks used a convention >>>>> >>>>> The stack proper is in libs/sofia-sip/, all you need is 'git log >>>> libs/sofia-sip' >>>> >>>>> >>>>> - Can I find the last commit before Sofia was merged into >>>>> Freeswitch project? So that I can follow history and see which changes >>>>> where made to Sofia after the merge? Also which version of Sofia was >>>>> Freeswitch basedon? Is it 1.12.11 >>>>> <https://gitorious.org/sofia-sip/sofia-sip?p=sofia-sip:sofia-sip.git;a=shortlog;h=refs/tags/1.12.11> >>>>> ? >>>>> >>>>> No idea. Mike might know. Otherwise, you'll have to follow the git >>>> history and see if there are clues there. >>>> >>>>> >>>>> - If I were to take Sofia from within the Freeswitch project and >>>>> copy it as an independent bundle, would autotools work in >>>>> configuring/making/installing etc? Or have dependencies been introduced >>>>> over time and now Sofia needs to have Freeswitch in order to work? >>>>> >>>>> I'm pretty sure there are no dependencies on FreeSWITCH, so you should >>>> be able to just compile the library alone and use it. >>>> >>> >>> >>> >>> -- >>> Antonis Tsakiridis >>> Lead Developer, Mobile SDKs at Telestax >>> ant...@te... >>> www.telestax.com >>> >>> >>> >> >> >> -- >> Antonis Tsakiridis >> Lead Developer, Mobile SDKs at Telestax >> ant...@te... >> www.telestax.com >> > > > > -- > Antonis Tsakiridis > Lead Developer, Mobile SDKs at Telestax > www.telestax.com > -- Antonis Tsakiridis Lead Developer, Mobile SDKs at Telestax www.telestax.com |
From: Antonis T. <ant...@te...> - 2017-07-24 10:01:05
|
Hello all, Here's a set of steps that come to mind: - Move Sofia SIP code to an open source repo. - I would propose GitHub, as we have been working for it on our OSS and it provides nice tools for collaboration as well as integrates with virtually everything we might need. Some examples are Travis for CI, Zenhub for PM, etc. At this point would be very important to retain history. - Add CI facilities. - I would suggest Travis CI that is free for OSS projects. It works pretty well for Linux projects, and also provides iOS images if we are interested in cross compilation. I know we do as we use Sofia for iOS. - Run unit/integration tests as part of CI job. IIRC Sofia SIP comes with a set of tests, but you guys are probably more knowledgeable on this - We can setup CI either for each commit, or for Pull Requests depending on what we need. - Potentially store the built libraries somewhere so that they are available for use. AFAIK Travis CI doesn't provide that sort of functionality, but we can search around and see what is available. - Cross-compile for iOS and upload to CocoaPods for easy distribution to iOS. We can also consider alternatives as CocoaPods are sometimes difficult to maintain. This is a rough list of things that we can build upon, so feel free to comment as you see fit Best regards, Antonis On Tue, Jul 18, 2017 at 12:51 PM, Antonis Tsakiridis < ant...@te...> wrote: > Ok cool Mike, I can try to come up with a draft of some activities to move > us in that direction and we can collaborate on that to get things going. > > Best regards, > Antonis > > On Mon, Jul 17, 2017 at 6:39 PM, Michael Jerris <mi...@je...> wrote: > >> Its still on my list…. but still not done. Antonis, yeah, lets >> coordinate and see if we can figure out what needs to be done to make it >> happen. >> >> Mike >> >> On Jul 17, 2017, at 9:14 AM, Antonis Tsakiridis < >> ant...@te...> wrote: >> >> Ok thanks Moises for the useful feedback. I remember I had a discussion >> with Mike on hosting Sofia source independently of FreeSwitch, but I guess >> he didn't have time to organize this yet. >> >> @Mike, are there any updates on this? >> >> I think it would be invaluable to have a single place for Sofia (for >> example GitHub) where code is buildable and potentially testable (for >> example using Travis CI). Also with the advent of WebRTC + mobile we could >> all help in further adoption of Sofia in iOS (using CocoaPods potentially) >> + Android (potentially using JNI even though JAIN SIP is pretty used in >> Android world) and make the whole thing modular so that it's more easily >> usable in many platforms. >> >> At Telestax we have already integrated Sofia with iOS and using it with >> WebRTC for media for quite some time now, so I could definitely help in >> this effort on my free cycles. >> >> Best regards, >> Antonis >> >> On Thu, Jul 13, 2017 at 9:47 PM, Moises Silva <moi...@gm...> >> wrote: >> >>> >>>> - Can I somehow differentiate commits that have to do with Sofia? I >>>> see 'mod_sofia' in some commits. Is that it? I guess I could probably come >>>> up with a git command to only show changes inside libs/sofia-sip, but >>>> wondering if the Freeswich folks used a convention >>>> >>>> The stack proper is in libs/sofia-sip/, all you need is 'git log >>> libs/sofia-sip' >>> >>>> >>>> - Can I find the last commit before Sofia was merged into >>>> Freeswitch project? So that I can follow history and see which changes >>>> where made to Sofia after the merge? Also which version of Sofia was >>>> Freeswitch basedon? Is it 1.12.11 >>>> <https://gitorious.org/sofia-sip/sofia-sip?p=sofia-sip:sofia-sip.git;a=shortlog;h=refs/tags/1.12.11> >>>> ? >>>> >>>> No idea. Mike might know. Otherwise, you'll have to follow the git >>> history and see if there are clues there. >>> >>>> >>>> - If I were to take Sofia from within the Freeswitch project and >>>> copy it as an independent bundle, would autotools work in >>>> configuring/making/installing etc? Or have dependencies been introduced >>>> over time and now Sofia needs to have Freeswitch in order to work? >>>> >>>> I'm pretty sure there are no dependencies on FreeSWITCH, so you should >>> be able to just compile the library alone and use it. >>> >> >> >> >> -- >> Antonis Tsakiridis >> Lead Developer, Mobile SDKs at Telestax >> ant...@te... >> www.telestax.com >> >> >> > > > -- > Antonis Tsakiridis > Lead Developer, Mobile SDKs at Telestax > ant...@te... > www.telestax.com > -- Antonis Tsakiridis Lead Developer, Mobile SDKs at Telestax www.telestax.com |
From: Antonis T. <ant...@te...> - 2017-07-18 09:51:21
|
Ok cool Mike, I can try to come up with a draft of some activities to move us in that direction and we can collaborate on that to get things going. Best regards, Antonis On Mon, Jul 17, 2017 at 6:39 PM, Michael Jerris <mi...@je...> wrote: > Its still on my list…. but still not done. Antonis, yeah, lets coordinate > and see if we can figure out what needs to be done to make it happen. > > Mike > > On Jul 17, 2017, at 9:14 AM, Antonis Tsakiridis < > ant...@te...> wrote: > > Ok thanks Moises for the useful feedback. I remember I had a discussion > with Mike on hosting Sofia source independently of FreeSwitch, but I guess > he didn't have time to organize this yet. > > @Mike, are there any updates on this? > > I think it would be invaluable to have a single place for Sofia (for > example GitHub) where code is buildable and potentially testable (for > example using Travis CI). Also with the advent of WebRTC + mobile we could > all help in further adoption of Sofia in iOS (using CocoaPods potentially) > + Android (potentially using JNI even though JAIN SIP is pretty used in > Android world) and make the whole thing modular so that it's more easily > usable in many platforms. > > At Telestax we have already integrated Sofia with iOS and using it with > WebRTC for media for quite some time now, so I could definitely help in > this effort on my free cycles. > > Best regards, > Antonis > > On Thu, Jul 13, 2017 at 9:47 PM, Moises Silva <moi...@gm...> > wrote: > >> >>> - Can I somehow differentiate commits that have to do with Sofia? I >>> see 'mod_sofia' in some commits. Is that it? I guess I could probably come >>> up with a git command to only show changes inside libs/sofia-sip, but >>> wondering if the Freeswich folks used a convention >>> >>> The stack proper is in libs/sofia-sip/, all you need is 'git log >> libs/sofia-sip' >> >>> >>> - Can I find the last commit before Sofia was merged into Freeswitch >>> project? So that I can follow history and see which changes where made to >>> Sofia after the merge? Also which version of Sofia was Freeswitch basedon? >>> Is it 1.12.11 >>> <https://gitorious.org/sofia-sip/sofia-sip?p=sofia-sip:sofia-sip.git;a=shortlog;h=refs/tags/1.12.11> >>> ? >>> >>> No idea. Mike might know. Otherwise, you'll have to follow the git >> history and see if there are clues there. >> >>> >>> - If I were to take Sofia from within the Freeswitch project and >>> copy it as an independent bundle, would autotools work in >>> configuring/making/installing etc? Or have dependencies been introduced >>> over time and now Sofia needs to have Freeswitch in order to work? >>> >>> I'm pretty sure there are no dependencies on FreeSWITCH, so you should >> be able to just compile the library alone and use it. >> > > > > -- > Antonis Tsakiridis > Lead Developer, Mobile SDKs at Telestax > ant...@te... > www.telestax.com > > > -- Antonis Tsakiridis Lead Developer, Mobile SDKs at Telestax ant...@te... www.telestax.com |
From: Michael J. <mi...@je...> - 2017-07-17 16:10:35
|
Its still on my list…. but still not done. Antonis, yeah, lets coordinate and see if we can figure out what needs to be done to make it happen. Mike > On Jul 17, 2017, at 9:14 AM, Antonis Tsakiridis <ant...@te...> wrote: > > Ok thanks Moises for the useful feedback. I remember I had a discussion with Mike on hosting Sofia source independently of FreeSwitch, but I guess he didn't have time to organize this yet. > > @Mike, are there any updates on this? > > I think it would be invaluable to have a single place for Sofia (for example GitHub) where code is buildable and potentially testable (for example using Travis CI). Also with the advent of WebRTC + mobile we could all help in further adoption of Sofia in iOS (using CocoaPods potentially) + Android (potentially using JNI even though JAIN SIP is pretty used in Android world) and make the whole thing modular so that it's more easily usable in many platforms. > > At Telestax we have already integrated Sofia with iOS and using it with WebRTC for media for quite some time now, so I could definitely help in this effort on my free cycles. > > Best regards, > Antonis > > On Thu, Jul 13, 2017 at 9:47 PM, Moises Silva <moi...@gm... <mailto:moi...@gm...>> wrote: > Can I somehow differentiate commits that have to do with Sofia? I see 'mod_sofia' in some commits. Is that it? I guess I could probably come up with a git command to only show changes inside libs/sofia-sip, but wondering if the Freeswich folks used a convention > The stack proper is in libs/sofia-sip/, all you need is 'git log libs/sofia-sip' > Can I find the last commit before Sofia was merged into Freeswitch project? So that I can follow history and see which changes where made to Sofia after the merge? Also which version of Sofia was Freeswitch basedon? Is it 1.12.11 <https://gitorious.org/sofia-sip/sofia-sip?p=sofia-sip:sofia-sip.git;a=shortlog;h=refs/tags/1.12.11>? > No idea. Mike might know. Otherwise, you'll have to follow the git history and see if there are clues there. > If I were to take Sofia from within the Freeswitch project and copy it as an independent bundle, would autotools work in configuring/making/installing etc? Or have dependencies been introduced over time and now Sofia needs to have Freeswitch in order to work? > I'm pretty sure there are no dependencies on FreeSWITCH, so you should be able to just compile the library alone and use it. > > > > -- > Antonis Tsakiridis > Lead Developer, Mobile SDKs at Telestax > ant...@te... <mailto:ant...@te...> > www.telestax.com <http://www.telestax.com/> |
From: Antonis T. <ant...@te...> - 2017-07-17 13:43:37
|
Ok thanks Moises for the useful feedback. I remember I had a discussion with Mike on hosting Sofia source independently of FreeSwitch, but I guess he didn't have time to organize this yet. @Mike, are there any updates on this? I think it would be invaluable to have a single place for Sofia (for example GitHub) where code is buildable and potentially testable (for example using Travis CI). Also with the advent of WebRTC + mobile we could all help in further adoption of Sofia in iOS (using CocoaPods potentially) + Android (potentially using JNI even though JAIN SIP is pretty used in Android world) and make the whole thing modular so that it's more easily usable in many platforms. At Telestax we have already integrated Sofia with iOS and using it with WebRTC for media for quite some time now, so I could definitely help in this effort on my free cycles. Best regards, Antonis On Thu, Jul 13, 2017 at 9:47 PM, Moises Silva <moi...@gm...> wrote: > >> - Can I somehow differentiate commits that have to do with Sofia? I >> see 'mod_sofia' in some commits. Is that it? I guess I could probably come >> up with a git command to only show changes inside libs/sofia-sip, but >> wondering if the Freeswich folks used a convention >> >> The stack proper is in libs/sofia-sip/, all you need is 'git log > libs/sofia-sip' > >> >> - Can I find the last commit before Sofia was merged into Freeswitch >> project? So that I can follow history and see which changes where made to >> Sofia after the merge? Also which version of Sofia was Freeswitch basedon? >> Is it 1.12.11 >> <https://gitorious.org/sofia-sip/sofia-sip?p=sofia-sip:sofia-sip.git;a=shortlog;h=refs/tags/1.12.11> >> ? >> >> No idea. Mike might know. Otherwise, you'll have to follow the git > history and see if there are clues there. > >> >> - If I were to take Sofia from within the Freeswitch project and copy >> it as an independent bundle, would autotools work in >> configuring/making/installing etc? Or have dependencies been introduced >> over time and now Sofia needs to have Freeswitch in order to work? >> >> I'm pretty sure there are no dependencies on FreeSWITCH, so you should be > able to just compile the library alone and use it. > -- Antonis Tsakiridis Lead Developer, Mobile SDKs at Telestax ant...@te... www.telestax.com |
From: Moises S. <moi...@gm...> - 2017-07-13 18:48:20
|
> > > - Can I somehow differentiate commits that have to do with Sofia? I > see 'mod_sofia' in some commits. Is that it? I guess I could probably come > up with a git command to only show changes inside libs/sofia-sip, but > wondering if the Freeswich folks used a convention > > The stack proper is in libs/sofia-sip/, all you need is 'git log libs/sofia-sip' > > - Can I find the last commit before Sofia was merged into Freeswitch > project? So that I can follow history and see which changes where made to > Sofia after the merge? Also which version of Sofia was Freeswitch basedon? > Is it 1.12.11 > <https://gitorious.org/sofia-sip/sofia-sip?p=sofia-sip:sofia-sip.git;a=shortlog;h=refs/tags/1.12.11> > ? > > No idea. Mike might know. Otherwise, you'll have to follow the git history and see if there are clues there. > > - If I were to take Sofia from within the Freeswitch project and copy > it as an independent bundle, would autotools work in > configuring/making/installing etc? Or have dependencies been introduced > over time and now Sofia needs to have Freeswitch in order to work? > > I'm pretty sure there are no dependencies on FreeSWITCH, so you should be able to just compile the library alone and use it. |
From: Dave H. <da...@be...> - 2017-07-12 12:48:28
|
Just as an FYI, I forked sofia a while back from freeswitch, mainly because my use of sofia is heavily nta-based while freeswitch is nua-based, and I needed various enhancements / fixes. Anyone is welcome to use / contribute if they like https://github.com/davehorton/sofia-sip <https://github.com/davehorton/sofia-sip> On Jul 12, 2017, at 8:07 AM, sof...@li... wrote: Send Sofia-sip-devel mailing list submissions to sof...@li... To subscribe or unsubscribe via the World Wide Web, visit https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel or, via email, send a message with subject or body 'help' to sof...@li... You can reach the person managing the list at sof...@li... When replying, please edit your Subject line so it is more specific than "Re: Contents of Sofia-sip-devel digest..." Today's Topics: 1. Re: Sofia SIP 'master' repo (Antonis Tsakiridis) From: Antonis Tsakiridis <ant...@te...> Subject: Re: [Sofia-sip-devel] Sofia SIP 'master' repo Date: July 12, 2017 at 7:53:42 AM EDT To: Moises Silva <moi...@gm...>, Michael Jerris <mi...@je...> Cc: "sof...@li... List" <sof...@li...> Thanks Moises for the quick answer. I found Sofia inside the Freeswitch source, which is great, but I'm wondering about the following: Can I somehow differentiate commits that have to do with Sofia? I see 'mod_sofia' in some commits. Is that it? I guess I could probably come up with a git command to only show changes inside libs/sofia-sip, but wondering if the Freeswich folks used a convention Can I find the last commit before Sofia was merged into Freeswitch project? So that I can follow history and see which changes where made to Sofia after the merge? Also which version of Sofia was Freeswitch basedon? Is it 1.12.11 <https://gitorious.org/sofia-sip/sofia-sip?p=sofia-sip:sofia-sip.git;a=shortlog;h=refs/tags/1.12.11>? If I were to take Sofia from within the Freeswitch project and copy it as an independent bundle, would autotools work in configuring/making/installing etc? Or have dependencies been introduced over time and now Sofia needs to have Freeswitch in order to work? Best regards and thanks in advance, Antonis On Mon, Jul 10, 2017 at 2:48 PM, Moises Silva <moi...@gm... <mailto:moi...@gm...>> wrote: On Mon, Jul 10, 2017 at 6:44 AM, Antonis Tsakiridis <ant...@te... <mailto:ant...@te...>> wrote: Hello, is there a master repo for Sofia SIP that is considered active and current? If so can you share where I can find it? I think libsofia inside the FreeSWITCH git repo si the most up to date. -- Antonis Tsakiridis Lead Developer, Mobile SDKs at Telestax ant...@te... <mailto:ant...@te...> http://www.telestax.com <http://www.telestax.com/> ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot_______________________________________________ Sofia-sip-devel mailing list Sof...@li... https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel |