[OpenSIPS-Users] SDP
How to see the SDP in opensips? -- Regards, B.Prathibha ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] [Blog] The SQL support, reloaded (in OpenSIPS 3.5)
Born from the AVPops ashes, the SQLops module is here to provide JSON structured SQL querying capabilities, from script level, with prepared statements support and many other facilities and boosts 😍. Read all about this https://blog.opensips.org/2024/03/13/the-sql-support-reloaded/ Enjoy, -- Bogdan-Andrei Iancu OpenSIPS Founder and Developer https://www.opensips-solutions.com https://www.siphub.com ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] How to change the a=sendrecv in SDP
Hi (again ...) I've found out how to strip out the o= to separate values ... but now I want to change the a=sendrecv to a=sendonly The cause is that our pbx's don't conform to either RFC2543 hold type: null connection IP detected, nor RFC3264 hold type: inactive or sendonly attributes detected but use the RFC5359 re-invite indicating call hold via session version incremented by 1. So now I've trying to make a workaround with the help of OpenSips .. Can you please help me with that ... // Regards ... Stefan Carlsson ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] OpenSIPs generate PRACK
Hello, two questions about mi_script module: 1. I don't understand well this sentence: "Moreover, if the running MI /command / is configured to run in asynchronous mode (such as /t_uac_dlg/ the command blocks in a busy waiting manner until the response is received." can I or I can't use t_uac_dlg in asynchronous mode? 2. Can I indicate more than un parameters in the line like: * $avp(params) = "method","callid","From:"; * or is one value for line? Same for $avp(vals) Thank you Regards --- I'm SoCIaL, MayBe El 26/02/2024 a las 7:43 a. m., Bogdan-Andrei Iancu escribió: yes, you can use the b2b_logic (together with b2b_entities) for that, but it may be a too heavy tool for the purpose. Maybe you can try to generate the PRACK from OpenSIPS level by using the t_uac_dlg MI function [1] via the mi_script module [2] - basically to trigger that MI cmd from the onreply_route, when receiving the 180 reply. [1] https://opensips.org/html/docs/modules/3.4.x/tm.html#mi_t_uac_dlg [2] https://opensips.org/html/docs/modules/3.4.x/mi_script.html#afunc_mi Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer https://www.opensips-solutions.com https://www.siphub.com On 25.02.2024 14:54, Social Boh wrote: I know the best way is the original caller handle and reply the 183, but I HAVE to do this at OpenSIPs level. Can I use B2B_Entities and B2B_logic to do this? Is there a scenario to use tu parse and reply the 183? Thank you --- I'm SoCIaL, MayBe El 16/02/2024 a las 11:31 a. m., Bogdan-Andrei Iancu escribió: I agree here, the 183 must be relayed back to the original caller (which generate the received INVITE) and let it do the PRACK - this confirmation must be end-2-end in the dialog. Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer https://www.opensips-solutions.com https://www.siphub.com On 12.02.2024 11:36, Ihor Olkhovskyi wrote: You should relay 183 to original source (ione that is sending INVITE) and got PRACK from there. That would be the most correct way of handling this Le lun. 12 févr. 2024 à 02:29, Social Boh a écrit : Maybe someone can help me. This is the scenario. OpenSIPs receive a INVITE and send it to a server that reply with a 302 message (always) Then OpenSIPs, in the failure route, take the user part present in the 302 contact header, change the destination IP and send with t_relay The destination reply with a 183 with Require: 100rel header so OpenSIPs have to reply with a PRACK. This is my problem. I don't know which is the best way to handle this (the PRACK) Thank you Regards --- I'm SoCIaL, MayBe El 9/02/2024 a las 6:46 a. m., Social Boh escribió: > Hello list, > > can OpenSIPs generate a PRACK message to reply a 180/183 message? > > Thank you > > Regards > > --- > I'm SoCIaL, MayBe > > > ___ > 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 -- Best regards, Ihor (Igor) ___ 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] 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
