Hi Peter,
Flow tokens are essentially the link between a SIP address and a TCP or UDP connection to the endpoint. When an endpoint REGISTERs, these associations are created and stored in RAM - so when the VM (or the process) restarts, Bono loses that data, and is unable to send calls to the endpoint until it next REGISTERs and re-creates that association. If you re-register your endpoint after restarting Bono, it should start working again. Best, Rob ________________________________ From: Clearwater <[email protected]> on behalf of Peter Skrzynski <[email protected]> Sent: 20 October 2017 04:26 To: [email protected] Subject: [Project Clearwater] Problem after Bono restart Hi Clearwater, I am running a manual install Release-89 bono/sprout/homestead/ibcf/dns configuration. Recently I had need to restart the Bono node (virtual machine). Following this, INVITE’s from both the external user side, and from the internal network side (from Sprout) were being rejected. Service was not restored until some time later. I am not certain what restored the service. Looking at the log file on Bono, it can be seen that the INVITE is rejected because of the lack of a flow token or route request. Are you able to explain what the flow tokens are, and how they work, and more importantly, what is the means to restore service after the Bono node has been restarted??? Or do I just have to wait until the flow tokens are recreated? What creates them? Regards, Peter Example on Bono for INVITE from network side (Sprout)… 17-10-2017 03:14:53.975 UTC Debug bono.cpp:1346: Flow identifier in Route header = 4fBpmFpN25 17-10-2017 03:14:53.975 UTC Debug flowtable.cpp:164: Find flow for flow token 4fBpmFpN25 17-10-2017 03:14:53.975 UTC Error bono.cpp:1357: Route header flow identifier failed to correlate 17-10-2017 03:14:53.975 UTC Debug acr.cpp:49: Created ACR (0x7ff7f4002880) 17-10-2017 03:14:53.975UTC Info bono.cpp:764: Reject INVITE request with 430 status code where the flow identifier comes from the INVITE… Route: <sip:[email protected]:5058;transport=TCP;lr;ob> Example on Bono for INVITE from external user side… 17-10-2017 03:28:36.581 UTC Debug bono.cpp:959: Request received on authentication flow – check for Service-Route 17-10-2017 03:28:36.581 UTC Debug pjutils.cpp:312: From header 0x7f5c700391d0 17-10-2017 03:28:36.581 UTC Debug pjutils.cpp:314: Served used from From header (0x7f5c70039278) 17-10-2017 03:28:36.581 UTC Verbose bono.cpp:966: Found Service-Route for served user sip:[email protected] - 17-10-2017 03:28:36.581 UTC Info bono.cpp:1029: Route request to upstream proxy sip:sprout.abcd.peter.co.nz:5054;transport=TCP;lr 17-10-2017 03:28:36.581 UTC Info bono.cpp:1377: Rejecting request from untrusted source 17-10-2017 03:28:36.581 UTC Debug flowtable.cpp:616: Dialog count now 1 for flow sip:[email protected] 17-10-2017 03:28:36.581 UTC Debug acr.cpp:49: Created ACR (0x7f5c70006e50) 17-10-2017 03:28:36.581 UTC Info bono.cpp:764: Reject INVITE request with 403 status code Peter Skrzynski Technical Sales Support NEC New Zealand Limited Level 2, 186 Willis Street, PO Box: 1936, Wellington 6011, New Zealand T: 043816257, M: 0274849530, F: +6443811110 [email protected]<mailto:[email protected]> nz.nec.com<http://nz.nec.com> [cid:[email protected]] Please consider the environment before printing this email Attention: The information contained in this message and or attachments is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination, copying or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any system and destroy any copies. NEC has no liability for any act or omission in reliance on the email or any attachment. Before opening this email or any attachment(s), please check them for viruses. NEC is not responsible for any viruses in this email or any attachment(s); any changes made to this email or any attachment(s) after they are sent; or any effects this email or any attachment(s) have on your network or computer system.
_______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org
