Please open a bug with respect to this issue. This error should end up in the error_route. Try to run tcpdump with buffer rotation and see if you can spot the bogus reply.
Regards, Ovidiu Sas On Mon, Apr 13, 2009 at 4:30 PM, Geoffrey Mina <[email protected]> wrote: > OK, the error has occurred again today, and the error_route didn't > catch the condition. Any other ideas? > > thanks, > Geoff > > On Sun, Apr 12, 2009 at 6:42 PM, Geoffrey Mina <[email protected]> wrote: >> Ovidiu, >> Thanks for your continued input. I currently have the error_route >> block configured with some logging. I am hoping this will be >> sufficient to capture the condition. The error hasn't happened today, >> traffic has been very light as it is Eastern and Passover, and I >> suppose people have better things to do than be on the phone :) >> >> If I get the log message and nothing from error_route, I will >> definitely do a tcpdump of the SIP port and try to correlate the >> timing. >> >> thanks! >> Geoff >> >> On Sun, Apr 12, 2009 at 8:46 AM, Ovidiu Sas <[email protected]> wrote: >>> Hello Geoffrey, >>> >>> With tcpdump, you can capture data in buffers and rotate the buffers >>> and keep only the latest 2-3 buffers (check the man page). >>> As soon as the error arise, you stop the traffic and your bogus >>> message should be in your last buffer. >>> Just an idea ... >>> >>> Also, if your cps is not very high, you can print the callid of each >>> request/reply, and when the error arise, you can correlate it with the >>> callid. >>> >>> >>> Regards, >>> Ovidiu Sas >>> >>> On Sun, Apr 12, 2009 at 8:06 AM, Geoffrey Mina <[email protected]> >>> wrote: >>>> Ovidiu, >>>> Thank you for your pointer. I could capture all the SIP traffic, but >>>> it would be a LOT of data to sift through. This machine processes >>>> hundreds of thousands of calls per day. I have tried the error_route >>>> handler to see if it shows up there... fingers crossed. I was unaware >>>> of that handler before now. >>>> >>>> Thanks for the info! >>>> Geoff >>>> >>>> On Sat, Apr 11, 2009 at 8:38 PM, Ovidiu Sas <[email protected]> wrote: >>>>> How often do you get this error? >>>>> IIRC, last time when I got this type of error it was related to a >>>>> missing Via header into a SIP reply. >>>>> Can you capture/sniff the traffic and check if all the received >>>>> replies are sane (via header is present)? >>>>> >>>>> Another idea would be to capture the bogus message into the error_route: >>>>> http://www.kamailio.net/dokuwiki/doku.php/core-cookbook:1.5.x#error_route >>>>> and then print the message via $mb: >>>>> http://www.kamailio.net/dokuwiki/doku.php/pseudovariables:1.5.x#sip_message_buffer >>>>> >>>>> I haven't checked the code to see if this type of error will end up in >>>>> the error_route, but is it worth a try. >>>>> If it's not caught, please open a bug, because it should be. >>>>> >>>>> >>>>> Regards, >>>>> Ovidiu Sas >>>>> >>>>> On Sat, Apr 11, 2009 at 5:58 PM, Geoffrey Mina <[email protected]> >>>>> wrote: >>>>>> Tried adding that log into my onreply_route[1] block, but it didn't >>>>>> work. I can't seem to figure out I can possibly capture the SIP >>>>>> message which is generating this error. Any help would be much >>>>>> appreciated. >>>>>> >>>>>> On Fri, Apr 10, 2009 at 10:23 PM, Geoffrey Mina <[email protected]> >>>>>> wrote: >>>>>>> Perhaps I should clarify what I am looking for a bit. I am guessing >>>>>>> based on the log "no via found in reply" that I would need to check >>>>>>> for this condition in my onreply_route[1] block. >>>>>>> >>>>>>> Based on my knowledge of SIP, all reply responses are REQUIRED to have >>>>>>> a VIA header to ensure the response traverses the same path as the >>>>>>> request... correct? >>>>>>> >>>>>>> Would the following effectively deal with this condition, or would >>>>>>> sending a 500 error in response to a reply cause problems down stream? >>>>>>> >>>>>>> onreply_route[1]{ >>>>>>> if(!is_present_hf("Via")){ >>>>>>> sl_reply_error("500","No Via found in response."); >>>>>>> } >>>>>>> } >>>>>>> >>>>>>> Thanks for anyone's assistance. >>>>>>> Geoff >>>>>>> >>>>>>> On Fri, Apr 10, 2009 at 12:02 PM, Geoffrey Mina >>>>>>> <[email protected]> wrote: >>>>>>>> Hello, >>>>>>>> I am seeing the following message repeatedly in my log file. I am >>>>>>>> guessing I have a server or servers misbehaving. Where might I be >>>>>>>> able to check for this error condition and log appropriately? I have >>>>>>>> attached my current configuration file for reference. >>>>>>>> >>>>>>>> Thanks! >>>>>>>> Geoff >>>>>>>> >>>>>>>> >>>>>>>> Apr 10 11:45:40 atl-sipgateway2 /usr/local/sbin/kamailio[15487]: >>>>>>>> ERROR:core:receive_msg: no via found in reply >>>>>>>> Apr 10 11:45:42 atl-sipgateway2 /usr/local/sbin/kamailio[15490]: >>>>>>>> ERROR:core:receive_msg: no via found in reply >>>>>>>> Apr 10 11:45:46 atl-sipgateway2 /usr/local/sbin/kamailio[15490]: >>>>>>>> ERROR:core:receive_msg: no via found in reply >>>>>>>> Apr 10 11:45:50 atl-sipgateway2 /usr/local/sbin/kamailio[15507]: >>>>>>>> ERROR:core:receive_msg: no via found in reply >>>>>>>> Apr 10 11:45:54 atl-sipgateway2 /usr/local/sbin/kamailio[15497]: >>>>>>>> ERROR:core:receive_msg: no via found in reply >>>>>>>> Apr 10 11:45:58 atl-sipgateway2 /usr/local/sbin/kamailio[15491]: >>>>>>>> ERROR:core:receive_msg: no via found in reply >>>>>>>> Apr 10 11:46:02 atl-sipgateway2 /usr/local/sbin/kamailio[15490]: >>>>>>>> ERROR:core:receive_msg: no via found in reply >>>>>>>> Apr 10 11:46:06 atl-sipgateway2 /usr/local/sbin/kamailio[15485]: >>>>>>>> ERROR:core:receive_msg: no via found in reply >>>>>>>> Apr 10 11:47:46 atl-sipgateway2 /usr/local/sbin/kamailio[15485]: >>>>>>>> ERROR:core:receive_msg: no via found in reply >>>>>>>> Apr 10 11:47:47 atl-sipgateway2 /usr/local/sbin/kamailio[15486]: >>>>>>>> ERROR:core:receive_msg: no via found in reply >>>>>>>> Apr 10 11:47:48 atl-sipgateway2 /usr/local/sbin/kamailio[15507]: >>>>>>>> ERROR:core:receive_msg: no via found in reply >>>>>>>> Apr 10 11:47:50 atl-sipgateway2 /usr/local/sbin/kamailio[15503]: >>>>>>>> ERROR:core:receive_msg: no via found in reply >>>>>>>> Apr 10 11:47:54 atl-sipgateway2 /usr/local/sbin/kamailio[15492]: >>>>>>>> ERROR:core:receive_msg: no via found in reply >>>>>>>> Apr 10 11:47:58 atl-sipgateway2 /usr/local/sbin/kamailio[15485]: >>>>>>>> ERROR:core:receive_msg: no via found in reply >>>>>>>> Apr 10 11:48:02 atl-sipgateway2 /usr/local/sbin/kamailio[15490]: >>>>>>>> ERROR:core:receive_msg: no via found in reply >>>>>>>> Apr 10 11:48:06 atl-sipgateway2 /usr/local/sbin/kamailio[15491]: >>>>>>>> ERROR:core:receive_msg: no via found in reply >>>>>>>> Apr 10 11:48:10 atl-sipgateway2 /usr/local/sbin/kamailio[15492]: >>>>>>>> ERROR:core:receive_msg: no via found in reply >>>>>>>> >>>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Kamailio (OpenSER) - Users mailing list >>>>>> [email protected] >>>>>> http://lists.kamailio.org/cgi-bin/mailman/listinfo/users >>>>>> http://lists.openser-project.org/cgi-bin/mailman/listinfo/users >>>>>> >>>>> >>>> >>> >> > _______________________________________________ Kamailio (OpenSER) - Users mailing list [email protected] http://lists.kamailio.org/cgi-bin/mailman/listinfo/users http://lists.openser-project.org/cgi-bin/mailman/listinfo/users
