<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> </head> <body> Hi Li, For passing around data between the b2b request route and local_route, in the context of an ongoing B2B session, you can use the $b2b_logic.ctx variable[1]. That would take care of transferring the Cseq from step 1 to step 2 and the id from step 3 to step 4. As for your cseq map, you can use the cachedb_local module, and maybe the $b2b_logic.key variable alongside Cseq2 for building a proper key. [1] <a class="moz-txt-link-freetext" href="https://opensips.org/docs/modules/3.3.x/b2b_logic.html#b2b_logic.key">https://opensips.org/docs/modules/3.3.x/b2b_logic.html#b2b_logic.key</a> Regards, <pre class="moz-signature" cols="72">-- Vlad Patrascu OpenSIPS Core Developer <a class="moz-txt-link-freetext" href="http://www.opensips-solutions.com">http://www.opensips-solutions.com</a></pre> <div class="moz-cite-prefix">On 22.07.2022 23:02, Li Cai wrote: </div> <blockquote type="cite" cite="mid:SA1PR09MB80004620A34C1A7EE463113E8E909@SA1PR09MB8000.namprd09.prod.outlook.com"> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> <meta name="Generator" content="Microsoft Word 15 (filtered medium)"> <style>@font-face {font-family:Wingdings; panose-1:5 0 0 0 0 0 0 0 0 0;}@font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4;}@font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4;}p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0cm; font-size:11.0pt; font-family:"Calibri",sans-serif; mso-fareast-language:EN-US;}p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph {mso-style-priority:34; margin-top:0cm; margin-right:0cm; margin-bottom:0cm; margin-left:36.0pt; font-size:11.0pt; font-family:"Calibri",sans-serif; mso-fareast-language:EN-US;}span.EmailStyle18 {mso-style-type:personal-compose; font-family:"Calibri",sans-serif; color:windowtext;}.MsoChpDefault {mso-style-type:export-only; font-size:10.0pt; font-family:"Calibri",sans-serif; mso-fareast-language:EN-US;}div.WordSection1 {page:WordSection1;}ol {margin-bottom:0cm;}ul {margin-bottom:0cm;}</style> <div class="WordSection1"> Hi experts,<o:p></o:p> <o:p> </o:p> I’m working on the implementation for ‘2.4.6 Multiple REFER Requests in a Dialog’ of RFC3515 in a B2B SIP Proxy. Right now, I got stuck with two problems in the solution. Please see the paragraph from RFC- <o:p></o:p> <o:p> </o:p> A REFER creates an implicit subscription sharing the dialog<o:p></o:p> identifiers in the REFER request. If more than one REFER is issued<o:p></o:p> in the same dialog (a second attempt at transferring a call for<o:p></o:p> example), the dialog identifiers do not provide enough information to<o:p></o:p> associate the resulting NOTIFYs with the proper REFER.<o:p></o:p> <o:p> </o:p> Thus, for the second and subsequent REFER requests a UA receives in a<o:p></o:p> given dialog, it MUST include an id parameter[2] in the Event header<o:p></o:p> field of each NOTIFY containing the sequence number (the number from<o:p></o:p> the CSeq header field value) of the REFER this NOTIFY is associated<o:p></o:p> with. This id parameter MAY be included in NOTIFYs to the first<o:p></o:p> REFER a UA receives in a given dialog. A SUBSCRIBE sent to refresh<o:p></o:p> or terminate this subscription MUST contain this id parameter.<o:p></o:p> <o:p> </o:p> Different from the definition in RFC, the NOTIFY forwarded by the proxy contains the same Id in Event header as the other side. Please see the below chart –<o:p></o:p> B2BProxy<o:p></o:p> | <o:p></o:p> <- REFER 2 (Cseq=2) | <-REFER 1 (Cseq=1003)<o:p></o:p> . . . | . . .<o:p></o:p> ->NOTIFY 1 (event:id=2) | ->NOTIFY 2 (event:id=2)<o:p></o:p> <o:p> </o:p> The current problem is, the above NOTIFY on the right side should include ‘id=1003’ instead of ‘id=2’.<o:p></o:p> <o:p> </o:p> <o:p> </o:p> The solution I’m trying is as in the following flow –<o:p></o:p> 1. get CSeq 1 of REFER 1 in route[b2b_request]{} -><o:p></o:p> 2. get CSeq 2 of REFER 2 in local_route{}, then save the pair(key=CSeq2, value=CSeq1) in a map set-><o:p></o:p> 3. get Id from NOTIFY 1 event in route[b2b_request]{} -><o:p></o:p> 4. use Id as key then get matched CSeq1 from the map set, use remove_hf() and append_hf() to modify the event header in local_route{}<o:p></o:p> <o:p> </o:p> My two questions are:<o:p></o:p> <ol style="margin-top:0cm" type="1" start="1"> <li class="MsoListParagraph" style="margin-left:0cm;mso-list:l1 level1 lfo2">To transfer Cseq 1 from step1 to step2, I tried a variable in the AVP type but it didn’t work. The script variable can work but it doesn’t fit because the processing is based on per request. Can I ask if you have any suggest on how to transfer the value from route[b2b_request]{} to local_route{}? <o:p></o:p></li> <li class="MsoListParagraph" style="margin-left:0cm;mso-list:l1 level1 lfo2">In the step2, I tried to create and operate a JSON map set to save the CSeq pairs. But the JSON data didn’t work for me.<o:p></o:p></li> </ol> My source : <o:p></o:p> $json(csList) = ””; # Initialize the data set, not sure if it’s correct<o:p></o:p> $json(csList/”$cs”) = “$avp(csNum)”;<o:p></o:p> The error I got:<o:p></o:p> ERROR:core:do_assign: setting PV failed<o:p></o:p> ERROR:core:do_assign: error at /usr/local//et/opensips/opensips.cfg:531<o:p></o:p> <o:p> </o:p> <o:p> </o:p> Thank you very much for the help! Any your suggests are very welcomed. <o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> Thanks,<o:p></o:p> Li<o:p></o:p> <o:p></o:p> <o:p> </o:p> <o:p></o:p> </div> NOTICE TO RECIPIENT: This email, including attachments, may contain information which is confidential, proprietary, attorney-client privileged and / or controlled under U.S. export laws and regulations and may be restricted from disclosure by applicable State and Federal law. Nothing in this email shall create any legal binding agreement between the parties unless expressly stated herein and provided by an authorized representative of Comtech Telecommunications Corp. or its subsidiaries. If you are not the intended recipient of this message, be advised that any dissemination, distribution, or use of the contents of this message is strictly prohibited. If you received this message in error, please notify us immediately by return email and permanently delete all copies of the original email and any attached documentation from any computer or other media. <fieldset class="moz-mime-attachment-header"></fieldset> <pre class="moz-quote-pre" wrap="">_______________________________________________ Users mailing list <a class="moz-txt-link-abbreviated" href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a> <a class="moz-txt-link-freetext" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a> </pre> </blockquote> </body> </html>