olecoot
-
Posts
150 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by olecoot
-
-
It would be nice to add the option to store locally or e-mail to the extension e-mail account for the other constant recording options. Some extension users don’t have admin privileges to a remote server and they need the recordings real-time. Similar to pressing *12 and receiving the recording via e-mail, but using the constant record options and still have the recordings e-mailed when the call completes.
Recording:
Record incoming calls from hunt group:
Record incoming calls from agent group:
Record incoming calls from extension:
Record outgoing calls to internal numbers:
Record outgoing calls to external numbers:
-
Hmm. Does that mean you also have a problem with attended transfer when there are two different registrations? Hard to believe. Maybe there is a flag that controls this behavior on the phone?
No. Attended transfers happen all day long. Never heard a complaint from anyone in the office or any of our customers.
-
Whow. I believe that is not very intuitive. Also for attended transfers. What phone type is it?
Okay, that sounds like a short-term workaround.
They're Polycom's. So far, we've tried it on 601s, 650s, and 550s and they all exhibit the same behavior.
The phones are on version 4.1 BootROM and 2.2.2 sip.ld
-
Maybe you can capture two SIP packets: The INVITE that hits the phone, and the INVITE from the phone that contains the star code. I think if we see those packets we can say if that is the problem or not.
What we have found:
On a phone with multiple registered extensions, placing the call on hold before using *85 to park call will always result in a failed parked call on our phones. Placing the call on hold with a phone that has more than one registered extension just "rolls" over to the second extension and tries to initiate the park on that second extension.
However, we have found that if instead of placing the call on hold we can use transfer and use *85 or *85+extension and the parking feature works.
Thank you
-
Maybe the issue is this:
Our office has a hunt group, in which all of our phones ring when a call comes in (sorry for leaving that out). Someone takes the call and tries to park the call on the extension of a coworker. If the phone that takes the call has 1 registered extensions, the park feature works fine. If the phone that takes the call has more than 1 registered extension, the park feature fails.
The phones are Polycom phones. Do you think it is an issue that is phone related?
-
There is a reoccurring error message in one of our servers stating:
SMTP: Cannot resolve smtp.domain-messaging
I have checked all of the .xml files that I can find trying to pinpoint where the typo may be. Can you give me a few hints on where to look for this entry? Obviously the .com has been left off. I've restarted the service thinking that it might have been cached but this did not work.
This is on version 2.1.6.2450 (Win32).
Thanks in advance.
-
Well, global names of course have a special meaning in restoring domains. If there is already another tel:alias with the same name, we are in trouble.
But it seems that all alias names are not restored. Looking into this right now.
Just getting around to update this:
I upgraded our platform to release version 2.1.11.2484 and the issue has been fixed!
Thank you!!
-
Hmm. Can you verify that the call park code was sent from the same account where the call was received? E.g. when the call went to 300 and then later you call from 500 to park the call it is understandable that the PBX says "what call are you talking about?"...
I may have not been clear in my original post. I apologize.
A call comes into my phone with 2 extensions 1 and 2. I answer the call on extension 1. The call is for another person on extension 400. I try to park the call from extension 1 to extension 400 by placing the call on hold then dialing *85400 at which time I hear the "failure" message. The call remains on hold on extension 1 and I can pick it up and continue the call. I just can't park it.
If I attempt the same scenario on a phone with 1 extension only and park a call using hold then *85400, the process works.
-
Ouch, seems there is for a strange reason a problem with the case. The link that is being generated is upper-case, while the matching expects lower case. Maybe just move the pnp.xml file away and restart the service (unfortunately that file is cached in the PBX). "In theory" the master file and the pnp.xml case should match and there should be no problem.
The /provisioning is hardcodec inside the PBX and just tell it to run the filename through the pnp.xml file for a match. This is to keep other web access efficient, no need to run through a list of ERE!
Ok, I moved the pnp.xml file out of the html directory and I'm getting a little further now. We now have the same 0004F2142B96/ directory in the generated/ dir and within that directory is now polycom_master.xml and polycom_phone.xml. Phone now gets to "Config file error error 0x0" on the phone screen. Should we have a sip.cfg file generated also?
Any ideas? Thanks
-
So that file is not in the generated directory? Did you manually edit the pnp.xml file?
There is a MAC labeled directory in the generated directory (/usr/local/pbxnsip/generated/0004F2142B96). Within the 0004F2142B96 directory resides the polycom_master.xml which has the path http://10.12.91.25:80/provisioning/polycom...004F2142B96.cfg, etc. I have not edited the pnp.xml file. What do I need to look for as far as editing? And where is the /provisioning coming from?
Here is the polycom portion of the pnp.xml file:
<file name="polycom_master.xml" encoding="xml">
<pattern>!^(0004f2[0-9a-f]{6})\.cfg!\1!</pattern>
<vendor>Polycom, Inc.</vendor>
</file>
<file name="polycom_phone.xml" encoding="xml">
<pattern>!polycom_phone_([0-9a-f]{12})\.cfg!\1!</pattern>
<vendor>Polycom, Inc.</vendor>
<parameter name="transport">DNSnaptr</parameter>
<parameter name="layer">UDP</parameter>
</file>
<file name="polycom_sip.xml" encoding="xml">
<pattern>!polycom_sip_([0-9a-f]{12})\.cfg!\1!</pattern>
<vendor>Polycom, Inc.</vendor>
<parameter name="transport">DNSnaptr</parameter>
<parameter name="layer">UDP</parameter>
</file>
<file name="polycom_adrbook.xml" encoding="xml">
<pattern>!(0004f2[0-9a-f]{6})-directory\.xml!\1!</pattern>
<vendor>Polycom, Inc.</vendor>
</file>
-
I would try looking at your configuration file/files for the phone itself. We had a similar issue with our Polycom phones and we were able to turn the beep on or off on a per phone basis by changing the value on the variable.
Hope this helps
-
We are using PBXnSIP version 2.1.11.2484 (Linux) and have an issue with call parking but only with phones having more than one registered extension.
For example, phone 1 has 2 registered extensions, 300 and 500. Call comes in and is picked up on 300. Try to park call on extension 400 and I hear "Call parking has failed". The call still remains on hold and can be resumed from the phone that answered the call. It can be transferred to another extension but not parked.
If I try the same scenario from a single extension phone, call parking works fine and as expected.
-
I'm trying to accomplish the same thing with some polycoms. When I check the generated/MACaddress directory I find polycom_master.xml file. The contents of the file state to find the phone configurations in a directory CONFIG_FILES="http://1x.x.1.xxx:80/provisioning/polycom_phone_0004F2142B96.cfg, etc. I do not specify the provisioning directory in my html files so where does it come from?
Also if I create a provisioning directory. PBXnSIP will not use it to create files for the phone.
Hmm. Did you check the "generated" directory for files? You should see a directory with the name 0004f2060b0a, check out what files are in there.Maybe you need to iron the configuration of the phone again. I remember I had to do this a couple of times before things worked fine.
-
Has anyone experienced this error message:
kernel: usb 1-4: usbfs: process 32630 (pbxctrl) did not claim interface 0 before use
PBXnIP 2.1.10.2474
kernel ver 2.6.18-53.1.14.el5
Red Hat
The usb port is working in the fact that the license associated with the dongle is recognized by PBXnSIP.
cat /proc/bus/usb/devices
T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 4
B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 2.06
S: Manufacturer=Linux 2.6.18-53.1.14.el5 ohci_hcd
S: Product=OHCI Host Controller
S: SerialNumber=0000:00:0f.2
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms
T: Bus=01 Lev=01 Prnt=01 Port=03 Cnt=01 Dev#= 4 Spd=1.5 MxCh= 0
D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=0e50 ProdID=0002 Rev= 1.01
S: Manufacturer=TDi GmbH - Germany
S: Product=USB-Chip
C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr= 8mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=00 Prot=00 Driver=(none)
E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=255ms
-
When attempting to move a domain with tel:alias configured from a server running version 2.1.6.2450 (Win32) to a server running version 2.1.10.2474 (Linux) the tel:alias did not move with the domain. The same issue occurs attempting the move from server to server of the same version 2.1.10.2474 (Linux). Any ideas?
Thanks in advance!
-
This may or may not be related to just the Linux version of PBXnSIP. I am in the process of trying to migrate customers from one server to another. The server that I am removing customers from is version 2.1.6.2450 (Win32). The server that I am moving customers to is version 2.1.10.2474 (Linux).
The issue is this:
Create the tar file on the production 2.1.6(Windows) server
Number of users in the domain = 5
Create the domain on the production 2.1.10(Linux) server using the tar file created on 2.1.6
Number of users in the domain = 3
Use the same tar file (from 2.1.6 Windows) to create a domain on a pre-production server running the same version as the Linux production server (2.1.10 Linux)
Number of users in the domain = 5
I have done this repeatedly with the same result. Can anyone suggest what might be the issue? The Linux servers are basically the same. Directory file permissions are the same, directory structure is the same, individual file permissions and ownership is the same.
This is a critical issue for us in the fact that I need to migrate these customers off of the existing server and onto the new server.
-
I feel really stupid about asking this ....
We have ver 2.1.6.2450 (Win32) installed and I am searching for the Domain Backup Utility. Has it been moved/removed from this version?
OK..... I am Stupid. I found it
-
I feel really stupid about asking this ....
We have ver 2.1.6.2450 (Win32) installed and I am searching for the Domain Backup Utility. Has it been moved/removed from this version?
-
So if there are leftovers from previous versions, how can I be sure, as administrator of the server, to have a "good" upgrade? Usually I will install over a previous version so as not to lose any of our users settings, etc.
Thank you in advance!
-
I'm seeing this in several of our servers and I'm not quite sure why the address change. Version 2.1.6.2450 (Win32).
[3] 2008/04/18 12:02:52: Source address for sip:1206@domain.com has changed to udp:xx.xxx.xx.xxx:23943
[3] 2008/04/18 12:04:01: Source address for sip:1207@domain.com has changed to udp:xx.xxx.xx.xxx:23953
[3] 2008/04/18 12:04:22: Source address for sip:1206@domain.com has changed to udp:xx.xxx.xx.xxx:23955
[3] 2008/04/18 12:05:31: Source address for sip:1207@domain.com has changed to udp:xx.xxx.xx.xxx:23963
[3] 2008/04/18 12:05:48: Source address for sip:1206@domain.com has changed to udp:xx.xxx.xx.xxx:23965
-
We use our own logo for PBXnSIP. Let's say I wanted to right justify or center the logo, is there a way to change the position of the logo?
-
No this is still in limbo. Unfortunately, but it is still on the list.
Is there an ETA?
I have licensed dongles and have given up on the Windows platform for various reasons?
-
How is the USB dongle support for Linux going? Is there any update?
Has there been any progress on the Linux/dongle effort?
-
2.1.6 already has a setting called "cdr_email_size" (invisible global setting in pbx.xml) - see http://wiki.pbxnsip.com/index.php/Global_Configuration_File. Check out http://www.pbxnsip.com/protect/pbxctrl-2.1.6.2441.exe if you like.
Have you seen any detrimental effects of increasing this limit? How was the value of '1000' determined?
Thanks in advance.
pid file
in Linux-related Topics
Posted
I have several installations of PBXnSIP running on a RH derived flavor of Linux. I use the startup script that is listed in the documentation of the WIKI for all of them.
http://wiki.pbxnsip.com/index.php/Installing_in_Linux
The init script mentions the pid file as "pidfile: /var/run/pbxctrl.pid" however, the pid is not created (or I have failed to find it). Is this file supposed to be created at statup of the pbxnsip service? I would like to use it for monitoring purposes. As always, thanks in advance.