rhill Posted March 20, 2013 Report Share Posted March 20, 2013 I have several linux servers running several different versions of PBXnSIP. Ver 3.1.0.3031 (Linux) and all domains work great for *12 in call recording. Newer version 3.3.1.3177 (Linux) *12 in call recording and the "appearance" system settings do not have that option listed. How do I get that "appearance" with in call recording back on. Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted March 20, 2013 Report Share Posted March 20, 2013 The recording via DTMF tones were changed a couple of times. E.g. when sold as snom ONE the point was that you must use snom phones to turn recording on and off (what phones are you using). Not sure what the situation was with 3.3.1. Quote Link to comment Share on other sites More sharing options...
rhill Posted March 20, 2013 Author Report Share Posted March 20, 2013 at the moment all polycom phones. it's not a DTMF tone not recognized issue. It's a there is no "Record On Key (e.g. *12): Record Off Key (e.g. *13):" on the version 3.3.1.3177 (Linux). We have a few servers different versions but example for here 3.1.0.3031 (Linux)does. in the admin overview "settings" "general" "appearance" with the record key settings. Thats is what we are looking to get to show up on the 3.3 version. Please let me know what went wrong here? Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted March 20, 2013 Report Share Posted March 20, 2013 What I was trying to say is that not the DTMF detection, but the processing has changed from version to version. So it could be, that 3.3 behaves differently with the recording than 3.1. Actually, it is probable. We don't make changes to those versions any more as they are several years old, so all we can try to do is to find workarounds. If it is Polycom phones, the only way to start recording is DTMF; there is no workaround for that. I would say the easiest solution is to go to your previous version. Quote Link to comment Share on other sites More sharing options...
rhill Posted April 10, 2013 Author Report Share Posted April 10, 2013 What I was trying to say is that not the DTMF detection, but the processing has changed from version to version. So it could be, that 3.3 behaves differently with the recording than 3.1. Actually, it is probable. We don't make changes to those versions any more as they are several years old, so all we can try to do is to find workarounds. If it is Polycom phones, the only way to start recording is DTMF; there is no workaround for that. I would say the easiest solution is to go to your previous version. I found it on page 304 of PBXnSIP admin guide v4 This is a licensing issue only available on certain licenses. I will have to call in to have my license checked to see if it was purchased or not. We have 10 servers all running different version and every server has this feature except this one Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted April 11, 2013 Report Share Posted April 11, 2013 You can always try out with a 30-day trial key (add it on top of your existing license). 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.