Re: [OpenSIPS-Users] Can't locate Opensips-cli package's location on Ubuntu22.04
check the location of the fifo file in opensips.cfg it should be in /var... as the same in opensips-cli.cfg. 2 cfg file shoud be pointing to the same file March 21, 2024 at 3:11 PM, "Alain Bieuzent" wrote: > > Did you run an apt update before apt install opensips-cli ? > > **De : **Users au nom de Li Cai > > **Répondre à : **OpenSIPS users mailling list > **Date : **jeudi 21 mars 2024 à 14:37 > **À : **"users@lists.opensips.org" > **Objet : **[OpenSIPS-Users] Can't locate Opensips-cli package's location on > Ubuntu22.04 > > Hi All, > > I’m doing migrating from OpenSIPs 2.X to 3.0 on Ubuntu22.04. Here I met a > problem to install Opensips-cli on Ubuntu22. > > After successfully executing the steps from the installation instruction, > like this – > > The command of ‘sudo apt-get install opensip-cli’ still can’t work, the > output is – > > The command complains that it can’t locate the package opensips-cli. > > Can anyone help with this issue? Any hint will be highly appreciated. > > Thanks, > > Li > > ___ Users mailing list > Users@lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users >___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] push notifications - and now packages failing
Hi all, Maybe I thought wrong and I tried another system with AMD-INTEL architecture. Desperate I started to install packages. The following packages have unmet dependencies: mediaproxy-common : Depends: python3 (< 3.9) but 3.10.6-1~22.04 is to be installed E: Unable to correct problems, you have held broken packages. Any advice is appreciated Regards, Ronald___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] push notifications opensips 3.4
Hi All,
I still have problems with opensips3.4 push notifications:
Somehow INVITEs keep looping and get rejected.
Code:
...
route{
...
if (has_totag()) {
...
if (!is_method("ACK"))
async (pn_process_purr("location"), resume_route);
...
}
...
# do lookup with method filtering
#--
lookup("location", "method-filtering");
$var(rc) = $retcode;
switch ($var(rc)) {
case 1:
# we found at least 1 non-PN contact!
xlog("L_INFO", "DBG: 1 contacts found non-PN ($var(rc))\n");
$var(do_relay) = true;
break;
case 2:
# success, but all contacts are PN-enabled, so we're
# sending PNs / awaiting re-registrations from them
xlog("L_INFO", "DBG: contacts found send PN? ($var(rc))\n");
$var(do_relay) = false;
#$avp(skip_relay) = true;
break;
default:
xlog("L_INFO", "DBG: no contacts found ($var(rc))\n");
t_reply(404, "Not Found");
exit;
}
if ($var(do_relay) && !t_relay())
send_reply(500, "Internal Server Error");
...
if($var(do_relay) == true)
route(relay);
}
...
from log (looping log, it repeats untill server REJECT the INVITE or until
CANCEL):
DBG:core:parse_headers: this is the first via
2024-03-09T09:41:13.485706+00:00 xsp2 /usr/local/sbin/opensips[2061136]:
DBG:core:_parse_to: end of header reached, state=10
2024-03-09T09:41:13.485748+00:00 xsp2 /usr/local/sbin/opensips[2061136]:
DBG:core:_parse_to: display={}, ruri={sip:t...@dummy.com}
2024-03-09T09:41:13.485807+00:00 xsp2 /usr/local/sbin/opensips[2061136]:
DBG:core:get_hdr_field: [20]; uri=[sip:t...@dummy.com]
2024-03-09T09:41:13.485854+00:00 xsp2 /usr/local/sbin/opensips[2061136]:
DBG:core:get_hdr_field: to body [#015#012]
2024-03-09T09:41:13.485915+00:00 xsp2 /usr/local/sbin/opensips[2061136]:
DBG:core:get_hdr_field: cseq : <1>
2024-03-09T09:41:13.485962+00:00 xsp2 /usr/local/sbin/opensips[2061136]:
DBG:core:get_hdr_field: found end of header
2024-03-09T09:41:13.486040+00:00 xsp2 /usr/local/sbin/opensips[2061136]:
DBG:core:parse_headers: flags=
2024-03-09T09:41:13.486088+00:00 xsp2 /usr/local/sbin/opensips[2061136]:
DBG:core:get_dummy_sip_msg: setting as static to 0xb1a612c0
2024-03-09T09:41:13.486145+00:00 xsp2 /usr/local/sbin/opensips[2061136]:
DBG:core:evi_raise_event_msg: found subscriber E_UL_CONTACT_REFRESH
2024-03-09T09:41:13.486207+00:00 xsp2 /usr/local/sbin/opensips[2061136]:
DBG:core:dup_ref_script_route_in_shm: dupping 0xaa264f60
[E_UL_CONTACT_REFRESH], idx 1, ver/cnt 1, to new 0xaa26d9e0
[E_UL_CONTACT_REFRESH], idx 1, ver/cnt 1
2024-03-09T09:41:13.486283+00:00 xsp2 /usr/local/sbin/opensips[2061136]:
DBG:core:release_dummy_sip_msg: cleaning the static sip msg 0xb1a612c0
2024-03-09T09:41:13.486352+00:00 xsp2 /usr/local/sbin/opensips[2061136]:
DBG:core:destroy_avp_list: destroying list (nil)
2024-03-09T09:41:13.486409+00:00 xsp2 /usr/local/sbin/opensips[2061136]:
DBG:core:ipc_handle_job: received job type 0[RPC] from process 6
2024-03-09T09:41:13.486467+00:00 xsp2 /usr/local/sbin/opensips[2061136]:
DBG:core:get_dummy_sip_msg: reusing the static sip msg 0xb1a612c0
2024-03-09T09:41:13.486533+00:00 xsp2 /usr/local/sbin/opensips[2061136]:
DBG:core:parse_params: Parsing params
for:[sip:rvg@82.151.164.77:57775;pn-prid=F1B7F53A99A35254A55CCAE2EDF80C1FAE12F353592BB6ED203ADA0175E34AD9:voip;pn-provider=apns;pn-param=ABCD1234.cllkit.voip;pn-silent=1;pn-timeout=0;transport=udp]
2024-03-09T09:41:13.486571+00:00 xsp2 /usr/local/sbin/opensips[2061136]: ERROR:
-- ** --pn_send was called sip:u...@dummy.com
2024-03-09T09:41:13.486651+00:00 xsp2 /usr/local/sbin/opensips[2061136]:
ERROR:core:route_param_get: route $param variable accepts only integer indexes
2024-03-09T09:41:13.486746+00:00 xsp2 /usr/local/sbin/opensips[2061136]:
message repeated 2 times: [ ERROR:core:route_param_get: route $param variable
accepts only integer indexes]
2024-03-09T09:41:13.486787+00:00 xsp2 /usr/local/sbin/opensips[2061136]:
ERROR:pn params: ,#012 ,#012
2024-03-09T09:41:13.486822+00:00 xsp2 /usr/local/sbin/opensips[2061136]:
DBG:core:release_dummy_sip_msg: cleaning the static sip msg 0xb1a612c0
2024-03-09T09:41:13.486913+00:00 xsp2 /usr/local/sbin/opensips[2061136]:
DBG:core:destroy_avp_list: destroying list (nil)
2024-03-09T09:41:13.697168+00:00 xsp2 /usr/local/sbin/opensips[2061135]:
DBG:core:parse_msg: SIP Request:
Any advice appreciated, regards,
Ronald Geerligs___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] pn still problems part 2
Adding:
event_route[E_UL_CONTACT_REFRESH]
{
route(pm_send, $(param(uri){param.value,pn-provider}),
$(param(uri){param.value,pn-prid}),
$(param(uri){param.value,pn-param}));
# $callid;
# $param(callid);
}
#--
route [pm_send]
{
# exec(marg.sh)
xlog(" -- ** --pn_send was called $ru\n");
xlog("pn_send: pn params: $(param(uri){param.value,pn-provider}),
$(param(uri){param.value,pn-prid}),
$(param(uri){param.value,pn-param})\n");
$var(input) = "input mine three";
#async(exec("/root/marg.sh > effect", "this is my $var(input) for exec\n", , ,
$avp(env));
# async(exec("/root/marg.sh 5 6 7 > effect", $ru, $ru), resume_route);
exit;
}
question: Does the route[pm_send] need to return any value? exit does not not
return value does it?
does the [pm_send] acually need to send the push for the INVITE to be answered
by 200 OK?
Regards, Ronald
March 9, 2024 at 2:46 PM, r...@rvgeerligs.nl wrote:
>
> Hi All,
>
> I still have problems with opensips3.4 push notifications:
>
> Somehow INVITEs keep looping and get rejected.
>
> Code:
> ...
> route{
>
> ...
>
> if (has_totag()) {
>
> ...
>
> if (!is_method("ACK"))
> async (pn_process_purr("location"), resume_route);
>
> ...
> }
>
> ...
>
> # do lookup with method filtering
>
> #--
> lookup("location", "method-filtering");
> $var(rc) = $retcode;
> switch ($var(rc)) {
> case 1:
> # we found at least 1 non-PN contact!
> xlog("L_INFO", "DBG: 1 contacts found non-PN ($var(rc))\n");
> $var(do_relay) = true;
> break;
> case 2:
> # success, but all contacts are PN-enabled, so we're
> # sending PNs / awaiting re-registrations from them
> xlog("L_INFO", "DBG: contacts found send PN? ($var(rc))\n");
> $var(do_relay) = false;
> #$avp(skip_relay) = true;
> break;
> default:
> xlog("L_INFO", "DBG: no contacts found ($var(rc))\n");
> t_reply(404, "Not Found");
> exit;
> }
>
> if ($var(do_relay) && !t_relay())
> send_reply(500, "Internal Server Error");
>
> ...
>
> if($var(do_relay) == true)
> route(relay);
> }
>
> ...
>
> from log (looping log, it repeats):
>
> DBG:core:parse_headers: this is the first via
> 2024-03-09T09:41:13.485706+00:00 xsp2 /usr/local/sbin/opensips[2061136]:
> DBG:core:_parse_to: end of header reached, state=10
> 2024-03-09T09:41:13.485748+00:00 xsp2 /usr/local/sbin/opensips[2061136]:
> DBG:core:_parse_to: display={}, ruri={sip:t...@dummy.com}
> 2024-03-09T09:41:13.485807+00:00 xsp2 /usr/local/sbin/opensips[2061136]:
> DBG:core:get_hdr_field: [20]; uri=[sip:t...@dummy.com]
> 2024-03-09T09:41:13.485854+00:00 xsp2 /usr/local/sbin/opensips[2061136]:
> DBG:core:get_hdr_field: to body [#015#012]
> 2024-03-09T09:41:13.485915+00:00 xsp2 /usr/local/sbin/opensips[2061136]:
> DBG:core:get_hdr_field: cseq : <1>
>
> 2024-03-09T09:41:13.485962+00:00 xsp2 /usr/local/sbin/opensips[2061136]:
> DBG:core:get_hdr_field: found end of header
> 2024-03-09T09:41:13.486040+00:00 xsp2 /usr/local/sbin/opensips[2061136]:
> DBG:core:parse_headers: flags=
> 2024-03-09T09:41:13.486088+00:00 xsp2 /usr/local/sbin/opensips[2061136]:
> DBG:core:get_dummy_sip_msg: setting as static to 0xb1a612c0
> 2024-03-09T09:41:13.486145+00:00 xsp2 /usr/local/sbin/opensips[2061136]:
> DBG:core:evi_raise_event_msg: found subscriber E_UL_CONTACT_REFRESH
> 2024-03-09T09:41:13.486207+00:00 xsp2 /usr/local/sbin/opensips[2061136]:
> DBG:core:dup_ref_script_route_in_shm: dupping 0xaa264f60
> [E_UL_CONTACT_REFRESH], idx 1, ver/cnt 1, to new 0xaa26d9e0
> [E_UL_CONTACT_REFRESH], idx 1, ver/cnt 1
> 2024-03-09T09:41:13.486283+00:00 xsp2 /usr/local/sbin/opensips[2061136]:
> DBG:core:release_dummy_sip_msg: cleaning the static sip msg 0xb1a612c0
> 2024-03-09T09:41:13.486352+00:00 xsp2 /usr/local/sbin/opensips[2061136]:
> DBG:core:destroy_avp_list: destroying list (nil)
> 2024-03-09T09:41:13.486409+00:00 xsp2 /usr/local/sbin/opensips[2061136]:
> DBG:core:ipc_handle_job: received job type 0[RPC] from process 6
> 2024-03-09T09:41:13.486467+00:00 xsp2 /usr/local/sbin/opensips[2061136]:
> DBG:core:get_dummy_sip_msg: reusing the static sip msg 0xb1a612c0
> 2024-03-09T09:41:13.486533+00:00 xsp2 /usr/local/sbin/opensips[2061136]:
> DBG:core:parse_params: Parsing params
> for:[sip:rvg@82.151.164.77:57775;pn-prid=F1B7F53A99A35254A55CCAE2EDF80C1FAE12F353592BB6ED203ADA0175E34AD9:voip;pn-provider=apns;pn-param=ABCD1234.cllkit.voip;pn-silent=1;pn-timeout=0;transport=udp]
> 2024-03-09T09:41:13.486571+00:00 xsp2 /usr/local/sbin/opensips[2061136]:
> ERROR: -- ** --pn_send was called sip:u...@dummy.com
> 2024-03-09T09:41:13.486651+00:00 xsp2 /usr/local/sbin/opensips[2061136]:
> ERROR:core:route_param_get: route $param variable accepts only integer indexes
> 2024-03-09T09:41:13.486746+00:00 xsp2 /usr/local/sbin/opensips[2061136]:
> message repeated 2 times: [ ERROR:core:route_param_get: route
[OpenSIPS-Users] pn still problems
Hi All,
I still have problems with opensips3.4 push notifications:
Somehow INVITEs keep looping and get rejected.
Code:
...
route{
...
if (has_totag()) {
...
if (!is_method("ACK"))
async (pn_process_purr("location"), resume_route);
...
}
...
# do lookup with method filtering
#--
lookup("location", "method-filtering");
$var(rc) = $retcode;
switch ($var(rc)) {
case 1:
# we found at least 1 non-PN contact!
xlog("L_INFO", "DBG: 1 contacts found non-PN ($var(rc))\n");
$var(do_relay) = true;
break;
case 2:
# success, but all contacts are PN-enabled, so we're
# sending PNs / awaiting re-registrations from them
xlog("L_INFO", "DBG: contacts found send PN? ($var(rc))\n");
$var(do_relay) = false;
#$avp(skip_relay) = true;
break;
default:
xlog("L_INFO", "DBG: no contacts found ($var(rc))\n");
t_reply(404, "Not Found");
exit;
}
if ($var(do_relay) && !t_relay())
send_reply(500, "Internal Server Error");
...
if($var(do_relay) == true)
route(relay);
}
...
from log (looping log, it repeats):
DBG:core:parse_headers: this is the first via
2024-03-09T09:41:13.485706+00:00 xsp2 /usr/local/sbin/opensips[2061136]:
DBG:core:_parse_to: end of header reached, state=10
2024-03-09T09:41:13.485748+00:00 xsp2 /usr/local/sbin/opensips[2061136]:
DBG:core:_parse_to: display={}, ruri={sip:t...@dummy.com}
2024-03-09T09:41:13.485807+00:00 xsp2 /usr/local/sbin/opensips[2061136]:
DBG:core:get_hdr_field: [20]; uri=[sip:t...@dummy.com]
2024-03-09T09:41:13.485854+00:00 xsp2 /usr/local/sbin/opensips[2061136]:
DBG:core:get_hdr_field: to body [#015#012]
2024-03-09T09:41:13.485915+00:00 xsp2 /usr/local/sbin/opensips[2061136]:
DBG:core:get_hdr_field: cseq : <1>
2024-03-09T09:41:13.485962+00:00 xsp2 /usr/local/sbin/opensips[2061136]:
DBG:core:get_hdr_field: found end of header
2024-03-09T09:41:13.486040+00:00 xsp2 /usr/local/sbin/opensips[2061136]:
DBG:core:parse_headers: flags=
2024-03-09T09:41:13.486088+00:00 xsp2 /usr/local/sbin/opensips[2061136]:
DBG:core:get_dummy_sip_msg: setting as static to 0xb1a612c0
2024-03-09T09:41:13.486145+00:00 xsp2 /usr/local/sbin/opensips[2061136]:
DBG:core:evi_raise_event_msg: found subscriber E_UL_CONTACT_REFRESH
2024-03-09T09:41:13.486207+00:00 xsp2 /usr/local/sbin/opensips[2061136]:
DBG:core:dup_ref_script_route_in_shm: dupping 0xaa264f60
[E_UL_CONTACT_REFRESH], idx 1, ver/cnt 1, to new 0xaa26d9e0
[E_UL_CONTACT_REFRESH], idx 1, ver/cnt 1
2024-03-09T09:41:13.486283+00:00 xsp2 /usr/local/sbin/opensips[2061136]:
DBG:core:release_dummy_sip_msg: cleaning the static sip msg 0xb1a612c0
2024-03-09T09:41:13.486352+00:00 xsp2 /usr/local/sbin/opensips[2061136]:
DBG:core:destroy_avp_list: destroying list (nil)
2024-03-09T09:41:13.486409+00:00 xsp2 /usr/local/sbin/opensips[2061136]:
DBG:core:ipc_handle_job: received job type 0[RPC] from process 6
2024-03-09T09:41:13.486467+00:00 xsp2 /usr/local/sbin/opensips[2061136]:
DBG:core:get_dummy_sip_msg: reusing the static sip msg 0xb1a612c0
2024-03-09T09:41:13.486533+00:00 xsp2 /usr/local/sbin/opensips[2061136]:
DBG:core:parse_params: Parsing params
for:[sip:rvg@82.151.164.77:57775;pn-prid=F1B7F53A99A35254A55CCAE2EDF80C1FAE12F353592BB6ED203ADA0175E34AD9:voip;pn-provider=apns;pn-param=ABCD1234.cllkit.voip;pn-silent=1;pn-timeout=0;transport=udp]
2024-03-09T09:41:13.486571+00:00 xsp2 /usr/local/sbin/opensips[2061136]: ERROR:
-- ** --pn_send was called sip:u...@dummy.com
2024-03-09T09:41:13.486651+00:00 xsp2 /usr/local/sbin/opensips[2061136]:
ERROR:core:route_param_get: route $param variable accepts only integer indexes
2024-03-09T09:41:13.486746+00:00 xsp2 /usr/local/sbin/opensips[2061136]:
message repeated 2 times: [ ERROR:core:route_param_get: route $param variable
accepts only integer indexes]
2024-03-09T09:41:13.486787+00:00 xsp2 /usr/local/sbin/opensips[2061136]:
ERROR:pn params: ,#012 ,#012
2024-03-09T09:41:13.486822+00:00 xsp2 /usr/local/sbin/opensips[2061136]:
DBG:core:release_dummy_sip_msg: cleaning the static sip msg 0xb1a612c0
2024-03-09T09:41:13.486913+00:00 xsp2 /usr/local/sbin/opensips[2061136]:
DBG:core:destroy_avp_list: destroying list (nil)
2024-03-09T09:41:13.697168+00:00 xsp2 /usr/local/sbin/opensips[2061135]:
DBG:core:parse_msg: SIP Request:
Any advice appreciated, regards,
Ronald Geerligs___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] opensips 3.4 push notification
Hi,
I kind of followed the article SIP Push Notification with OpenSIPS 3.1 LTS [RFC
8599 support][Part II] as I connot find anything related to opensips 3.4.x.
When I disable (commenting by #) modparam("registrar", "pn_enable", true), the
call actually works.
When I enable modparam("registrar", "pn_enable", true) the call does not come
through.
It gets rerouted internally to external ip address after the authentication,
second INVITE with answer to nonce, and giving it a try.
Opensips keeps asking for Proxy Authentication required which was allready
accepted.
Anyone an idea?
Regards,
Ronald Geerligs___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] pn opensips 3.4
Hi,
Currently experimenting with the EXEC module. Still all advice is welcome.
Regards,
Ronald
February 3, 2024 at 4:39 PM, r...@rvgeerligs.nl wrote:
>
> Hi,
>
> I managed to integrate pn in opensips 3.4 as I get as reply to register from
> my opensips server:
>
> SIP/2.0 200 OK
>
> Via: SIP/2.0/UDP
> 192.168.1.14:57993;received=x.x.x.x;branch=z9hG4bK.wxwvFfCSG;rport=57993
>
> To: sip:xx;tag=eeba.752562b862ac8bd9236fb7979b3044b6
>
> From: ;tag=mFddPGSw6
>
> Call-ID: UFVVRWp5rN
>
> CSeq: 23 REGISTER
>
> **Feature-Caps:
> +sip.pns="apns";+sip.pnsreg="130";+sip.pnspurr="3fa.a1d4c.c3fbd0c8"**
>
> Server: OpenSIPS (3.4.0 (aarch64/linux))
>
> Content-Length: 0
>
> Also I have a bash script getting token and sending pn to apns developement.
> I have pn-prid, pn-param, pn-provider
> I want to connect the in the function
>
> route[pm_send]
>
> {
>
> exit;
>
> }
>
> questions:
> How do I get opensips to call a bash script with arguments? Arguments being
> pn-prid, pn-param, pn-provider.
> Where do I place the script?
>
> would that be in my module path?
>
> mpath="/usr/local/lib64/opensips/modules/"
>
> I tried a marg.sh doing:
>
> #!/bin/bash
>
> echo "The first argument is: $1"
>
> echo "The second argument is: $2"
>
> echo "The third argument is: $3"
>
> But I got:
>
> ERROR:core:parse_opensips_cfg: bad config file (4 errors)
>
> Any advise appreciated.
>
> Regards,
>___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] pn opensips 3.4
Hi,
I managed to integrate pn in opensips 3.4 as I get as reply to register from my
opensips server:
SIP/2.0 200 OK
Via: SIP/2.0/UDP
192.168.1.14:57993;received=x.x.x.x;branch=z9hG4bK.wxwvFfCSG;rport=57993
To: sip:xx;tag=eeba.752562b862ac8bd9236fb7979b3044b6
From: ;tag=mFddPGSw6
Call-ID: UFVVRWp5rN
CSeq: 23 REGISTER
**Feature-Caps:
+sip.pns="apns";+sip.pnsreg="130";+sip.pnspurr="3fa.a1d4c.c3fbd0c8"**
Server: OpenSIPS (3.4.0 (aarch64/linux))
Content-Length: 0
Also I have a bash script getting token and sending pn to apns developement.
I have pn-prid, pn-param, pn-provider
I want to connect the in the function
route[pm_send]
{
exit;
}
questions:
How do I get opensips to call a bash script with arguments? Arguments being
pn-prid, pn-param, pn-provider.
Where do I place the script?
would that be in my module path?
mpath="/usr/local/lib64/opensips/modules/"
I tried a marg.sh doing:
#!/bin/bash
echo "The first argument is: $1"
echo "The second argument is: $2"
echo "The third argument is: $3"
But I got:
ERROR:core:parse_opensips_cfg: bad config file (4 errors)
Any advise appreciated.
Regards,___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] Implementation of RFC 8599
Hi Volkan, I implemented the scripting from sip-push-notification-with-opensips-3-1-lts-rfc-8599-supportpart-ii/ in opensips 3.4.0. As the send pn to apple or googlei s not defined I fail to get the parameters passed to the send pn to apns script which I also have. I seem to have lost the device-ID in opensips or in any INVITE somewhere as I do not understand the RFC certainly not towards the device_ID or token. Or this ID is stored on registration at the proxy? srcipt to directly talk to apple: https://medium.com/@egzon.arifi/sending-a-push-notification-to-an-ios-device-using-a-bash-script-96c056c1544c Please keep me posted on what you find. Regards, Ronald February 2, 2024 at 6:01 AM, "johan" wrote: > > send a query directly to apple or to google for waking them up. I did > something like that in an external lua script. > > > On 2/02/2024 09:49, Volkan Oransoy wrote: > > > > > > Hi all, > > > > I am working on implementing RFC 8599 and have an architectural question. > > I followed the blog > > posthttps://blog.opensips.org/2020/06/03/sip-push-notification-with-opensips-3-1-lts-rfc-8599-supportpart-ii/ > > and it works. Based on the rfc and the implementation of Opensips, the UA > > should have a valid registration throughout the process. When a lookup > > performed, opensips finds the pn-enabled record, triggers the PN and after > > a re-registration of the UA, it proxies the call. This process works > > without an issue. But when we kill the UA on the client device (the client > > is connected via WSS), after the registration expires, the call can't be > > proxied since there is no registration. > > I want to wake up the UA even if there is no registration on the proxy and > > suspend the call until the UA registers to the system. Should I handle this > > scenario with a custom setup? How do you handle this scenario on your > > setups? Or do I misinterpret the rfc? > > > > Thanks > > > > > > > > > > > > > > Volkan > > > > > > > > > > ___ > > Users mailing list > > Users@lists.opensips.org > > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > >___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] opensips 3.4 documentation event_routing example 1.6.1 - push notification
Hi openSIPS team, I do not understand the documentaion (opensips version 3.4 manual) on the event_routing module. The example given 1.6.1 push notification does not seem to do just that. It says: " 1.6.1. Push Notification We use*notify_on_event*to capture the events on new contact registrations for callee. Once the call is sent to callee, based on the notification (for new contacts) we inject the newly registered contacts as new branches in the ongoing transaction. Schematics : when we send a call to a user, we subscribe to see any new contacts being registered by the user. On such a notification, we add the new contact as a new branch to the ongoing transaction (ringing) to user. " It seems this has to do with notify_on_event. It may be that the new branches are be added with device information for the push notification, but I do not see that in the example given. Please advise, Regards, Ronald Geerligs___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] pn push notifications
hi all, for your information: **Sending a push notification to an iOS device using a Bash script** https://medium.com/@egzon.arifi/sending-a-push-notification-to-an-ios-device-using-a-bash-script-96c056c1544c I hope the pn in opensips only requires the route to the apn: https://api.development.push.apple.com/. dev https://api.push.apple.com/ opp but I fear it does not. Regards, Ronald January 15, 2024 at 10:57 AM, "Alexey" wrote: > > Hello, > > there are two tutorials in the official blog: > > part I : > https://blog.opensips.org/2020/05/07/sip-push-notification-with-opensips-3-1-lts-rfc-8599-supportpart-i/ > > part II : > https://blog.opensips.org/2020/06/03/sip-push-notification-with-opensips-3-1-lts-rfc-8599-supportpart-ii/ > > -- > best regards, Alexey > https://alexeyka.zantsev.com/ > > ___ > Users mailing list > Users@lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users >___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] pn push notifications
Adrian, thank you for the explanation. It is clear to me now. I will firstly go with a solution completely within openSIPS. Regards, Ronald January 15, 2024 at 8:59 AM, "Adrian Georgescu" wrote: > > OpenSIPS handles the SIP traffic, of course. The push server just handles > multiple combinations of apps/ push services in an easier way. You could do a > lot or all that its needed just from within OpenSIPS but as the number of > combinations of apps and services grow another layer of abstraction make it > easier to manage, plus you eliminate another possible blocking item from your > routes as the works are down asynchronously outside OpenSIPS. > > > — > Adrian > > > > > On 14 Jan 2024, at 20:33, r...@rvgeerligs.nl wrote: > > > > Thank you very much, Adrian, > > > > I noticed it allready. It seems this is a dedicated push server. > > Does it handle the normal SIP traffic as well? > > > > Regards, > > > > Ronald > > > > January 14, 2024 at 3:13 PM, "Adrian Georgescu" > > wrote: > > > > > > > > There are many ways of implementing push notifications with OpenSIPS. > > > This is how we implemented it. > > > > > > https://github.com/AGProjects/sylk-pushserver/blob/master/config/opensips.cfg > > > > > > — > > > Adrian > > > > > > > > > > > On 13 Jan 2024, at 17:37, r...@rvgeerligs.nl wrote: > > > > > > > > Hi All, > > > > > > > > > > > > I am trying to implement an opensips server 3.4 with pn support. > > > > Primarily apple push notifications. Later I will try google. > > > > > > > > Does any one have this implemented yet? > > > > > > > > Where can I find an example cfg for opensips? > > > > > > > > Any help is appreciated. > > > > > > > > > > > > Regards, > > > > > > > > > > > > Ronald Geerligs > > > > ___ > > > > Users mailing list > > > > Users@lists.opensips.org > > > > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > > > > > > > > ___ > > > Users mailing list > > > Users@lists.opensips.org > > > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > > > > > ___ > > Users mailing list > > Users@lists.opensips.org > > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > >___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] pn push notifications
Hi Alexey,
I noticed those too, but I do not understand the following code:
event_route [E_UL_CONTACT_REFRESH]
{
route(PN_SEND, $(param(uri){param.value,pn-provider}),
$(param(uri){param.value,pn-prid}),
$(param(uri){param.value,pn-param}));
}
# $param(1) - PN provider
# $param(2) - PN PRID
# $param(3) - PN param
What is this doing? Is the contents of this part lacking? Is it the normal
routing code, but the actual pn send is lacking? How do i write exec(what
client) or rest_client?
route [PN_SEND]
{
# send a PN using, for example, **exec** or **rest_client**
}
# how do we actually send the PN?
Regards,
Ronald
January 15, 2024 at 10:57 AM, "Alexey" wrote:
>
> Hello,
>
> there are two tutorials in the official blog:
>
> part I :
> https://blog.opensips.org/2020/05/07/sip-push-notification-with-opensips-3-1-lts-rfc-8599-supportpart-i/
>
> part II :
> https://blog.opensips.org/2020/06/03/sip-push-notification-with-opensips-3-1-lts-rfc-8599-supportpart-ii/
>
> --
> best regards, Alexey
> https://alexeyka.zantsev.com/
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] pn push notifications
Thank you very much, Adrian, I noticed it allready. It seems this is a dedicated push server. Does it handle the normal SIP traffic as well? Regards, Ronald January 14, 2024 at 3:13 PM, "Adrian Georgescu" wrote: > > There are many ways of implementing push notifications with OpenSIPS. This is > how we implemented it. > > https://github.com/AGProjects/sylk-pushserver/blob/master/config/opensips.cfg > > — > Adrian > > > > > On 13 Jan 2024, at 17:37, r...@rvgeerligs.nl wrote: > > > > Hi All, > > > > > > I am trying to implement an opensips server 3.4 with pn support. Primarily > > apple push notifications. Later I will try google. > > > > Does any one have this implemented yet? > > > > Where can I find an example cfg for opensips? > > > > Any help is appreciated. > > > > > > Regards, > > > > > > Ronald Geerligs > > ___ > > Users mailing list > > Users@lists.opensips.org > > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > > ___ > Users mailing list > Users@lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users >___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] pn push notifications
Hi All, I am trying to implement an opensips server 3.4 with pn support. Primarily apple push notifications. Later I will try google. Does any one have this implemented yet? Where can I find an example cfg for opensips? Any help is appreciated. Regards, Ronald Geerligs___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] Adding PSTN Gateway in Opensips 3.0
Thx, But I have it working allready and I have a choise of PSTN gateways too. Regards January 12, 2024 at 6:37 AM, "HS" wrote: > > Hi all. > > Thanks a lot @Bogdan-Andrei Iancu, once you confirmed that it appends the > correct domain, I had to play around with the dialplan and config and made it > work. > > @Ronald - thanks. Hope it works for you too. > > Best. >___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] Adding PSTN Gateway in Opensips 3.0
Hi, Shouldn't this be done in dynamic routing > Gateway | Carriers? Regards, Ronald Geerligs PS I registered at anveo for an account too. January 9, 2024 at 11:40 AM, "HS" wrote: > > Dear all. > > Greetings and a Happy New Year. I want to add a PSTN gateway and the carrier > expects something like: [PREFIX]phonenum...@sbc.anveo.com. I think I have > figured out the [PREFIX] part, but can't seem to add "@sbc.anveo.com > http://sbc.anveo.com/ " via the dialplan module. There seems to be a > validation error on the Opensips CP. According to some old documentation it > used to be possible to add something like: sip:\\1...@sbc.anveo.com - but not > any more. I have searched about Opensips/Kamailio, read Flavio's book. > > Is it possible to append the correct domain/URI/@sbc.whatever.com > http://sbc.whatever.com/ to a phone number dependant on the gateway used? > Would this happen in the config? Dialplan? Dynamic Routing? Dispatcher module? > > I am sure this is really basic - references to any tutorials would be helpful. > > Thanks. >___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] opensips and NAT
Hi, Should I try something like nat_uac_test(diff-ip-src-contact || private-contact || diff-ip-src-via || diff-port-src-via)? Any ideas? Regards, Ronald December 15, 2023 at 4:38 PM, r...@rvgeerligs.nl wrote: > > Hi > > I use opensips 3.4 and I have NAT problems with 2 devices behind the same NAT > (called party hears nothing). > The A party is softphone on iPhone (linphone) the B (called)party is > Polycom310. The other way around works (Polycom calls linphone). > > Actually I tested this in two different NAT locations. > The first location repeatedly works. The second location gives the problem. > Both locations have changing public IP addresses and DHCP on 192.168 network. > Both locations have one FX number assigned to them. No SIP ALG active. > > I use nat_uac_test(diff-ip-src-contact). > > There is a table: > 1.5.5. nat_uac_test(flags) > Tries to guess if client's request originated behind a nat. The parameter > determines what heuristics is used. > > Meaning of the flags (string) parameter is as follows: > > private-contact - (old 1 flag) Contact header field is searched for > occurrence of RFC1918 / RFC6598 addresses. > > diff-ip-src-via - (old 2 flag) the "received" test is used: address in Via is > compared against source IP address of signaling > > private-via - (old 4 flag) Top Most VIA is searched for occurrence of RFC1918 > / RFC6598 addresses > > private-sdp - (old 8 flag) SDP is searched for occurrence of RFC1918 / > RFC6598 addresses > > diff-port-src-via - (old 16 flag) test if the source port is different from > the port in Via > > diff-ip-src-contact - (old 32 flag) address in Contact is compared against > source IP address of signaling. > > diff-port-src-contact - (old 64 flag) Port in Contact is compared against > source port of signaling > > carrier-grade-nat - (old 128 flag) also include RFC 6333 addresses in the > checks for ct, via and sdp flags. > > A CSV of the above flags can be provided, the test returns true if any of the > tests identified a NAT. > > Currently I use old flag 32. > > I read that using the equivalent of 19 might help but I dont see that in the > table. > > Any advice is appreciated. > > Regards, > > Ronald Geerligs >___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] opensips and NAT
Hi I use opensips 3.4 and I have NAT problems with 2 devices behind the same NAT (called party hears nothing). The A party is softphone on iPhone (linphone) the B (called)party is Polycom310. The other way around works (Polycom calls linphone). Actually I tested this in two different NAT locations. The first location repeatedly works. The second location gives the problem. Both locations have changing public IP addresses and DHCP on 192.168 network. Both locations have one FX number assigned to them. No SIP ALG active. I use nat_uac_test(diff-ip-src-contact). There is a table: 1.5.5. nat_uac_test(flags) Tries to guess if client's request originated behind a nat. The parameter determines what heuristics is used. Meaning of the flags (string) parameter is as follows: private-contact - (old 1 flag) Contact header field is searched for occurrence of RFC1918 / RFC6598 addresses. diff-ip-src-via - (old 2 flag) the "received" test is used: address in Via is compared against source IP address of signaling private-via - (old 4 flag) Top Most VIA is searched for occurrence of RFC1918 / RFC6598 addresses private-sdp - (old 8 flag) SDP is searched for occurrence of RFC1918 / RFC6598 addresses diff-port-src-via - (old 16 flag) test if the source port is different from the port in Via diff-ip-src-contact - (old 32 flag) address in Contact is compared against source IP address of signaling. diff-port-src-contact - (old 64 flag) Port in Contact is compared against source port of signaling carrier-grade-nat - (old 128 flag) also include RFC 6333 addresses in the checks for ct, via and sdp flags. A CSV of the above flags can be provided, the test returns true if any of the tests identified a NAT. Currently I use old flag 32. I read that using the equivalent of 19 might help but I dont see that in the table. Any advice is appreciated. Regards, Ronald Geerligs___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] Facing some issue with opensips while configuration .
Hi, Your OCP OpenSIPS Control Panel will not work! Please downgrade to version 7.4. Ronald Geerligs December 12, 2023 at 6:39 AM, "Bogdan-Andrei Iancu" wrote: > > Hi Sasmita? > > Why the old 2.2? Try 3.4 version, this may be fixed. > > Regards, > > Bogdan-Andrei Iancu > > OpenSIPS Founder and Developer > https://www.opensips-solutions.com https://www.opensips-solutions.com/ > https://www.siphub.com https://www.siphub.com/ > > On 12.12.2023 10:48, Sasmita Panda wrote: > > > > > > HI All , > > > > > > I have RedHat machine : VERSION_ID="8.7" > > > > I am trying to install opensips 2.2 . > > > > > > > > I have installed mysql > > > > Name : mysql-server : Version : 8.0.32 > > > > > > > > > > > > Name : mysql-devel : Version : 8.0.32 > > > > Name : mysql-libs: Version : 8.0.32 > > > > > > > > **These are all installed still when I am running make command on opensips > > its giving some error while building mysql module . ** > > > > > > > > make[1]: Entering directory '/home/ec2-user/opensips-2.2/modules/db_mysql' > > Compiling row.c > > Compiling my_con.c > > In file included from row.c:29: > > my_con.h:36:2: error: unknown type name ‘my_bool’ > > my_bool null; > > ^~~ > > > > > > > > > > Is there any compatibility issue of opensips with mysql ? What version of > > mysql I should use ? > > > > > > > > **Thanks & Regards** > > *Sasmita Panda* > > > > *Senior Network Testing and Software Engineer* > > > > *3CLogic , ph:07827611765* > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ___ > > Users mailing list > > Users@lists.opensips.org > > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > >___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] OpenSIPS Control Panel supported OpenSIPS version question
Hi all, I do not know where to post this, but maybe it is all right. I use: Opensips 3.4 compiled on Oracle VM ARM Ubuntu 22.04.2 LTS - php 7.4 with OCP 9.3.3. Everything works! Installed OCP 9.3.4 and many menues on the left side have no reaction: CallCenter keepalived TLS management ! UAC registrant SMPP Gateway TCP Management Regards, Ronald Geerligs October 2, 2023 at 8:49 AM, "Răzvan Crainea" wrote: > > Hi, Nineto! > > Although it was not already released, OpenSIPS master branch should be > compatible with OpenSIPS 3.4. The compatibility process is not yet > complete, therefore a full release (9.3.4) is not available yet for > OpenSIPS 3.4. > > Best regards, > > Răzvan Crainea > OpenSIPS Core Developer / SIPhub CTO > http://www.opensips-solutions.com/ / https://www.siphub.com/ > > On 9/29/23 19:15, Nine to one wrote: > > > > > Hello OpenSIPS Control Panel developers, > > > > From website OCP only mentioned support up to OpenSIPS 3.3, I am using > > 3.4, so want to know if current OCP already support OpenSIPS 3.4 or not. > > > > Thanks, > > Nineto > > > > ___ > > Users mailing list > > Users@lists.opensips.org > > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > > ___ > Users mailing list > Users@lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users >___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] Opensips-cp php versions supported
Hi, I had the same. Had to work back towards PHP 7.4. There are very big changes in syntax in 8.1. And it seems the OCP has not adapted its sources. As you have also noticed, that is a lot of work. Regards, Ronald September 5, 2023 at 11:49 PM, tre...@webon.co.za wrote: > > Hi Guys, > > Cant seem to find any info on what versions of PHP work with OCP, I > just installed 9.3.2 on PHP 8.1 (Centos9 Stream) and other than login > nothing was working every page would just display a blank body, > checking php logs gives me a php exception every page load, switcing to > php7.4 everything seems to be working so far. does OCP not support php > 8.X? > > [05-Sep-2023 21:27:51 UTC] PHP Fatal error: Uncaught Error: Call to > undefined function each() in /var/www/opensips- > cp/web/tools/admin/boxes_config/template/menu.php:46 > > [05-Sep-2023 21:25:42 UTC] PHP Fatal error: Uncaught Error: Attempt to > assign property "addresses" on null in /var/www/opensips- > cp/config/tools/system/addresses/settings.inc.php:24 > > Thanks > Trevor > > ___ > Users mailing list > Users@lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users >___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] Wrong TCP socket being used on TLS registrations
Hi, again,
Did this work any time before?
I have force_rport(), fix_nated_register() active and as follows:
if (nat_uac_test("diff-ip-src-contact")) {
if (is_method("REGISTER")) {
fix_nated_register();
setbflag("NAT");
} else {
fix_nated_contact(); <
setflag("NAT");
}
}
But in my tcpdump I only see 1 natted address. Which would mean opensips
suddenly forgets the register with the other natted address
fix_nated_register().
we would like to see both natted ip adresses. The public IPv4 address is the
only one addressed.
Regards
Ronald
September 2, 2023 at 2:17 AM, "Ray Jackson" wrote:
>
> Hi all,
>
>
>
> I'm facing a weird issue which I think is related to broken TCP socket reuse
> logic where the wrong client is receiving incoming calls due to the wrong
> socket being used for the incoming INVITE.
>
>
>
> The scenario is when I have 2 clients registering using TLS behind NAT at the
> same Public IPv4 address and both clients are using the same private port
> number. So client 1 registers and the Via and contact header looks like:
>
>
>
> **Via: ** SIP/2.0/TLS
> 192.168.42.162:5062;**branch=**z9hG4bK1409895926;rport;alias**Contact: **
> ;**reg-id=**2;+sip.instance="
> urn:uuid:--1000-8000-C074AD928AC4 "
>
>
>
> Client 2 registers from behind the same Public IPv4 address and the Via and
> contact header looks like:
>
>
>
> **Via: ** SIP/2.0/TLS
> 192.168.42.186:5062;**branch=**z9hG4bK-aff1f3b3**Contact: **
> ;expire**s=**300
>
>
>
> The location table shows Client 1 received field of 103.212.1.2:5062 and
> Client 103.212.1.2:23456
>
>
>
> When a call comes in for Client 1 the location lookup seems to return the
> correct 'received' address and port (e.g. 103.212.1.2:5062) and all the logs
> indicate that this is where the SIP INVITE *should* be going to (in the $du
> field). However when you check the SIP traffic it selects Client 2's socket
> and the traffic goes to port 23456 instead of 5062.
>
>
>
> I think this is related somehow to the TCP port reuse logic inside Opensips.
> My suspicion is that Opensips is looking at the Contact or Via port number
> (which is the same for both client 1 and 2) and then somehow mapping this to
> the wrong TCP received socket.
>
>
>
> Does anybody have any suggestions here? Should I be fixing the NAT in the
> Contact header (using fix_nated_contact). I read somewhere that you
> shouldn't rewrite the Contact header to avoid problems with sending a
> different Contact URI to the client on calls. Or is this issue more related
> to the Via header and the TCP port reuse logic looking at this port instead
> of the actual received port when choosing the outgoing socket?
>
>
>
> FYI: I am using both force_rport() and fix_nated_register() for incoming
> registrations from these clients and matching_mode of 0 in usrloc. However,
> I am not using fix_nated_contact() for registrations.
>
>
>
> Thanks,
>
>
>
> Ray
>___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] Wrong TCP socket being used on TLS registrations
Hi Ray, I am interested the solution or comments you receive. I have a similar problem. I have no voice or oneway voice on one of the clients. But I could work around it as I am using softphones on iphones as client. My work around was to turn wifi off on one of the clients, so this client gets the public IP of the phone subscription. But I still have this problem is both clients are in the same NAT. Regards, Ronald September 2, 2023 at 2:17 AM, "Ray Jackson" wrote: > > Hi all, > > > > I'm facing a weird issue which I think is related to broken TCP socket reuse > logic where the wrong client is receiving incoming calls due to the wrong > socket being used for the incoming INVITE. > > > > The scenario is when I have 2 clients registering using TLS behind NAT at the > same Public IPv4 address and both clients are using the same private port > number. So client 1 registers and the Via and contact header looks like: > > > > **Via: ** SIP/2.0/TLS > 192.168.42.162:5062;**branch=**z9hG4bK1409895926;rport;alias**Contact: ** > ;**reg-id=**2;+sip.instance=" > urn:uuid:--1000-8000-C074AD928AC4 " > > > > Client 2 registers from behind the same Public IPv4 address and the Via and > contact header looks like: > > > > **Via: ** SIP/2.0/TLS > 192.168.42.186:5062;**branch=**z9hG4bK-aff1f3b3**Contact: ** > ;expire**s=**300 > > > > The location table shows Client 1 received field of 103.212.1.2:5062 and > Client 103.212.1.2:23456 > > > > When a call comes in for Client 1 the location lookup seems to return the > correct 'received' address and port (e.g. 103.212.1.2:5062) and all the logs > indicate that this is where the SIP INVITE *should* be going to (in the $du > field). However when you check the SIP traffic it selects Client 2's socket > and the traffic goes to port 23456 instead of 5062. > > > > I think this is related somehow to the TCP port reuse logic inside Opensips. > My suspicion is that Opensips is looking at the Contact or Via port number > (which is the same for both client 1 and 2) and then somehow mapping this to > the wrong TCP received socket. > > > > Does anybody have any suggestions here? Should I be fixing the NAT in the > Contact header (using fix_nated_contact). I read somewhere that you > shouldn't rewrite the Contact header to avoid problems with sending a > different Contact URI to the client on calls. Or is this issue more related > to the Via header and the TCP port reuse logic looking at this port instead > of the actual received port when choosing the outgoing socket? > > > > FYI: I am using both force_rport() and fix_nated_register() for incoming > registrations from these clients and matching_mode of 0 in usrloc. However, > I am not using fix_nated_contact() for registrations. > > > > Thanks, > > > > Ray >___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] opensips v 3.3 to 3.4 on Oracle cloud ARM
changed user and passwd August 4, 2023 at 12:40 PM, r...@rvgeerligs.nl wrote: > > Hi. > > cfg file attached and init.d/opensips34 attached. > > Regards, > > Ronald Geerligs > > August 4, 2023 at 9:48 AM, "Răzvan Crainea" wrote: > > > > > Hi, Ronald! > > > > Usage of nat_uac_test has been changed between 3.3 and 3.4 [1]. Did you > > update your function according to the 3.4 syntax? Can you paste the > > snippet you are using? > > > > [1] https://www.opensips.org/Documentation/Migration-3-3-0-to-3-4-0 > > > > Best regards, > > > > Răzvan Crainea > > OpenSIPS Core Developer / SIPhub CTO > > http://www.opensips-solutions.com/ / https://www.siphub.com/ > > > > On 8/3/23 19:15, r...@rvgeerligs.nl wrote: > > > > > > > > Hi , > > > > > > I compiled v 3.3 all is working. Compiled 3.4 and I get the errors below. > > > > > > I looked at the source 3.4, also at the source in version 3.3.5 > > > (nathelper and nattraversal) but I could not simply replace the 3.4 > > > source with the 3.3 source. > > > > > > This looks like a compiler setting or a programm issue. > > > > > > Please advice, > > > > > > > > > Ronald Geerligs > > > > > > > > > --- > > > error from logfile: > > > > > > DBG:core:trace_prot_bind: has no bind api function > > > > > > > > > 2023-08-03T12:20:09.298662+00:00 xsp2 /usr/local/sbin/opensips[52802]: > > > DBG:core:init_xlog: failed to load trace protocol! > > > > > > > > > 2023-08-03T12:20:09.298686+00:00 xsp2 /usr/local/sbin/opensips[52802]: > > > DBG:core:count_module_procs: modules require 1 extra processes > > > > > > > > > 2023-08-03T12:20:09.298712+00:00 xsp2 /usr/local/sbin/opensips[52802]: > > > DBG:core:init_pkg_stats: setting stats for 18 processes > > > > > > > > > 2023-08-03T12:20:09.298741+00:00 xsp2 /usr/local/sbin/opensips[52802]: > > > DBG:core:fix_actions: fixing force_rport, > > > /etc/opensips/opensips34.cfg:169 > > > > > > > > > 2023-08-03T12:20:09.298769+00:00 xsp2 /usr/local/sbin/opensips[52802]: > > > DBG:core:fix_actions: fixing nat_uac_test, > > > /etc/opensips/opensips34.cfg:170 > > > > > > > > > 2023-08-03T12:20:09.298796+00:00 xsp2 /usr/local/sbin/opensips[52802]: > > > ERROR:core:fix_cmd: Param [1] expected to be a string or variable > > > > > > > > > 2023-08-03T12:20:09.298826+00:00 xsp2 /usr/local/sbin/opensips[52802]: > > > ERROR:core:fix_actions: Failed to fix command > > > > > > > > > 2023-08-03T12:20:09.298851+00:00 xsp2 /usr/local/sbin/opensips[52802]: > > > ERROR:core:fix_actions: fixing failed (code=-6) at > > > /etc/opensips/opensips34.cfg:170 > > > > > > > > > 2023-08-03T12:20:09.298879+00:00 xsp2 /usr/local/sbin/opensips[52802]: > > > CRITICAL:core:fix_expr: fix_actions error > > > > > > > > > 2023-08-03T12:20:09.298905+00:00 xsp2 /usr/local/sbin/opensips[52802]: > > > ERROR:core:main: failed to fix configuration with err code -6 > > > > > > > > > 2023-08-03T12:20:09.298936+00:00 xsp2 /usr/local/sbin/opensips[52802]: > > > INFO:core:cleanup: cleanup > > > > > > > > > 2023-08-03T12:20:09.298962+00:00 xsp2 /usr/local/sbin/opensips[52802]: > > > DBG:presence_xml:destroy: start > > > > > > > > > 2023-08-03T12:20:09.298991+00:00 xsp2 /usr/local/sbin/opensips[52802]: > > > NOTICE:presence:destroy: destroy module ... > > > > > > > > > > > > ___ > > > Users mailing list > > > Users@lists.opensips.org > > > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > > > > > ___ > > Users mailing list > > Users@lists.opensips.org > > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > >___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] opensips v 3.3 to 3.4 on Oracle cloud ARM
Hi, I chose the equivalent of 32 "*diff-ip-src-contact*" and "*private-contact*" later on in the script and it started working! Thx all for the help. Regards, Ronald Geerligs August 4, 2023 at 9:48 AM, "Răzvan Crainea" wrote: > > Hi, Ronald! > > Usage of nat_uac_test has been changed between 3.3 and 3.4 [1]. Did you > update your function according to the 3.4 syntax? Can you paste the > snippet you are using? > > [1] https://www.opensips.org/Documentation/Migration-3-3-0-to-3-4-0 > > Best regards, > > Răzvan Crainea > OpenSIPS Core Developer / SIPhub CTO > http://www.opensips-solutions.com/ / https://www.siphub.com/ > > On 8/3/23 19:15, r...@rvgeerligs.nl wrote: > > > > > Hi , > > > > I compiled v 3.3 all is working. Compiled 3.4 and I get the errors below. > > > > I looked at the source 3.4, also at the source in version 3.3.5 > > (nathelper and nattraversal) but I could not simply replace the 3.4 > > source with the 3.3 source. > > > > This looks like a compiler setting or a programm issue. > > > > Please advice, > > > > > > Ronald Geerligs > > > > > > --- > > error from logfile: > > > > DBG:core:trace_prot_bind: has no bind api function > > > > > > 2023-08-03T12:20:09.298662+00:00 xsp2 /usr/local/sbin/opensips[52802]: > > DBG:core:init_xlog: failed to load trace protocol! > > > > > > 2023-08-03T12:20:09.298686+00:00 xsp2 /usr/local/sbin/opensips[52802]: > > DBG:core:count_module_procs: modules require 1 extra processes > > > > > > 2023-08-03T12:20:09.298712+00:00 xsp2 /usr/local/sbin/opensips[52802]: > > DBG:core:init_pkg_stats: setting stats for 18 processes > > > > > > 2023-08-03T12:20:09.298741+00:00 xsp2 /usr/local/sbin/opensips[52802]: > > DBG:core:fix_actions: fixing force_rport, /etc/opensips/opensips34.cfg:169 > > > > > > 2023-08-03T12:20:09.298769+00:00 xsp2 /usr/local/sbin/opensips[52802]: > > DBG:core:fix_actions: fixing nat_uac_test, /etc/opensips/opensips34.cfg:170 > > > > > > 2023-08-03T12:20:09.298796+00:00 xsp2 /usr/local/sbin/opensips[52802]: > > ERROR:core:fix_cmd: Param [1] expected to be a string or variable > > > > > > 2023-08-03T12:20:09.298826+00:00 xsp2 /usr/local/sbin/opensips[52802]: > > ERROR:core:fix_actions: Failed to fix command > > > > > > 2023-08-03T12:20:09.298851+00:00 xsp2 /usr/local/sbin/opensips[52802]: > > ERROR:core:fix_actions: fixing failed (code=-6) at > > /etc/opensips/opensips34.cfg:170 > > > > > > 2023-08-03T12:20:09.298879+00:00 xsp2 /usr/local/sbin/opensips[52802]: > > CRITICAL:core:fix_expr: fix_actions error > > > > > > 2023-08-03T12:20:09.298905+00:00 xsp2 /usr/local/sbin/opensips[52802]: > > ERROR:core:main: failed to fix configuration with err code -6 > > > > > > 2023-08-03T12:20:09.298936+00:00 xsp2 /usr/local/sbin/opensips[52802]: > > INFO:core:cleanup: cleanup > > > > > > 2023-08-03T12:20:09.298962+00:00 xsp2 /usr/local/sbin/opensips[52802]: > > DBG:presence_xml:destroy: start > > > > > > 2023-08-03T12:20:09.298991+00:00 xsp2 /usr/local/sbin/opensips[52802]: > > NOTICE:presence:destroy: destroy module ... > > > > > > > > ___ > > Users mailing list > > Users@lists.opensips.org > > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > > ___ > Users mailing list > Users@lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users >___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] opensips v 3.3 to 3.4 on Oracle cloud ARM
Hi, I took a look at it but I did not do anything with it.
I read through the xml nathelper_admin.xml but there the same flags as in the
doc.
In that case
nat_uac_test(23) should use flag 23 and I can't find what flag that is. It
says that a CSV file can be provided?
if the call was nat_uac_test(4), it would now be nat_uac_test(*private-via*) ??
Where could I obtain this CSV?
Regards,
Ronald Geerligs
# initial NAT handling; detect if the request comes from behind a NAT
# and apply contact fixing
force_rport();
if (nat_uac_test(23)) {
if (is_method("REGISTER")) {
fix_nated_register();
setbflag("NAT");
} else {
fix_nated_contact();
setflag("NAT");
}
}
August 4, 2023 at 1:06 PM, "Răzvan Crainea" wrote:
>
> The migration document[1] clearly states to "Check the module docs for
> the flags parameters of the fix_nated_sdp() and nat_uac_test() functions
> for the mapping between the old and new flag names." Did you do that?
> You might have missed the fact that the nat_uac_test() function no
> longer receives arguments as integers, they have to be strings. Please
> check the 3.4 documentation[2].
>
> [2] https://opensips.org/docs/modules/3.4.x/nathelper.html#func_nat_uac_test
>
> PS: please do not attach files in a mailing list message
>
> Best regards,
>
> Răzvan Crainea
> OpenSIPS Core Developer / SIPhub CTO
> http://www.opensips-solutions.com/ / https://www.siphub.com/
>
> On 8/4/23 12:40, r...@rvgeerligs.nl wrote:
>
> >
> > Hi.
> >
> > cfg file attached and init.d/opensips34 attached.
> >
> > Regards,
> >
> > Ronald Geerligs
> >
> >
> >
> > August 4, 2023 at 9:48 AM, "Răzvan Crainea" >
> > >
> > wrote:
> >
> > Hi, Ronald!
> >
> > Usage of nat_uac_test has been changed between 3.3 and 3.4 [1]. Did you
> > update your function according to the 3.4 syntax? Can you paste the
> > snippet you are using?
> >
> > [1] https://www.opensips.org/Documentation/Migration-3-3-0-to-3-4-0
> >
> >
> > Best regards,
> >
> > Răzvan Crainea
> > OpenSIPS Core Developer / SIPhub CTO
> > http://www.opensips-solutions.com/
> > wrote:
> >
> > Hi ,
> > I compiled v 3.3 all is working. Compiled 3.4 and I get the
> > errors below.
> > I looked at the source 3.4, also at the source in version 3.3.5
> > (nathelper and nattraversal) but I could not simply replace the 3.4
> > source with the 3.3 source.
> > This looks like a compiler setting or a programm issue.
> > Please advice,
> > Ronald Geerligs
> > ---
> > error from logfile:
> > DBG:core:trace_prot_bind: has no bind api function
> > 2023-08-03T12:20:09.298662+00:00 xsp2
> > /usr/local/sbin/opensips[52802]:
> > DBG:core:init_xlog: failed to load trace protocol!
> > 2023-08-03T12:20:09.298686+00:00 xsp2
> > /usr/local/sbin/opensips[52802]:
> > DBG:core:count_module_procs: modules require 1 extra processes
> > 2023-08-03T12:20:09.298712+00:00 xsp2
> > /usr/local/sbin/opensips[52802]:
> > DBG:core:init_pkg_stats: setting stats for 18 processes
> > 2023-08-03T12:20:09.298741+00:00 xsp2
> > /usr/local/sbin/opensips[52802]:
> > DBG:core:fix_actions: fixing force_rport,
> > /etc/opensips/opensips34.cfg:169
> > 2023-08-03T12:20:09.298769+00:00 xsp2
> > /usr/local/sbin/opensips[52802]:
> > DBG:core:fix_actions: fixing nat_uac_test,
> > /etc/opensips/opensips34.cfg:170
> > 2023-08-03T12:20:09.298796+00:00 xsp2
> > /usr/local/sbin/opensips[52802]:
> > ERROR:core:fix_cmd: Param [1] expected to be a string or variable
> > 2023-08-03T12:20:09.298826+00:00 xsp2
> > /usr/local/sbin/opensips[52802]:
> > ERROR:core:fix_actions: Failed to fix command
> > 2023-08-03T12:20:09.298851+00:00 xsp2
> > /usr/local/sbin/opensips[52802]:
> > ERROR:core:fix_actions: fixing failed (code=-6) at
> > /etc/opensips/opensips34.cfg:170
> > 2023-08-03T12:20:09.298879+00:00 xsp2
> > /usr/local/sbin/opensips[52802]:
> > CRITICAL:core:fix_expr: fix_actions error
> > 2023-08-03T12:20:09.298905+00:00 xsp2
> > /usr/local/sbin/opensips[52802]:
> > ERROR:core:main: failed to fix configuration with err code -6
> > 2023-08-03T12:20:09.298936+00:00 xsp2
> > /usr/local/sbin/opensips[52802]:
> > INFO:core:cleanup: cleanup
> > 2023-08-03T12:20:09.298962+00:00 xsp2
> > /usr/local/sbin/opensips[52802]:
> > DBG:presence_xml:destroy: start
> > 2023-08-03T12:20:09.298991+00:00 xsp2
> > /usr/local/sbin/opensips[52802]:
> > NOTICE:presence:destroy: destroy module ...
> > ___
> > Users mailing list
> > Users@lists.opensips.org
> > http://lists.opensips.org/cgi-bin/mailman/listinfo/users
> >
Re: [OpenSIPS-Users] opensips v 3.3 to 3.4 on Oracle cloud ARM
Hi.
cfg file attached and init.d/opensips34 attached.
Regards,
Ronald Geerligs
August 4, 2023 at 9:48 AM, "Răzvan Crainea" wrote:
>
> Hi, Ronald!
>
> Usage of nat_uac_test has been changed between 3.3 and 3.4 [1]. Did you
> update your function according to the 3.4 syntax? Can you paste the
> snippet you are using?
>
> [1] https://www.opensips.org/Documentation/Migration-3-3-0-to-3-4-0
>
> Best regards,
>
> Răzvan Crainea
> OpenSIPS Core Developer / SIPhub CTO
> http://www.opensips-solutions.com/ / https://www.siphub.com/
>
> On 8/3/23 19:15, r...@rvgeerligs.nl wrote:
>
> >
> > Hi ,
> >
> > I compiled v 3.3 all is working. Compiled 3.4 and I get the errors below.
> >
> > I looked at the source 3.4, also at the source in version 3.3.5
> > (nathelper and nattraversal) but I could not simply replace the 3.4
> > source with the 3.3 source.
> >
> > This looks like a compiler setting or a programm issue.
> >
> > Please advice,
> >
> >
> > Ronald Geerligs
> >
> >
> > ---
> > error from logfile:
> >
> > DBG:core:trace_prot_bind: has no bind api function
> >
> >
> > 2023-08-03T12:20:09.298662+00:00 xsp2 /usr/local/sbin/opensips[52802]:
> > DBG:core:init_xlog: failed to load trace protocol!
> >
> >
> > 2023-08-03T12:20:09.298686+00:00 xsp2 /usr/local/sbin/opensips[52802]:
> > DBG:core:count_module_procs: modules require 1 extra processes
> >
> >
> > 2023-08-03T12:20:09.298712+00:00 xsp2 /usr/local/sbin/opensips[52802]:
> > DBG:core:init_pkg_stats: setting stats for 18 processes
> >
> >
> > 2023-08-03T12:20:09.298741+00:00 xsp2 /usr/local/sbin/opensips[52802]:
> > DBG:core:fix_actions: fixing force_rport, /etc/opensips/opensips34.cfg:169
> >
> >
> > 2023-08-03T12:20:09.298769+00:00 xsp2 /usr/local/sbin/opensips[52802]:
> > DBG:core:fix_actions: fixing nat_uac_test, /etc/opensips/opensips34.cfg:170
> >
> >
> > 2023-08-03T12:20:09.298796+00:00 xsp2 /usr/local/sbin/opensips[52802]:
> > ERROR:core:fix_cmd: Param [1] expected to be a string or variable
> >
> >
> > 2023-08-03T12:20:09.298826+00:00 xsp2 /usr/local/sbin/opensips[52802]:
> > ERROR:core:fix_actions: Failed to fix command
> >
> >
> > 2023-08-03T12:20:09.298851+00:00 xsp2 /usr/local/sbin/opensips[52802]:
> > ERROR:core:fix_actions: fixing failed (code=-6) at
> > /etc/opensips/opensips34.cfg:170
> >
> >
> > 2023-08-03T12:20:09.298879+00:00 xsp2 /usr/local/sbin/opensips[52802]:
> > CRITICAL:core:fix_expr: fix_actions error
> >
> >
> > 2023-08-03T12:20:09.298905+00:00 xsp2 /usr/local/sbin/opensips[52802]:
> > ERROR:core:main: failed to fix configuration with err code -6
> >
> >
> > 2023-08-03T12:20:09.298936+00:00 xsp2 /usr/local/sbin/opensips[52802]:
> > INFO:core:cleanup: cleanup
> >
> >
> > 2023-08-03T12:20:09.298962+00:00 xsp2 /usr/local/sbin/opensips[52802]:
> > DBG:presence_xml:destroy: start
> >
> >
> > 2023-08-03T12:20:09.298991+00:00 xsp2 /usr/local/sbin/opensips[52802]:
> > NOTICE:presence:destroy: destroy module ...
> >
> >
> >
> > ___
> > Users mailing list
> > Users@lists.opensips.org
> > http://lists.opensips.org/cgi-bin/mailman/listinfo/users
> >
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>#
# OpenSIPS residential configuration script
# by OpenSIPS Solutions
#
# This script was generated via "make menuconfig", from
# the "Residential" scenario.
# You can enable / disable more features / functionalities by
# re-generating the scenario with different options.#
#
# Please refer to the Core CookBook at:
# https://opensips.org/Resources/DocsCookbooks
# for a explanation of possible statements, functions and parameters.
#
### Global Parameters #
/* uncomment the following lines to enable debugging */
#debug_mode=yes
log_level=4
xlog_level=3
stderror_enabled=yes
syslog_enabled=yes
syslog_facility=LOG_LOCAL6
udp_workers=4
/* uncomment the next line to enable the auto temporary blacklisting of
not available destinations (default disabled) */
#disable_dns_blacklist=no
/* uncomment the next line to enable IPv6 lookup after IPv4 dns
lookup failures (default disabled) */
#dns_try_ipv6=yes
#socket=udp:127.0.0.1:5060 # CUSTOMIZE ME
#socket=tcp:127.0.0.1:5060 # CUSTOMIZE ME
socket=udp:10.0.0.186:5060 as 129.146.82.194:5060 # CUSTOMIZE ME
socket=tcp:10.0.0.186:5060 as 129.146.82.194:5060 # CUSTOMIZE ME
alias=xsp2.rvgeerligs.nl
### Modules Section
#set module path
mpath="/usr/local/lib64/opensips/modules/"
SIGNALING module
loadmodule "signaling.so"
StateLess module
loadmodule "sl.so"
Transaction Module
loadmodule "tm.so"
modparam("tm", "fr_timeout", 5)
modparam("tm", "fr_inv_timeout", 30)
modparam("tm", "restart_fr_on_each_reply", 0)
modparam("tm", "onreply_avp_mode",
Re: [OpenSIPS-Users] opensips v 3.3 to 3.4 on Oracle cloud ARM
Hi Răzvan,
The error happens at the if (nat_uac_test(23)), fix_nated_register(); This part
of the 3.4 cfg file is the same as in the 3.3 cfg file. It was generated with
osipsconfig in the 3.4 sbin directory, after compilation.
I did not do anything with the nathelper or nat_traversal .c files.
Regards,
Ronald Geerligs
--- from cfg file:
# initial NAT handling; detect if the request comes from behind a NAT
# and apply contact fixing
force_rport();
if (nat_uac_test(23)) {
if (is_method("REGISTER")) {
fix_nated_register();
setbflag("NAT");
} else {
fix_nated_contact();
setflag("NAT");
}
}
August 4, 2023 at 9:48 AM, "Răzvan Crainea" wrote:
>
> Hi, Ronald!
>
> Usage of nat_uac_test has been changed between 3.3 and 3.4 [1]. Did you
> update your function according to the 3.4 syntax? Can you paste the
> snippet you are using?
>
> [1] https://www.opensips.org/Documentation/Migration-3-3-0-to-3-4-0
>
> Best regards,
>
> Răzvan Crainea
> OpenSIPS Core Developer / SIPhub CTO
> http://www.opensips-solutions.com/ / https://www.siphub.com/
>
> On 8/3/23 19:15, r...@rvgeerligs.nl wrote:
>
> >
> > Hi ,
> >
> > I compiled v 3.3 all is working. Compiled 3.4 and I get the errors below.
> >
> > I looked at the source 3.4, also at the source in version 3.3.5
> > (nathelper and nattraversal) but I could not simply replace the 3.4
> > source with the 3.3 source.
> >
> > This looks like a compiler setting or a programm issue.
> >
> > Please advice,
> >
> >
> > Ronald Geerligs
> >
> >
> > ---
> > error from logfile:
> >
> > DBG:core:trace_prot_bind: has no bind api function
> >
> >
> > 2023-08-03T12:20:09.298662+00:00 xsp2 /usr/local/sbin/opensips[52802]:
> > DBG:core:init_xlog: failed to load trace protocol!
> >
> >
> > 2023-08-03T12:20:09.298686+00:00 xsp2 /usr/local/sbin/opensips[52802]:
> > DBG:core:count_module_procs: modules require 1 extra processes
> >
> >
> > 2023-08-03T12:20:09.298712+00:00 xsp2 /usr/local/sbin/opensips[52802]:
> > DBG:core:init_pkg_stats: setting stats for 18 processes
> >
> >
> > 2023-08-03T12:20:09.298741+00:00 xsp2 /usr/local/sbin/opensips[52802]:
> > DBG:core:fix_actions: fixing force_rport, /etc/opensips/opensips34.cfg:169
> >
> >
> > 2023-08-03T12:20:09.298769+00:00 xsp2 /usr/local/sbin/opensips[52802]:
> > DBG:core:fix_actions: fixing nat_uac_test, /etc/opensips/opensips34.cfg:170
> >
> >
> > 2023-08-03T12:20:09.298796+00:00 xsp2 /usr/local/sbin/opensips[52802]:
> > ERROR:core:fix_cmd: Param [1] expected to be a string or variable
> >
> >
> > 2023-08-03T12:20:09.298826+00:00 xsp2 /usr/local/sbin/opensips[52802]:
> > ERROR:core:fix_actions: Failed to fix command
> >
> >
> > 2023-08-03T12:20:09.298851+00:00 xsp2 /usr/local/sbin/opensips[52802]:
> > ERROR:core:fix_actions: fixing failed (code=-6) at
> > /etc/opensips/opensips34.cfg:170
> >
> >
> > 2023-08-03T12:20:09.298879+00:00 xsp2 /usr/local/sbin/opensips[52802]:
> > CRITICAL:core:fix_expr: fix_actions error
> >
> >
> > 2023-08-03T12:20:09.298905+00:00 xsp2 /usr/local/sbin/opensips[52802]:
> > ERROR:core:main: failed to fix configuration with err code -6
> >
> >
> > 2023-08-03T12:20:09.298936+00:00 xsp2 /usr/local/sbin/opensips[52802]:
> > INFO:core:cleanup: cleanup
> >
> >
> > 2023-08-03T12:20:09.298962+00:00 xsp2 /usr/local/sbin/opensips[52802]:
> > DBG:presence_xml:destroy: start
> >
> >
> > 2023-08-03T12:20:09.298991+00:00 xsp2 /usr/local/sbin/opensips[52802]:
> > NOTICE:presence:destroy: destroy module ...
> >
> >
> >
> > ___
> > Users mailing list
> > Users@lists.opensips.org
> > http://lists.opensips.org/cgi-bin/mailman/listinfo/users
> >
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] opensips v 3.3 to 3.4 on Oracle cloud ARM
Hi , I compiled v 3.3 all is working. Compiled 3.4 and I get the errors below. I looked at the source 3.4, also at the source in version 3.3.5 (nathelper and nattraversal) but I could not simply replace the 3.4 source with the 3.3 source. This looks like a compiler setting or a programm issue. Please advice, Ronald Geerligs --- error from logfile: DBG:core:trace_prot_bind: has no bind api function 2023-08-03T12:20:09.298662+00:00 xsp2 /usr/local/sbin/opensips[52802]: DBG:core:init_xlog: failed to load trace protocol! 2023-08-03T12:20:09.298686+00:00 xsp2 /usr/local/sbin/opensips[52802]: DBG:core:count_module_procs: modules require 1 extra processes 2023-08-03T12:20:09.298712+00:00 xsp2 /usr/local/sbin/opensips[52802]: DBG:core:init_pkg_stats: setting stats for 18 processes 2023-08-03T12:20:09.298741+00:00 xsp2 /usr/local/sbin/opensips[52802]: DBG:core:fix_actions: fixing force_rport, /etc/opensips/opensips34.cfg:169 2023-08-03T12:20:09.298769+00:00 xsp2 /usr/local/sbin/opensips[52802]: DBG:core:fix_actions: fixing nat_uac_test, /etc/opensips/opensips34.cfg:170 2023-08-03T12:20:09.298796+00:00 xsp2 /usr/local/sbin/opensips[52802]: ERROR:core:fix_cmd: Param [1] expected to be a string or variable 2023-08-03T12:20:09.298826+00:00 xsp2 /usr/local/sbin/opensips[52802]: ERROR:core:fix_actions: Failed to fix command 2023-08-03T12:20:09.298851+00:00 xsp2 /usr/local/sbin/opensips[52802]: ERROR:core:fix_actions: fixing failed (code=-6) at /etc/opensips/opensips34.cfg:170 2023-08-03T12:20:09.298879+00:00 xsp2 /usr/local/sbin/opensips[52802]: CRITICAL:core:fix_expr: fix_actions error 2023-08-03T12:20:09.298905+00:00 xsp2 /usr/local/sbin/opensips[52802]: ERROR:core:main: failed to fix configuration with err code -6 2023-08-03T12:20:09.298936+00:00 xsp2 /usr/local/sbin/opensips[52802]: INFO:core:cleanup: cleanup 2023-08-03T12:20:09.298962+00:00 xsp2 /usr/local/sbin/opensips[52802]: DBG:presence_xml:destroy: start 2023-08-03T12:20:09.298991+00:00 xsp2 /usr/local/sbin/opensips[52802]: NOTICE:presence:destroy: destroy module ...___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
