ndemou

Sure there is an /etc/init.d/pbxsrv script. In fact we used it to restart the service (/etc/init.d/pbxsrv restart). But what does the existence of the init script has to do with this issue? Sorry if I'm missing something obvious here.

Thank you! It works just fine.

No problem with a full file system (we've plenty of space available). Note that the only thing we did to solve the issue was to restart the service and it keeps working until now. What about the log lines I've pasted? Do they reveal something? Would the full log help you and if yes can I share them privately? Do you want me to open a ticket for this? _______________________ System Status Overview Please use the information shown on this web page when you request help from the support team. Software-Version: 5.2.4 (CentOS32) Build Date: Aug 22 2014 06:11:46 License Status: Vodia PBX Hosted 5AY-T9L-MWT-13A License Duration: Active subscription

Today the service went down. ps output was showing the process still running and netstat -anp was showing it bind to the network interface. However we could place no call and we could not open the web interface. The logs had hundrends of messages like these: [5] 20150920121742: Did not receive ACK, disconnecting call 2684293046@192.168.1.23 [5] 20150920121742: Did not receive ACK, disconnecting call 2e3d18e0-15eb03@127.0.0.1 [4] 20150920121742: 11 registration messages pending [4] 20150920121748: Last message repeated 13 times A simple /etc/init.d/pbx restart was enough to restore the service. We're happy it did but we feel kind of scared. This was version 5.2.4 on CentOS 32bit. We need your help to find the root cause.

I can't upgrade to 5.3.0 because I get this error: [3] 20150919113523: Software update: Sending request for file http://vodia.com/downloads/pbx/centos32/pbxctrl-centos32-5.3.0 [7] 20150919113523: http:vodia.com:80: Return code 404 A few more relevant lines from the logs: [1] 20150919113505: Performing software upgrade based on http://vodia.com/downloads/pbx/version-5.3.0.xml [7] 20150919113505: http:vodia.com:80: DNS A returned 68.178.130.101 [7] 20150919113505: http:vodia.com:80: Connect to 68.178.130.101 [7] 20150919113506: http:vodia.com:80: Return code 200 [3] 20150919113506: Software update: Removing file pbxctrl-old [3] 20150919113506: Software update: Sending request for file http://vodia.com/downloads/pbx/pbxctrl-5.3.0.dat [7] 20150919113523: http:vodia.com:80: Return code 200 [7] 20150919113523: Writing file pbxctrl.dat with hash f7b89c1670367e0bbd45b0b56e6f4d7a [3] 20150919113523: Software update: Sending request for file http://vodia.com/downloads/pbx/centos32/pbxctrl-centos32-5.3.0 [7] 20150919113523: http:vodia.com:80: Return code 404

We've tried with Firefox, Safari, Chrome and maybe Internet Explorer also

Do I understand correctly that if we set things up as you propose the user will have to remember to start recording every time? (If it is so then this is not desirable because users will some times forget it)

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

This might help: When connecting with https there is apparently an SSL error: ssl_error_bad_mac_read If we connect with http instead of https everything works as it should. Note also that when we connect via https we have not installed any certificate we just tell our browsers to continue to the PBX web UI no matter the certificate issues.

When a domain is configured to record all calls but a caller external to the PBX calls a callee in that domain and requests not to record his call what can the callee do? Star codes to start / stop recording don't seem to work in this case. (note that by default there is a prerecorded message that informs the caller that his call is being recorded and he can ask for recording to be canceled if he so wishes) (version 5.2.4 (CentOS32)

I'm opening a domain, then I click through these links: Agent Groups -> the first agent group -> Caller Setup. At this point I'm at the page titled "Caller handling for ACD nnn (Users)" and I also get this log entry: [6] Dictionary: Item dom_acd6.htm percent not found Then under "Upload Messages" I'm clicking to play one of the wav files but instead of hearing the audio the player dissapears and I get these log entries: [5] Alert(2, 20) [8] Received closure alert [9] [f0f79be4] send_alert(0100) Any ideas of what went wrong? _____ P.S. Software-Version: 5.2.4 (CentOS32) Build Date: Aug 22 2014 06:11:46 ____________ P.P.S. I've not customized the dom_acd6.htm page. If I go to customization of this page here are the lines with the word percent in them: <td> <select id="muting" name="muting" class="cCombo"> <option value="" selected="{ssi sel muting }">{lng $default}</option> <!-- 12.5 % --> <option value="0" selected="{ssi sel muting 0}">{lng $dom_acd.htm#full_mute}</option> <option value="10" selected="{ssi sel muting 10}">{lng $dom_acd.htm#mute_to} 10 {lng percent}</option> <option value="20" selected="{ssi sel muting 20}">{lng $dom_acd.htm#mute_to} 20 {lng percent}</option> <option value="50" selected="{ssi sel muting 50}">{lng $dom_acd.htm#mute_to} 50 {lng percent}</option> <option value="100" selected="{ssi sel muting 100}">{lng $dom_acd.htm#no_mute}</option> </td>

I've verified that the following are set to Greek: 1) System Settings -> Default IVR Language, Default Tone Language 2) domain's general settings -> Default IVR language, Tone language 3) extension settings -> IVR language Am I missing something?

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.

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

Thanks for the tip regarding missing Greek prompts (it's a minor issue but it still is one). Regarding our major issue you write that: but our problem is that since upgrading to ver. 5 no matter what we do to control the language (using the settings mentioned in the OP) many extensions answer calls with English prompts.

[note: this post is a descentant of post 8019-...-audio-and-web-language-to-greek That original post is being split in two separate loosely related bug-reports in order to better follow the different resolution of issues] I want to have Greek web UI but I can't make it work in version 5 (was working fine for version 3 and 4). I've tried switching the following settings to Greek: 1) System Settings -> Default Web Language 2) domain's general settings -> Default web language I restarted the service after changing the settings The only thing that changed was that Greek is now pre-selected when I login. However the UI is still English. This is like really important to us because all our customers are Greeks and some of them don't speak english. However returning to version 4 is not an option. So do I need to try something else? Can I provide more info?

