Thanks for your response! I’ll give this solution a try and see if it works for my situation.
On Fri, 31 Jan 2025 at 3:31 PM, <users-requ...@lists.opensips.org> wrote: > Send Users mailing list submissions to > users@lists.opensips.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > or, via email, send a message with subject or body 'help' to > users-requ...@lists.opensips.org > > You can reach the person managing the list at > users-ow...@lists.opensips.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Users digest..." > > > Today's Topics: > > 1. Re: Push Notification: fr_inv_timeout and t_wait_for_branches > and 480 (inderjeet sharma) > 2. Re: Push Notification: fr_inv_timeout and t_wait_for_branches > and 480 (Prathibha B) > 3. Re: Push Notification: fr_inv_timeout and t_wait_for_branches > and 480 (Bogdan-Andrei Iancu) > 4. Re: SIP Push Notification (Bogdan-Andrei Iancu) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 31 Jan 2025 14:06:10 +0530 > From: inderjeet sharma <inder.it...@gmail.com> > To: users@lists.opensips.org > Subject: Re: [OpenSIPS-Users] Push Notification: fr_inv_timeout and > t_wait_for_branches and 480 > Message-ID: > <CAOAEC9HOtte7TSG8jSgiXWJAG= > fzbxqxmogsetzkj1ymp6q...@mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Hi john, > > I’m stuck in the same situation. By any chance, did you find a solution to > this issue? > > I just want to reject the call immediately when I receive a 480 response > from the registered device, instead of waiting until fr_inv_timeout. > Thanks > Inderjeet > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > http://lists.opensips.org/pipermail/users/attachments/20250131/373fb0d1/attachment-0001.html > > > > ------------------------------ > > Message: 2 > Date: Fri, 31 Jan 2025 15:00:46 +0530 > From: Prathibha B <prathibhab....@gmail.com> > To: OpenSIPS users mailling list <users@lists.opensips.org> > Subject: Re: [OpenSIPS-Users] Push Notification: fr_inv_timeout and > t_wait_for_branches and 480 > Message-ID: > <CAJh_-cB0HehB0n5=4z2fvJyk0U96mwiR5Zx=Ke2= > awwkkps...@mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > No, I didn't get any solution. > > On Fri, 31 Jan 2025 at 14:09, inderjeet sharma <inder.it...@gmail.com> > wrote: > > > Hi john, > > > > I’m stuck in the same situation. By any chance, did you find a solution > to > > this issue? > > > > I just want to reject the call immediately when I receive a 480 response > > from the registered device, instead of waiting until fr_inv_timeout. > > Thanks > > Inderjeet > > > > _______________________________________________ > > Users mailing list > > Users@lists.opensips.org > > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > > > -- > Regards, > B.Prathibha > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > http://lists.opensips.org/pipermail/users/attachments/20250131/43cb2ce0/attachment-0001.html > > > > ------------------------------ > > Message: 3 > Date: Fri, 31 Jan 2025 11:55:29 +0200 > From: Bogdan-Andrei Iancu <bog...@opensips.org> > To: OpenSIPS users mailling list <users@lists.opensips.org>, Prathibha > B <prathibhab....@gmail.com> > Subject: Re: [OpenSIPS-Users] Push Notification: fr_inv_timeout and > t_wait_for_branches and 480 > Message-ID: <ec844fa2-fe98-44ef-bbb9-1d4f6f47d...@opensips.org> > Content-Type: text/plain; charset="utf-8"; Format="flowed" > > Hi, > > check this > > https://opensips.org/html/docs/modules/3.4.x/tm.html#func_t_wait_no_more_branches > > or use the param for > > https://opensips.org/html/docs/modules/3.4.x/tm.html#func_t_wait_for_new_branches > > Regards, > > Bogdan-Andrei Iancu > > OpenSIPS Founder and Developer > https://www.opensips-solutions.com > https://www.siphub.com > > On 31.01.2025 11:30, Prathibha B wrote: > > No, I didn't get any solution. > > > > On Fri, 31 Jan 2025 at 14:09, inderjeet sharma <inder.it...@gmail.com> > > wrote: > > > > Hi john, > > > > I’m stuck in the same situation. By any chance, did you find a > > solution to this issue? > > > > I just want to reject the call immediately when I receive a 480 > > response from the registered device, instead of waiting until > > fr_inv_timeout. > > > > Thanks > > Inderjeet > > > > _______________________________________________ > > Users mailing list > > Users@lists.opensips.org > > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > > > > > > -- > > Regards, > > B.Prathibha > > > > _______________________________________________ > > Users mailing list > > Users@lists.opensips.org > > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > http://lists.opensips.org/pipermail/users/attachments/20250131/427ae71e/attachment-0001.html > > > > ------------------------------ > > Message: 4 > Date: Fri, 31 Jan 2025 12:00:16 +0200 > From: Bogdan-Andrei Iancu <bog...@opensips.org> > To: OpenSIPS users mailling list <users@lists.opensips.org>, Prathibha > B <prathibhab....@gmail.com> > Subject: Re: [OpenSIPS-Users] SIP Push Notification > Message-ID: <20e782ee-b153-40f1-b441-4cc58e3ba...@opensips.org> > Content-Type: text/plain; charset="utf-8"; Format="flowed" > > The error has nothing to do with PN, but with the way you use the > rest_post() function. The error log is 100% clear - the third param you > pass to the function is not a string! > > Regards, > > Bogdan-Andrei Iancu > > OpenSIPS Founder and Developer > https://www.opensips-solutions.com > https://www.siphub.com > > On 30.01.2025 09:25, Prathibha B wrote: > > this is my route for sending Push Notification: > > > > route [PN_SEND] > > { > > # send a PN using, for example, exec or rest_client > > # Define FCM URL > > $var(fcm_url) = > > "https://fcm.googleapis.com/v1/projects/xxx/messages:send > > < > https://fcm.googleapis.com/v1/projects/asterisk-push-notificaiton/messages:send > >"; > > > > # Set HTTP headers > > rest_append_hf("Authorization: Bearer ya29.c.c0AS..."); > > #rest_append_hf("Content-Type: application/json"); > > rest_append_hf("Content-Type: \"application/json\""); > > > > # Create JSON payload > > $var(json_payload) = '{\"message\": {\"token\": > > \"xxx\",\"notification\": {\"title\": \"Notification Title\",\"body\": > > \"Notification Body\"}}}'; > > > > # Send REST POST request > > if (launch(rest_post($var(fcm_url), "$var(json_payload)", > > $avp(response_body), $avp(response_code)))) { > > xlog("L_INFO", "Push notification sent successfully. Response > > code: $avp(response_code)\n"); > > } else { > > xlog("L_ERR", "Failed to send push notification. Response > > code: $avp(response_code)\n"); > > } > > } > > > > But I get the following error while running Opensips: > > ERROR:rest_client:rest_append_hf_method: header field buffer too small > > Jan 30 12:29:09 ngdcs opensips[102753]: ERROR:core:get_cmd_fixups: > > Variable in param [3] is not a string > > Jan 30 12:29:09 ngdcs opensips[102753]: ERROR:core:do_action: Failed > > to get fixups for launch command <rest_post> > > > > Can you pls help to resolve the issue? > > > > -- > > Regards, > > B.Prathibha > > > > _______________________________________________ > > Users mailing list > > Users@lists.opensips.org > > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > http://lists.opensips.org/pipermail/users/attachments/20250131/6df7996c/attachment.html > > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > Users mailing list > Users@lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > ------------------------------ > > End of Users Digest, Vol 198, Issue 32 > ************************************** >
_______________________________________________ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
