[OpenSIPS-Users] Opensips 2.x 3.x alpine linux images
Hello, Does anyone know if such package exists and if it exists where can I find it? thanks, -- -- Konrad Malewski -- At Motorola Solutions and our subsidiaries, your privacy is important to us. That is why we have taken appropriate measures to ensure the data you provide to us is kept secure. To learn more about how we process your personal information, how we comply with applicable data protection laws, and care for the security and privacy of your personal data, please review our Privacy Policy <https://www.motorolasolutions.com/en_us/about/privacy-policy.html#privacystatement>. If you have any questions related to data protection and compliance with applicable laws, please contact us at priva...@motorolasolutions.com <mailto:priva...@motorolasolutions.com> ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] Cluster call restore during conference call
Hello, So from Opensips perspective conference call should be all right. What if freeswitch crashes ? Can opensips detect and reinvite all parties ? Or am I correct to assume that there should be separate HA for freeswitch ? On Wed, May 15, 2019 at 1:14 PM Răzvan Crainea wrote: > Hi, Konrad! > > From a proxy POV, a conference is seen as multiple calls going to the > same destination. Therefore, for example, OpenSIPS will see a 3 person > conference as 3 different (and independent) calls/dialogs. If opensips > crashes, after recovery it will restore all 3 dialogs, thuse the entire > conference. > > Best regards, > Răzvan > > On 5/15/19 10:16 AM, Konrad Malewski wrote: > > Hello, > > > > Thanks for your input... :) > > > > I thought that opensips is not conference aware UA so Opensips is > > involved only in initial dialog and all other conference legs are > > managed by asterisk/freeswitch. > > So correct me if I am wrong but In such case when > > a) opensips dies - only initial 2 legs are restored > > b) freeswitch/asterisk dies - there is no way to recover the > > conference as it is anchored somewhere else. > > > > thanks, > > > > On Tue, May 14, 2019 at 4:51 PM Alexey Kazantsev via Users > > mailto:users@lists.opensips.org>> wrote: > > > > It should work. > > > > A conference consists of the same SIP requests and replies > > as any other SIP call. > > > > --- > > BR, Alexey > > > https://urldefense.proofpoint.com/v2/url?u=http-3A__alexeyka.zantsev.com_&d=DwIGaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=Q2-P3NgorS0ZH4_aMeg5NL1og3Rsx6yNgM-aaPfa8xzzIkVlEcHJTs2jlyabbp9e&m=ZnApHbpZ6nEpkcK0sn41GLwwZ694S06HonWP03c3FZE&s=ZBuyJARPSdBSgReETDHX4uKGKZfefnrgIW5waxNkdoM&e= > > ___ > > Users mailing list > > Users@lists.opensips.org <mailto:Users@lists.opensips.org> > > > https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.opensips.org_cgi-2Dbin_mailman_listinfo_users&d=DwIGaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=Q2-P3NgorS0ZH4_aMeg5NL1og3Rsx6yNgM-aaPfa8xzzIkVlEcHJTs2jlyabbp9e&m=ZnApHbpZ6nEpkcK0sn41GLwwZ694S06HonWP03c3FZE&s=rXHRCUanE9A4zYZzlW9QIYovR4x9Po2GptbP8Keld-I&e= > > > > > > > > -- > > -- > > Konrad Malewski > > > > ___ > > Users mailing list > > Users@lists.opensips.org > > > https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.opensips.org_cgi-2Dbin_mailman_listinfo_users&d=DwIGaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=Q2-P3NgorS0ZH4_aMeg5NL1og3Rsx6yNgM-aaPfa8xzzIkVlEcHJTs2jlyabbp9e&m=Iiesh9lx6l77cnuuVcOn3moQdaLrKaCP4SEYamjUsLc&s=dGOs78L5ovqeH9kseDM0UJonkr9WGG-me2EvnJ6998U&e= > > > > -- > Răzvan Crainea > OpenSIPS Core Developer > > https://urldefense.proofpoint.com/v2/url?u=http-3A__www.opensips-2Dsolutions.com&d=DwIGaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=Q2-P3NgorS0ZH4_aMeg5NL1og3Rsx6yNgM-aaPfa8xzzIkVlEcHJTs2jlyabbp9e&m=Iiesh9lx6l77cnuuVcOn3moQdaLrKaCP4SEYamjUsLc&s=U_bBbsKYhaIhB44moDBnBVRjt4ktplg3VcEc_oc_b-c&e= > Meet the OpenSIPS team at the next OpenSIPS Summit: > > https://urldefense.proofpoint.com/v2/url?u=https-3A__www.opensips.org_events&d=DwIGaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=Q2-P3NgorS0ZH4_aMeg5NL1og3Rsx6yNgM-aaPfa8xzzIkVlEcHJTs2jlyabbp9e&m=Iiesh9lx6l77cnuuVcOn3moQdaLrKaCP4SEYamjUsLc&s=Fk-mmZLWEqnWowjed_JT9vqNjlCOnWvBocJ1N4SR9Oc&e= > > ___ > Users mailing list > Users@lists.opensips.org > > https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.opensips.org_cgi-2Dbin_mailman_listinfo_users&d=DwIGaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=Q2-P3NgorS0ZH4_aMeg5NL1og3Rsx6yNgM-aaPfa8xzzIkVlEcHJTs2jlyabbp9e&m=Iiesh9lx6l77cnuuVcOn3moQdaLrKaCP4SEYamjUsLc&s=dGOs78L5ovqeH9kseDM0UJonkr9WGG-me2EvnJ6998U&e= > -- -- Konrad Malewski ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] Cluster call restore during conference call
Hello, Thanks for your input... :) I thought that opensips is not conference aware UA so Opensips is involved only in initial dialog and all other conference legs are managed by asterisk/freeswitch. So correct me if I am wrong but In such case when a) opensips dies - only initial 2 legs are restored b) freeswitch/asterisk dies - there is no way to recover the conference as it is anchored somewhere else. thanks, On Tue, May 14, 2019 at 4:51 PM Alexey Kazantsev via Users < users@lists.opensips.org> wrote: > It should work. > > A conference consists of the same SIP requests and replies > as any other SIP call. > > --- > BR, Alexey > > https://urldefense.proofpoint.com/v2/url?u=http-3A__alexeyka.zantsev.com_&d=DwIGaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=Q2-P3NgorS0ZH4_aMeg5NL1og3Rsx6yNgM-aaPfa8xzzIkVlEcHJTs2jlyabbp9e&m=ZnApHbpZ6nEpkcK0sn41GLwwZ694S06HonWP03c3FZE&s=ZBuyJARPSdBSgReETDHX4uKGKZfefnrgIW5waxNkdoM&e= > ___ > Users mailing list > Users@lists.opensips.org > > https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.opensips.org_cgi-2Dbin_mailman_listinfo_users&d=DwIGaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=Q2-P3NgorS0ZH4_aMeg5NL1og3Rsx6yNgM-aaPfa8xzzIkVlEcHJTs2jlyabbp9e&m=ZnApHbpZ6nEpkcK0sn41GLwwZ694S06HonWP03c3FZE&s=rXHRCUanE9A4zYZzlW9QIYovR4x9Po2GptbP8Keld-I&e= > -- -- Konrad Malewski ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] Cluster call restore during conference call
Hello, If I integrate opensips with asterisk/freeswitch and use clusterer to create opensips HA, will it be able to restore conference calls as well ? if no than what are the options to restore the conference call ? thanks for any hint, -- Konrad Malewski ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] cluster dialog synchronization - 200Ok/180Ringing ?
so if there is like 60 sec after 180ringing and 200ok - during that time this dialog is vulnerable to failover ? On Tue, May 7, 2019 at 3:59 PM Vlad Patrascu wrote: > Hi Konrad, > > The dialog is replicated after the 200 OK is received. > > Regards, > > Vlad Patrascu > OpenSIPS Developerhttp://www.opensips-solutions.com > <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.opensips-2Dsolutions.com&d=DwMDaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=Q2-P3NgorS0ZH4_aMeg5NL1og3Rsx6yNgM-aaPfa8xzzIkVlEcHJTs2jlyabbp9e&m=Fj_nyRYH9UHn3Dx85pRDIF29KpGk8e8xgDGDS9NQfe0&s=bj9ef4taHUsG059fUfifgY1l66gNZXwXrF5Oj5x83-Y&e=> > > On 05/07/2019 04:43 PM, Konrad Malewski wrote: > > Hello, > > I have a question regarding dialog synchronization in opensips cluster. > > Does dialog synchronization happen after initial transaction is complete > or before ? (When backup is able to take over failed active node?) > > I am asking because it may be a lot of time after 180Ringing before 200Ok > arrives. > > thanks, > -- > Konrad Malewski > > > ___ > Users mailing > listUsers@lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users > > <https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.opensips.org_cgi-2Dbin_mailman_listinfo_users&d=DwMDaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=Q2-P3NgorS0ZH4_aMeg5NL1og3Rsx6yNgM-aaPfa8xzzIkVlEcHJTs2jlyabbp9e&m=Fj_nyRYH9UHn3Dx85pRDIF29KpGk8e8xgDGDS9NQfe0&s=zNjisP_DWAX5QHdaLvr5SOM8oZ1MfdElR_5vfGOJ4ls&e=> > > > ___ > Users mailing list > Users@lists.opensips.org > > https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.opensips.org_cgi-2Dbin_mailman_listinfo_users&d=DwIGaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=Q2-P3NgorS0ZH4_aMeg5NL1og3Rsx6yNgM-aaPfa8xzzIkVlEcHJTs2jlyabbp9e&m=Fj_nyRYH9UHn3Dx85pRDIF29KpGk8e8xgDGDS9NQfe0&s=zNjisP_DWAX5QHdaLvr5SOM8oZ1MfdElR_5vfGOJ4ls&e= > -- -- Konrad Malewski ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] cluster dialog synchronization - 200Ok/180Ringing ?
Hello, I have a question regarding dialog synchronization in opensips cluster. Does dialog synchronization happen after initial transaction is complete or before ? (When backup is able to take over failed active node?) I am asking because it may be a lot of time after 180Ringing before 200Ok arrives. thanks, -- Konrad Malewski ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] opensips3.0/dev requires huge amount of memory and crashes
fm_malloc is first error: Apr 23 12:11:27 [50] INFO:core:mod_init: initializing UDP-plain protocol Apr 23 12:11:27 [50] INFO:dialog:mod_init: Dialog module - initializing Apr 23 12:11:27 [50] INFO:core:evi_publish_event: Registered event Apr 23 12:11:27 [50] INFO:topology_hiding:mod_init: initializing... Apr 23 12:11:27 [50] INFO:rest_client:mod_init: Module initialized! Apr 23 12:11:27 [50] NOTICE:signaling:mod_init: initializing module ... Apr 23 12:11:27 [50] ERROR:core:fm_malloc: not enough free shm memory (62949808 bytes left, need 2824938474944), please increase the "-m" command line parameter! Apr 23 12:11:27 [50] INFO:core:fm_malloc: attempting defragmentation... Apr 23 12:11:27 [50] INFO:core:fm_malloc: unable to alloc a big enough fragment! Apr 23 12:11:27 [50] ERROR:core:init_multi_proc_support: out of memory Apr 23 12:11:27 [50] ERROR:core:main: failed to init multi-proc support Apr 23 12:11:27 [50] INFO:core:cleanup: cleanup Apr 23 12:11:27 [50] NOTICE:event_datagram:destroy: destroy module ... Apr 23 12:11:27 [50] NOTICE:core:main: Exiting TCP alone is the problem TCP + UDP works fine UDP alone works fine On Tue, Apr 23, 2019 at 12:49 PM Bogdan-Andrei Iancu wrote: > Is there any following error / warning log ? Or you get only that single > err line ?? > > And you get that error by using TCP without UDP ? using TCP + UDP is fine ? > > Regards, > > Bogdan-Andrei Iancu > > OpenSIPS Founder and Developer > https://www.opensips-solutions.com > <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.opensips-2Dsolutions.com&d=DwMDaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=Q2-P3NgorS0ZH4_aMeg5NL1og3Rsx6yNgM-aaPfa8xzzIkVlEcHJTs2jlyabbp9e&m=_bnCF3cXINafd9aW9lAOcWFgfAH52iW85NTp0KIOfT0&s=XKZhpHD685GLGMMHTjiSBH0ZGuo5TJxTty8a14LL6Gs&e=> > OpenSIPS Summit 2019 > https://www.opensips.org/events/Summit-2019Amsterdam/ > <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.opensips.org_events_Summit-2D2019Amsterdam_&d=DwMDaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=Q2-P3NgorS0ZH4_aMeg5NL1og3Rsx6yNgM-aaPfa8xzzIkVlEcHJTs2jlyabbp9e&m=_bnCF3cXINafd9aW9lAOcWFgfAH52iW85NTp0KIOfT0&s=_xIKaXTeDJ4umSkuenOzE3L96WICDmUstpWFDDB2H5U&e=> > > On 04/23/2019 01:08 PM, Konrad Malewski wrote: > > I checked just now. > It sufficient to comment out UDP listening port and leave just TCP > > /// > #listen=udp:172.17.0.2:5060 > <https://urldefense.proofpoint.com/v2/url?u=http-3A__172.17.0.2-3A5060&d=DwMDaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=Q2-P3NgorS0ZH4_aMeg5NL1og3Rsx6yNgM-aaPfa8xzzIkVlEcHJTs2jlyabbp9e&m=_bnCF3cXINafd9aW9lAOcWFgfAH52iW85NTp0KIOfT0&s=FVZCOP9baSEN4VjWUe833t3Zyie_i6cWX7VgmEOWT_k&e=> > # CUSTOMIZE ME > listen=tcp:172.17.0.2:5060 > <https://urldefense.proofpoint.com/v2/url?u=http-3A__172.17.0.2-3A5060&d=DwMDaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=Q2-P3NgorS0ZH4_aMeg5NL1og3Rsx6yNgM-aaPfa8xzzIkVlEcHJTs2jlyabbp9e&m=_bnCF3cXINafd9aW9lAOcWFgfAH52iW85NTp0KIOfT0&s=FVZCOP9baSEN4VjWUe833t3Zyie_i6cWX7VgmEOWT_k&e=> > # CUSTOMIZE ME > /// > > ERROR:core:fm_malloc: not enough free shm memory (63093216 bytes left, > need 8843713106240), please increase the "-m" command line parameter! > > > On Tue, Apr 23, 2019 at 9:00 AM Bogdan-Andrei Iancu > wrote: > >> Hi Konrad, >> >> For sure there was something wrong - could you give it a another try with >> latest 3.0 beta ? >> >> Regards, >> >> Bogdan-Andrei Iancu >> >> OpenSIPS Founder and Developer >> https://www.opensips-solutions.com >> <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.opensips-2Dsolutions.com&d=DwMDaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=Q2-P3NgorS0ZH4_aMeg5NL1og3Rsx6yNgM-aaPfa8xzzIkVlEcHJTs2jlyabbp9e&m=j0LqP8JXCUhyWZJz9QYkuiQ6yY7HWS3ozNR18T-FC2o&s=xWCGHrJVYpMR16Pm1dXvRy317O8Qia-1uLZI3zWSkHs&e=> >> OpenSIPS Summit 2019 >> https://www.opensips.org/events/Summit-2019Amsterdam/ >> <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.opensips.org_events_Summit-2D2019Amsterdam_&d=DwMDaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=Q2-P3NgorS0ZH4_aMeg5NL1og3Rsx6yNgM-aaPfa8xzzIkVlEcHJTs2jlyabbp9e&m=j0LqP8JXCUhyWZJz9QYkuiQ6yY7HWS3ozNR18T-FC2o&s=S1JpCMZ0JNXjz9g8AUgBs8lUV76bDYTGPI5ohs7IrSM&e=> >> >> On 04/08/2019 12:38 PM, Konrad Malewski wrote: >> >> Hello, >> >> If I enabled TCP only as only protocol, opensips3 starts crashing at >> startup with following error: >> >> ERROR:core:fm_malloc: not enough free shm memory (62949296 bytes left, >> need 17109592486272), please increase the "-m" command line parameter! >> >> The amount of "need" is different every time I restart opensips >> >>
[OpenSIPS-Users] b2b top hiding with opensips 3.0.0-beta gives "Wrong Scenary ID"
Hello,
I switched to opensips3 and b2b internal scenario stopped working:
Apr 23 10:33:29 [55] ERROR:b2b_logic:fixup_b2b_logic: Wrong Scenary ID. No
scenario with this ID [�Ͷ�s]
Apr 23 10:33:29 [55] ERROR:core:fix_cmd: Fixup failed for param [1]
Apr 23 10:33:29 [55] ERROR:core:fix_actions: Failed to fix command
Apr 23 10:33:29 [55] ERROR:core:fix_actions: fixing failed (code=-1) at
/etc/opensips/opensips.cfg:185
Apr 23 10:33:29 [55] ERROR:core:main: failed to fix configuration with err
code -1
Line 185 of configuration contains only
-> b2b_init_request("top hiding");
did scenario name changed ?
--
--
Konrad Malewski
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] opensips3.0/dev requires huge amount of memory and crashes
I checked just now. It sufficient to comment out UDP listening port and leave just TCP /// #listen=udp:172.17.0.2:5060 # CUSTOMIZE ME listen=tcp:172.17.0.2:5060 # CUSTOMIZE ME /// ERROR:core:fm_malloc: not enough free shm memory (63093216 bytes left, need 8843713106240), please increase the "-m" command line parameter! On Tue, Apr 23, 2019 at 9:00 AM Bogdan-Andrei Iancu wrote: > Hi Konrad, > > For sure there was something wrong - could you give it a another try with > latest 3.0 beta ? > > Regards, > > Bogdan-Andrei Iancu > > OpenSIPS Founder and Developer > https://www.opensips-solutions.com > <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.opensips-2Dsolutions.com&d=DwMDaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=Q2-P3NgorS0ZH4_aMeg5NL1og3Rsx6yNgM-aaPfa8xzzIkVlEcHJTs2jlyabbp9e&m=j0LqP8JXCUhyWZJz9QYkuiQ6yY7HWS3ozNR18T-FC2o&s=xWCGHrJVYpMR16Pm1dXvRy317O8Qia-1uLZI3zWSkHs&e=> > OpenSIPS Summit 2019 > https://www.opensips.org/events/Summit-2019Amsterdam/ > <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.opensips.org_events_Summit-2D2019Amsterdam_&d=DwMDaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=Q2-P3NgorS0ZH4_aMeg5NL1og3Rsx6yNgM-aaPfa8xzzIkVlEcHJTs2jlyabbp9e&m=j0LqP8JXCUhyWZJz9QYkuiQ6yY7HWS3ozNR18T-FC2o&s=S1JpCMZ0JNXjz9g8AUgBs8lUV76bDYTGPI5ohs7IrSM&e=> > > On 04/08/2019 12:38 PM, Konrad Malewski wrote: > > Hello, > > If I enabled TCP only as only protocol, opensips3 starts crashing at > startup with following error: > > ERROR:core:fm_malloc: not enough free shm memory (62949296 bytes left, > need 17109592486272), please increase the "-m" command line parameter! > > The amount of "need" is different every time I restart opensips > > ERROR:core:fm_malloc: not enough free shm memory (62949296 bytes left, > need 8689571889280), please increase the "-m" command line parameter! > > when I enable udp and add appropriate listen=udp:IP:PORT entry problem > goes away. > > The issue is odd, so what am I doing wrong? Maybe this is a bug ? > > -- > -- > Konrad Malewski > > > ___ > Users mailing > listUsers@lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users > > <https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.opensips.org_cgi-2Dbin_mailman_listinfo_users&d=DwMDaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=Q2-P3NgorS0ZH4_aMeg5NL1og3Rsx6yNgM-aaPfa8xzzIkVlEcHJTs2jlyabbp9e&m=j0LqP8JXCUhyWZJz9QYkuiQ6yY7HWS3ozNR18T-FC2o&s=3-PY2shO5Q9SB6W7HquVvtqxXkTdsl4Hwt_33Nkkmg8&e=> > > > -- -- Konrad Malewski ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] how to migrate statistics to 3.x ?
Thanks.
I found the github repository.
Are you planning to integrate this into package (I am using debian) ?
Currently opensips depends on python (which is 2.7) but opensips-cli
requires python3
On Fri, Apr 12, 2019 at 10:42 AM Vlad Patrascu wrote:
> The opensipsctl tool does not work anymore with the get_statistics command
> and will be dropped soon anyway. Please try the new opensips-cli tool.
>
> Regards,
>
> Vlad Patrascu
> OpenSIPS Developerhttp://www.opensips-solutions.com
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.opensips-2Dsolutions.com&d=DwMDaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=Q2-P3NgorS0ZH4_aMeg5NL1og3Rsx6yNgM-aaPfa8xzzIkVlEcHJTs2jlyabbp9e&m=e1cMNheMB6S0UOeY_WdEZXrfA9R8IF3RbLt4oSfkotM&s=368ZylOnjT2wshn1FXVCpUoc03KGvdRujH7v5TjlNwk&e=>
>
> On 04/11/2019 12:54 PM, Konrad Malewski wrote:
>
> Hello,
>
> I am using 3.0.0-dev version and I am having problem with opensipsctl
> command for statistics:
>
> $opensipsctl fifo get_statistics load-all
> {
>"jsonrpc": "2.0",
>"id": "a7cbfd4e",
>"error": {
> "message": "Invalid params",
> "code": -32602
>}
> }
>
> $opensipsctl fifo get_statistics load:
> {
>"jsonrpc": "2.0",
>"id": "177e12c6",
>"error": {
> "message": "Invalid params",
> "code": -32602
>}
> }
>
> the log says: ERROR:core:get_mi_array_param: Parameter: statistics is not
> an array.
>
> What is the new syntax ?
>
> --
> --
> Konrad Malewski
>
>
> ___
> Users mailing
> listUsers@lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.opensips.org_cgi-2Dbin_mailman_listinfo_users&d=DwMDaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=Q2-P3NgorS0ZH4_aMeg5NL1og3Rsx6yNgM-aaPfa8xzzIkVlEcHJTs2jlyabbp9e&m=e1cMNheMB6S0UOeY_WdEZXrfA9R8IF3RbLt4oSfkotM&s=9MMa6DU1B2Z7PGEmqGlSiVm_ujL4HqvpXby2HUyxfbg&e=>
>
>
> _______
> Users mailing list
> Users@lists.opensips.org
>
> https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.opensips.org_cgi-2Dbin_mailman_listinfo_users&d=DwIGaQ&c=q3cDpHe1hF8lXU5EFjNM_A&r=Q2-P3NgorS0ZH4_aMeg5NL1og3Rsx6yNgM-aaPfa8xzzIkVlEcHJTs2jlyabbp9e&m=e1cMNheMB6S0UOeY_WdEZXrfA9R8IF3RbLt4oSfkotM&s=9MMa6DU1B2Z7PGEmqGlSiVm_ujL4HqvpXby2HUyxfbg&e=
>
--
--
Konrad Malewski
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] how to migrate statistics to 3.x ?
Hello,
I am using 3.0.0-dev version and I am having problem with opensipsctl
command for statistics:
$opensipsctl fifo get_statistics load-all
{
"jsonrpc": "2.0",
"id": "a7cbfd4e",
"error": {
"message": "Invalid params",
"code": -32602
}
}
$opensipsctl fifo get_statistics load:
{
"jsonrpc": "2.0",
"id": "177e12c6",
"error": {
"message": "Invalid params",
"code": -32602
}
}
the log says: ERROR:core:get_mi_array_param: Parameter: statistics is not
an array.
What is the new syntax ?
--
--
Konrad Malewski
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] opensips3.0/dev requires huge amount of memory and crashes
Hello, If I enabled TCP only as only protocol, opensips3 starts crashing at startup with following error: ERROR:core:fm_malloc: not enough free shm memory (62949296 bytes left, need 17109592486272), please increase the "-m" command line parameter! The amount of "need" is different every time I restart opensips ERROR:core:fm_malloc: not enough free shm memory (62949296 bytes left, need 8689571889280), please increase the "-m" command line parameter! when I enable udp and add appropriate listen=udp:IP:PORT entry problem goes away. The issue is odd, so what am I doing wrong? Maybe this is a bug ? -- -- Konrad Malewski ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] capabilities of opensips clusterer module
Alexey, I already read some of the articles from the links you provided, but answer is still not straight forward. The relevant part states that "The new dialog clustering support in OpenSIPS 2.4 is a complete one as it not only takes care of dialog replication/sharing, but also of dialog handling in terms of properly triggering dialog-specific actions." But there is no information on how or "if" the module will do call representing / re-homing or restoring. /Konrad Hi Konrad! Clustering OpenSIPS is some mix of: - N OpenSIPS nodes - N RTPEngine instances (I think you can use one, standalone, on a different host than OpenSIPSes) - at least 1 Redis, in case of >=2 RTPEngines, to share RTP sessions - some VRRP realisation, e.g. Keepalived or Pacemaker/Corosync. OpenSIPSes share cluster-related critical data through BIN interface [1], along with cluster-related options in some modules like usrloc [2], dialog [3], tm [4]. Please find 'cluster' word on the documentation pages, I hope this will give you answers on your questions. [1] https://www.opensips.org/Documentation/Interface-Binary-2-4 [2] https://opensips.org/html/docs/modules/2.4.x/usrloc.html [3] https://opensips.org/html/docs/modules/2.4.x/dialog.html [4] https://opensips.org/html/docs/modules/2.4.x/tm.html Another kind of clustering is for horizontal scaling, not redundancy/high-availability. A good example is registrar server clustering:http://www.opensips.org/Documentation/Tutorials-Distributed-User-Location-Federation And some more links:https://blog.opensips.org/2018/03/13/the-new-clustering-engine-of-opensips-2-4/https://blog.opensips.org/2018/03/23/clustering-ongoing-calls-with-opensips-2-4/https://blog.opensips.org/2018/03/27/clustering-presence-services-with-opensips-2-4/ https://github.com/sipwise/rtpenginehttps://github.com/sipwise/rtpengine/wiki/Redis-keyspace-notifications On Tue, Mar 5, 2019 at 11:38 PM Konrad Malewski < konrad.malew...@motorolasolutions.com> wrote: > Hello, > > We ware trying out clusterer module with opensips. We are having problems > understanding what is the purpose of clustering when it comes to calls, so > if anyone has some insights we would appreciate: > - if in active-backup mode active fails how backup is going to recover > the call (with one of our tries nothing happened) ? Does clusterer module > handles it ? > - does the behavior differ when it comes to tcp/udp ? > - how does opensips support call representing / re-homing or restoring > ? > > thanks for any hint, >Konrad > > ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] capabilities of opensips clusterer module
Hello, We ware trying out clusterer module with opensips. We are having problems understanding what is the purpose of clustering when it comes to calls, so if anyone has some insights we would appreciate: - if in active-backup mode active fails how backup is going to recover the call (with one of our tries nothing happened) ? Does clusterer module handles it ? - does the behavior differ when it comes to tcp/udp ? - how does opensips support call representing / re-homing or restoring ? thanks for any hint, Konrad ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] B2BUA and BYE message generated from sipp
I think I found a solution so posting it here.
SIPP sent BYE to wrong address. I had to change uac.xml.
capture contact field field from 200Ok:
-
-
And use it in BYE:
-
---
Now
sipp -t tn -rsa opensips -trace_logs -sf uac.xml -r 1 sipp-uas
works every time
Also when I modified modules/b2b_entities/dlg.c
- method_value = msg->first_line.u.request.method_value;
-
- if(method_value == METHOD_ACK)
- {
- goto search_dialog;
- }
+ method_value = msg->first_line.u.request.method_value;
+
+ if((method_value == METHOD_ACK) || (method_value == METHOD_BYE))
+ {
+ goto search_dialog;
+ }
it started working as well, but I dont think this is the right fix.
On Thu, Feb 7, 2019 at 4:17 PM Konrad Malewski <
konrad.malew...@motorolasolutions.com> wrote:
> Hello,
>
> I am new to opensips. I went through proxy tutorials and now I am trying
> to configure opensips in b2bua mode. I am using 3 dockers (UAS, UAC and
> opensips).
>
> I have problems with BYE message sent by UAC. Opensips is not able to
> match it to whole dialog (this is my interpretation) and returns 500
> internal error (due to t_relay call, but without it there is no response at
> all).
>
>
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] B2BUA and BYE message generated from sipp
=> DBG:b2b_logic:b2bl_search_entity: Key [B2B.407.108.1549535500]
=> DBG:b2b_logic:b2b_logic_notify_request: b2b_entity key =
B2B.407.108.1549535500
=> DBG:b2b_logic:b2b_logic_notify_request: request received for
tuple[0x7fdc845be810]->[95.0]
=> DBG:b2b_logic:b2b_logic_notify_request: Send request [ACK] to peer
[B2B.95.8135310.1549535500]
=> DBG:b2b_entities:b2b_parse_key: hash_index = [95] - local_index=
[8135310]
=> DBG:b2b_entities:b2b_search_htable_next_dlg: entering with start=(nil),
table=0x7fdc845a4128, hash=95, label=8135310
=> DBG:b2b_entities:b2b_search_htable_next_dlg: searching callid
25[B2B.95.8135310.1549535500]
=> DBG:b2b_entities:b2b_search_htable_next_dlg: searching totag
32[42494589cc6520b7535401b81466113d]
=> DBG:b2b_entities:b2b_search_htable_next_dlg: searching fromtag
14[370SIPpTag0130]
=> DBG:b2b_entities:b2b_send_request: Send request [ACK] for entity type
[1] for dlg[0x7fdc845c43c0]->[B2B.95.8135310.1549535500]
=> DBG:b2b_entities:b2b_client_build_dlg: Rem_target = sip:172.18.0.4:5060
;transport=TCP
=> DBG:b2b_entities:b2b_client_build_dlg: send sock= 172.18.0.2
=> DBG:tm:t_uac: next_hop=
=> DBG:core:mk_proxy: doing DNS lookup...
=> DBG:tm:t_uac: sending socket is 172.18.0.2
=> DBG:tm:dlg2hash: 22720
=> DBG:tm:print_request_uri: sip:172.18.0.4:5060;transport=TCP
=> DBG:core:tcp_conn_get: con found in state 0
=> DBG:core:tcp_conn_get: tcp connection found (0x7fdc845c3f68), acquiring
fd
=> DBG:core:tcp_conn_get: c= 0x7fdc845c3f68, n=16, Usock=42
=> DBG:core:handle_worker: read response= 7fdc845c3f68, 1, fd -1 from 4
(1827)
=> DBG:core:tcp_conn_get: after receive_fd: c= 0x7fdc845c3f68 n=8 fd=43
=> DBG:core:proto_tcp_send: sending via fd 43...
=> DBG:core:async_tsend_stream: Async successful write from first try on
0x7fdc845c3f68
=> DBG:core:proto_tcp_send: after write: c= 0x7fdc845c3f68 n/len=420/420
fd=43
=> DBG:tm:cleanup_uac_timers: RETR/FR timers reset
=> DBG:tm:insert_timer_unsafe: [2]: 0x7fdc845c48a0 (51)
=> DBG:core:destroy_avp_list: destroying list (nil)
=> DBG:core:receive_msg: cleaning up
=> DBG:core:tcp_read_req: tcp_read_req end
=> DBG:core:tcp_read_req: Using the global ( per process ) buff
=> DBG:core:tcp_handle_req: content-length= 0
=> DBG:core:tcp_handle_req: Nothing more to read on TCP conn
0x7fdc845be558, currently in state 0
=> DBG:core:parse_msg: SIP Request:
=> DBG:core:parse_msg: method:
=> DBG:core:parse_msg: uri:
=> DBG:core:parse_msg: version:
=> DBG:core:parse_headers: flags=2
=> DBG:core:parse_via_param: found param type 232, =
; state=16
=> DBG:core:parse_via: end of header reached, state=5
=> DBG:core:parse_headers: via found, flags=2
=> DBG:core:parse_headers: this is the first via
=> DBG:core:receive_msg: After parse_msg...
=> DBG:core:receive_msg: preparing to run routing scripts...
=> DBG:core:parse_headers: flags=
=> DBG:core:parse_to_param: tag=B2B.407.108.1549535500
=> DBG:core:_parse_to: end of header reached, state=29
=> DBG:core:_parse_to: display={sut}, ruri={sip:service@172.18.0.4:5060}
=> DBG:core:get_hdr_field: [62]; uri=[sip:service@172.18.0.4:5060]
=> DBG:core:get_hdr_field: to body [sut ]
=> DBG:core:get_hdr_field: cseq : <2>
=> DBG:core:get_hdr_field: content_length=0
=> DBG:core:get_hdr_field: found end of header
=> DBG:b2b_entities:b2b_prescript_f: start - method = BYE
=> DBG:b2b_entities:b2b_prescript_f: host:port [172.18.0.4][5060]
=> DBG:core:grep_sock_info: checking if host==us: 10==10 && [172.18.0.4]
== [172.18.0.2]
=> DBG:core:grep_sock_info: checking if port 5060 matches port 5060
=> DBG:core:check_self: host != me
=> DBG:b2b_entities:b2b_prescript_f: RURI does not point to me
=> DBG:core:parse_headers: flags=
=> t_relay - callid 1-382@172.18.0.3 time [Thu Feb 7 10:31:41 2019] method
(BYE) r-uri (sip:service@172.18.0.4:5060) 2nd via ()
///
--
Konrad Malewski
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
