ndemou Posted November 20, 2014 Report Share Posted November 20, 2014 After a restart of the service I noticed that I had a thousand messages "[0] Need a session" yesterday and they keep comming up today. Everything else seems normal but I had zero such messages before. What's the meaning of the message? Should I take any action? grep "^\[0\]" pbx/log/2014-11-19.txt | sed -e 's/^\(\[.\]\) [^:]*:/\1/'|grep -v 'message repeated'|sort|uniq -c|sort -n 1 [0] SMTP: Illegal state 2 [0] Hangup reason: wait 3 [0] Removing expired call 1120 [0] Need a session The time distribution is not uniform (errors seem to appear corelate with rush hours or maybe during hours with web UI activity): grep ' call created ' pbx/log/2014-11-19.txt |sed -e 's/^...//' -e 's/....:.*$//'|uniq -c 67 2014111900 15 2014111901 6 2014111902 4 2014111903 1 2014111906 17 2014111907 77 2014111908 257 2014111909 350 2014111910 484 2014111911 634 2014111912 482 2014111913 456 2014111914 319 2014111915 235 2014111916 195 2014111917 123 2014111918 122 2014111919 132 2014111920 128 2014111921 143 2014111922 78 2014111923 grep "^\[0\].*a session" pbx/log/2014-11-19.txt |sed -e 's/....://'|uniq -c 96 [0] 2014111909 Need a session 227 [0] 2014111910 Need a session 207 [0] 2014111911 Need a session 197 [0] 2014111912 Need a session 253 [0] 2014111913 Need a session 134 [0] 2014111914 Need a session 6 [0] 2014111915 Need a session after switching to debug level 9 this is a typical pattern of log messages before the "Need a session": [8] 20141120120315: Port 13: state code from 0 to 100 [9] 20141120120315: Port 13: Adding codec PCMU/8000 to available list [9] 20141120120315: Port 13: Adding codec PCMA/8000 to available list [9] 20141120120315: Port 13: Adding codec G729/8000 to available list [9] 20141120120315: Port 13: Update codecs preference size 4, available codecs size 4 [9] 20141120120315: Resolve 6212348: url sip:2.84.223.249:1270;transport=udp [9] 20141120120315: Resolve 6212348: a udp 2.84.223.249 1270 [9] 20141120120315: Resolve 6212348: udp 2.84.223.249 1270 [9] 20141120120315: UDP(IPv4): Opening socket on 0.0.0.0:58190 [9] 20141120120315: UDP(IPv4): Opening socket on 0.0.0.0:58191 [9] 20141120120315: UDP(IPv6): Opening socket on [::]:58190 [9] 20141120120315: UDP(IPv6): Opening socket on [::]:58191 [0] 20141120120315: Need a session [0] 20141120120315: Last message repeated 2 times Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted November 20, 2014 Report Share Posted November 20, 2014 It means that the PBX needs a HTTP session in order to complete a request. As far as I can see this is not related to a phone call. This can happen when a session expires, e.g. a user has not done anything for a longer time and then requests something that would require a still valid session. IMHO not very serious, although the log level is pretty low. Quote Link to comment Share on other sites More sharing options...
ndemou Posted November 22, 2014 Author Report Share Posted November 22, 2014 It must have to do with https requests that are sent from 2.84.223.249 to the PBX in order for it to initiate calls. The calls get initiated just fine but for some reason the PBX logs this message anyway. I'll get back with more details after contacting the admin of that application. Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted November 23, 2014 Report Share Posted November 23, 2014 Could be that the PBX tries to send back a web page saying "okay your call is being started" which has content that requires a session. Again, this would not be serious; it just would not look as pretty as it could. Quote Link to comment Share on other sites More sharing options...
ndemou Posted November 25, 2014 Author Report Share Posted November 25, 2014 OK I've verified that it really has to do with the https initiated calls and you're of course right that it's not serious. I guess I'll just grep them out of my reports. Thanks for the help Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.