olecoot
-
Posts
150 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by olecoot
-
-
voicemail/ recordings and all? thats awesome.
How do you import it?
When you go to the new server, go to create domains, give it the primary name and then create from file. PBXnSIP will look on the local machine for the file which by default is named domain.tar. That is if you are using the browser on the server it looks on the server. If you are using a desktop/laptop to browse to the web interface it looks on the desktop/laptop.
I generally use a laptop and keep the file there. If you have the opportunity, test first.
hope this helps!
-
Yes that looks correct. There should be no difference between Linux and Windows; the differnce is probably just when you saved something the last time. After using the link above, the file should contain the setting that you want.
We are piling more and more "hidden" settings up. Usually we don't want that customers play with these setting (because it makes support more difficult); however it is always good to be able to make a change when neccessary without changing the code. That settings above would be a candidate for becoming visible...
That would be very good news indeed! And much appreciated
Thank you
-
Check this out: http://wiki.pbxnsip.com/index.php/Global_Configuration_File
So using your example the command would be:
http://pbx/reg_status.htm?save=save&send_recording=true
Is this correct?
The question remains why is the variable provided in the Linux pbx.xml and not the Windows pbx.xml of the same version? And how does it become "visable" or will the above command make it appear in the file?
Thanks!
-
I've upgraded a few of our Windows servers to version 3.0.1.3023 recently (using the upgrade .exe file) and the pbx.xml file does not have the global setting called "send_recording". I have Linux servers with the same version of PBXnSIP (upgraded the same way) and the setting is there.
The Windows servers host several customers that require the recordings emailed to them. The recordings are not being emailed and stopped the day of the upgrade. I fear that the issue lies with the missing setting. The license on these servers have recording enabled. Can you please tell me how to have the setting appear? I have tried making changes in through the web interface, which has worked in the past, but it is not working for this.
I cannot use beta versions on these servers.
Thanks
Is there a fix for this???
-
Is it possible to extract a domain and move it to another box? some sort of export tool?
Yes there is and I have used it many times. Click on the domain you would like to move, then edit. At the bottom of the page is a link that says "To save the domain, click here" . That will create a tar file that can be used to create the domain from file on the new server.
-
Can you tell me please if the issue with Agent Queue Statistics has been corrected in this release? This is the issue where there are no statistics are collected if the domain is in a different time zone that the server. This was broken when 3.x was introduced.
-
I've upgraded a few of our Windows servers to version 3.0.1.3023 recently (using the upgrade .exe file) and the pbx.xml file does not have the global setting called "send_recording". I have Linux servers with the same version of PBXnSIP (upgraded the same way) and the setting is there.
The Windows servers host several customers that require the recordings emailed to them. The recordings are not being emailed and stopped the day of the upgrade. I fear that the issue lies with the missing setting. The license on these servers have recording enabled. Can you please tell me how to have the setting appear? I have tried making changes in through the web interface, which has worked in the past, but it is not working for this.
I cannot use beta versions on these servers.
Thanks
-
I think this is because the system time zone is not the domain time zone. When the system performs the mightnight events, it sets the timestamps for the agents in system time. Then when the statistics are being sent, the domain time zone is used. That explains the differences.
Workaround: Choose a system time that is the same as the domain time zone.
Is there a fix for this in the next release, please? It did not seem to be broken in the 2.x release.
-
There was one difference in the settings above and that would be the time zone. Both servers are in the central time zone. The domain that is issuing the report with the statistics is set for the same time zone as the server, i.e central TZ. The domain that is sending no statistics is set to eastern TZ.
As a test I set the domain that was sending stats in the report to eastern time zone while the server is set to central time zone and as a result the report came in with the statistics at zero. This does seem to have an affect on the stats. ????
-
Please wait one day/night. It could be that the last report is more than one day ago, and that would explain the strange availability times.
Was the starting time for Shel 16:38?
From this morning:
This email contains the summary of the operation of queue Air ACD on 2008/10/10.
Overview:
Number of calls: 0
Calls where user hung up while ringing: 0
Calls where user hung up while waiting: 0
Calls that have been redirected while ringing: 0
Calls that have been redirected while waiting: 0
Calls where callers navigated to other destinations: 0
Total duration spent in IVR:
Total duration ringing:
Total duration talking:
Total duration holding calls:
Activity report of agents:
Agent Name Availability Calls Duration (Hold)
103 Anna 0
128 Sheila 1193033:13-1193038:32 0
132 Luis 0
135 Marina 1193031:33-1193035:45 1193036:26-1193039:33 0
138 Jeannie 0
151 Melissa 00:00-24:00 0
List of calls to the queue:
From To Time Account IVR Ringing Talking (Hold)
Compared to my test server:
This email contains the summary of the operation of queue MGR PICK UP on 2008/10/09.
Overview:
Number of calls: 2
Calls where user hung up while ringing: 0
Calls where user hung up while waiting: 0
Calls that have been redirected while ringing: 0
Calls that have been redirected while waiting: 0
Calls where callers navigated to other destinations: 0
Total duration spent in IVR:
Total duration ringing: 0:00:24
Total duration talking: 0:01:16
Total duration holding calls:
Activity report of agents:
Agent Name Availability Calls Duration (Hold)
300 Joe Blow 00:00-24:00 1 0:00:35
450 Test-430 00:00-24:00 0
501 Test 501 00:00-24:00 1 0:00:41
List of calls to the queue:
From To Time Account IVR Ringing Talking (Hold)
300 4444 13:12:36 501 0:00:15 0:00:41
500 4444 13:13:26 300 0:00:09 0:00:35
From everything that I can see they are set up the same.
-
OK. That corrected the problem. Now when is this going to become GA?
When I tested the release, it worked fine on our test system (RHEL5). Or customer (Windows server) ver 3.0.1.3023 however, still have an issue with no stats in the email. Any ideas? One suggestion was a time zone difference. Customer is set to Eastern and server is in Central timezone.
Contents of email Report:
Activity report of agents:
Agent Name Availability Calls Duration (Hold)
103 Ann 0
128 Shel xxxxx 1193032:38-1193038:40 1193038:48-1193039:26 0
132 Luisxxxxxxxx 0
135 Marixxxxxxxa 1193031:51-1193039:45 0
138 Jxxxxxxxxxx 0
151 Mexxxxxxxx 00:00-24:00 0
-
Try http://pbxnsip.com/protect/pbxctrl-rhes4-3.1.0.3031. Is has a global setting called "send_recording", if you set it to "true" it will treat recordings like voicemail. Maybe a workaround until we found a better solution.
That seems to work.
Thanks
-
What OS do you run? We can provide a test image.
RedHat EL5
Thank you!
-
That was supposed to be a feature... The recordings are now available from the web interface and are shown as such.
The motivation behind this was that you might want to receive voicemails as emails, but not recordings. Maybe we need another flag that tells the user what to do with the recordings, just like with new voice mails.
PLEASE.... Add the flag! In the meantime, is there a way for us lay folk to activate the feature again?
Thank you.
-
No, that did not make it into this release. In the meantime, can you double check that the license allows recording?
Yes, our license allows recording. Can you tell me if you can get a patch out? I have a very irritated customer right now. They had that feature in the previous version (2.x) and now they don't have it any longer.
-
So did you follow the guidelines in http://wiki.pbxnsip.com/index.php/Installi...#Manual_Upgrade?
I see that 3.0.1.3023 has been released on the website. Can you please tell me if the recording/star code/email issue has been resolved in this release?
-
Can you please verify the "recordings" folder under the pbx install directory? If the file is generated there, then there must be some issues in sending emails.
I think there is an issue with the email of recordings in 3.x. as I am having a similar problem since upgrading to 3.x. The recordings are created but not sent via email.
See the posting here:
http://forum.pbxnsip.com/index.php?showtopic=1344
This customer of ours relies heavily on these recordings.
-
I have an issue to report.
We have customers that use a star code to record calls and then receive those recordings via email as attachments. Those seem to be broken. Unless the settings have changed. When using the star code, the recording seems to be made but are not sent via email.
Can you confirm this please? Version 3.0.1.3023 Linux.
Thanks in advance
-
You can grab the latest and greatest here - http://pbxnsip.com/download/pbxctrl-3.0.1.3023.exe
Is there a RedHat version available? We've been testing 3.0.1.3018 Linux.
Thanks.
-
Sirs:
I have a customer that is giving me fits about VM to EM messages getting caught up in his spam filter. This server is version 3.0.0.2998 Linux and since upgrading to this version, I have had this problem. The customer is too pig headed to white list my relay server and demands that I change the email format.
Is there a way for me to change the format of the date in the email header so that the spam filter will allow the messages to go through? I'll include some of the threads that have been exchanged.
Pig headed customer:
We did some additional research into the issue of the voice messages ending up blocked by the spam filter. The spam filter folks also looked at the header information in your messages. And in fact the date field is simply not formatted correctly. Here is the comment from the filter company:
Reply from filter company:
Yes, it appears that the voice mail provider is adding an invalid date
header. This is adding a total of 5.6 points -- 1.7 for the incorrect
format, plus 3.9 points because the incorrect format can't be parsed to
arrive at a correct date, causing it to appear as if the Date: header
postdates the receipt of the message.
The date header they add is:
Date: Mon, 2008 Sep 29 19:41:03 -0000
which is not in the correct format for use in an email header. The
correct format would be:
Date: Mon, 29 Sep 2008 19:41:03 -0000
You will need to contact your voicemail provider to have them fix the
header.
Test Message sent to myself:
Microsoft Mail Internet Headers Version 2.0
Received: from mailserver.domain.net ([125.125.125.74]) by domain2.com with Microsoft SMTPSVC(6.0.3790.3959);
Tue, 30 Sep 2008 11:04:23 -0500
Received: from localhost (pbx.domain3.com [66.1xx.xxx.xxx])
by mailserver.domain.net (8.13.8/8.13.8) with ESMTP id m8UG4IvC018042
for <testuser@domain2.com>; Tue, 30 Sep 2008 11:04:18 -0500
Message-Id: <200809301604.m8UG4IvC018042@mailserver.domain.net>
From: "PBX-Voicemail-Server" <messaging@mailserver.domain.net>
To: <testuser@domain2.com>
Subject: Voicemail from Test 501 (501) to Test User 1
Date: Tue, 2008 Sep 30 15:53:41 -0000 <<<<<<<----------- This is where the pig headed customer's spam filter keeps the message from delivery.
MIME-Version: 1.0
Content-Type: multipart/mixed;boundary="b-z76k2l5wjndkcnfmesnzhkomde"
Return-Path: messaging@mailserver.domain.net
X-OriginalArrivalTime: 30 Sep 2008 16:04:23.0541 (UTC) FILETIME=[34982A50:01C92316]
X-TM-AS-Product-Ver: SMEX-8.0.0.1181-5.500.1027-16188.005
X-TM-AS-Result: No--15.291400-5.000000-31
X-TM-AS-User-Approved-Sender: No
X-TM-AS-User-Blocked-Sender: No
--b-z76k2l5wjndkcnfmesnzhkomde
Content-Transfer-Encoding: base64
Content-Type: text/html;charset="utf-8"
--b-z76k2l5wjndkcnfmesnzhkomde
Content-Transfer-Encoding: base64
Content-Disposition: attachment;filename="msg273.wav"
Content-Type: audio/wav;name="msg273.wav"
--b-z76k2l5wjndkcnfmesnzhkomde--
-
One of our customers is having an issue, since upgrading to 3.x. This is on a server hosting multiple customers.
Here’s the exact scenario:
1. A call comes into the office and it needs to be transferred to an agent group that handles that type of call. For instance, we tried this earlier from 123-456-7890 (cell phone) to our main number (234-567-1234) auto attendant and dialed an extension. 119.
2. We transferred the call to x176 (our certificate agent group).
3. There are two agents that are on the agent group, extension 105 and 146. Both phones ring when the call is transferred, which should not happen. If extension 146 tries to answer the call, there is no body there and x105 continues to ring. When x105 answers the call, then the person is connected successfully.
Any ideas?
Thank you.
-
OK. That corrected the problem. Now when is this going to become GA?
-
What kind of Linux flavor do you prefer?
RedHat EL5
Thank you
-
You may have to move straight to 3.0.1.3017 (http://pbxnsip.com/protect/pbxctrl-3.0.1.3017.exe). There were a couple of problems with email servers, so I think it is better to upgrade to the above version. If you can, make a backup and give the new version a shot.
Do you have a Linux version? I have a test server that I will try it on and it is Linux.
This particular Windows server is in a production environment.
Thank you.
CentOS 5 Build issues
in Linux-related Topics
Posted
I have run into an issue with the CentOS build that is currently in the download section of the PBXnSIP website.
We are in the process of migrating all of our Windows 2003 servers to CentOS 5. Previous to the current release, I have used to pbxctrl file that was built for RedHat. After rebuilding a server with CentOS, I decided to use pbxctrl-centos5-3.0.1.3023. BTW this server has a dongle installed with the proper licensing that was issued to the box when it was running Windows Server 2003. When I attempted to install the license key, PBXnSIP would not accept it.
The entries in the log file are:
[1] 20081215105857: Starting up version 3.0.1.3023
[0] 20081215105857: License: This version does not support dongle
[1] 20081215105857: Working Directory is /usr/local/pbxnsip
I then installed the build for RedHat Linux and the license and dongle are recognized, so there is something amiss with the CentOS build.