[note: this post is a descentant of post 8019-...-audio-and-web-language-to-greek That original post is being split in two separate loosely related bug-reports in order to better follow the different resolution of issues] I want to have Greek audio prompts but I can't make it work in version 5 (was working fine for version 3 and 4). In fact for some extensions it does work and for others it doesn't but I can't tell what's the difference In all cases where I wasn't getting Greek audio prompts I've tried switching the following settings to Greek: 1) System Settings -> Default IVR Language, Default Tone Language 2) domain's general settings -> Default IVR language, Tone language 3) extension settings -> IVR language I've also tried upgrading the Greek language files from http://vodia.com/doc...ng_installation I restarted the service after changing the settings and after upgrading. Do you believe I'm missing some setting? If yes what setting? What other steps should I follow to help you diagnose the problem?

Update: we found out that some extensions do hear Greek audio prompts but it seems it has nothing to do with the settings -- at least not the settings that I know about: 1) System Settings -> Default IVR Language, Default Tone Language 2) domain's general settings -> Default IVR language, Tone language 3) extension settings -> IVR language Am I missing something? (e.g. is there is any other setting I forgot about?) BTW Should I split this post in two bug reports (Greek audio prompts -- Greek web language)?

I must note that we had Greek webUI in version 4 also so the "delta" maybe shorter. Also you seem to be touching only the webUI part of the Greek localization. Can you also look at the audio prompts part?

about the status. We're willing to help by all means. What should we do to get the ball rolling?

Do I need to try something else? Can I provide more info? This is like really important to us because all our customers are Greeks and some of them don't speak english. However returning to version 4 is not an option.

I want to have Greek web UI and audio prompts but I can't make it work in version 5 (was working fine for version 3 and 4). I've tried switching the following settings to Greek: 1) System Settings -> Default IVR Language, Default Tone Language, Default Web Language 2) domain's general settings -> Default IVR language, Tone language, Default web language 3) extension settings -> IVR language I've also tried upgrading the Greek language files from http://vodia.com/doc...ng_installation I restarted the service after changing the settings and after upgrading. The only thing that changed was that Greek is now pre-selected when I login. However the UI and the IVR prompts are English.

Thanks for the help. It's indeed better/cleaner than ver. 4. For anybody googling their way to this thread: On the trunk settings you set "Yes" under "Inter-Office Trunk --> Trunk may terminate calls for remote systems" and then set the dial plan to "Dial plan for outbound calls"

In version 4 we have a trunk for incoming calls with the setting "Assume that call comes from extension" 200 That way it redirects all incoming calls to the dial plan of that user. In version 5 we can't find this setting anywhere. After reading the manual I thought maybe I had to try the setting "Use a list of expressions" and I tried with this expression: ![0-9][0-9]*$!\+\1!t!200 but I get not founds and the logs show this: [5] 20141024181559: Port 26: Incoming call in domain XXXX on port 26 trunk YYYY (102) [8] 20141024181559: Port 26: Changing the user to 200 because of trunk setting [8] 20141024181559: Trying to match number 1234567890 with ERE .*$ [8] 20141024181559: Send call to extension ERE returned +1234567890 [8] 20141024181559: User +1234567890 not found in domain XXXXX

Since v.5.2.3a the email that is sent to the participants of a scheduled conference is malformed and is not recognized as a calendar event by any mail client I've tried (mac mail, gmail, thunderbird). If I save the attachment adding an ics extension it opens fine and I see all the details of the calendar event just fine. Here is the source of such an email: Subject: Invitation to telephone conference "test 4/9" From: <pbx@company.com> To: <user@company.com> Date: Thu, 04 Sep 2014 06:25:06 -0000 MIME-Version: 1.0 BEGIN:VCALENDAR VERSION:2.0 METHOD:REQUEST PRODID:-//PBX/5.2.3a//EN BEGIN:VEVENT ORGANIZER:MAILTO:user@company.com ATTENDEE;ROLE=REQ-PARTICIPANT;RSVP=FALSE:MAILTO:user@anothercompany.eu ATTENDEE;ROLE=CHAIR;RSVP=FALSE:MAILTO:user@company.com DTSTART:20140905T070000Z DTEND:20140905T080000Z DTSTAMP:20140904T062505Z SUMMARY:Telephone conference "test 4/9" DESCRIPTION:The access code is 0967. The conference room name is "company's Main Conference Room". LOCATION:Conference Server 442223339918. UID:95EE426EB23DED48FAA9BB0912C3E2F2 STATUS:CONFIRMED SEQUENCE:1 TRANSP:OPAQUE CLASS:PUBLIC PRIORITY:5 END:VEVENT BEGIN:VALARM TRIGGER:-PT15M ACTION:DISPLAY DESCRIPTION:Reminder END:VALARM END:VCALENDAR