Jump to content

rhill

Members
  • Posts

    13
  • Joined

  • Last visited

Everything posted by rhill

  1. I added the 1 for "Country code (e.g. "1" or "32"):" field. Is that the entry that is needed to complete black listing? Do I need to enter anything for area code? I added my personal number and attempted to call back however nothing was blocked and the call went through normally.
  2. Using PBXnSIP Version: 3.2.0.3143 (Linux) Cannot seem to get black listing to work. Sometimes it will cicumvent the callerID with the name we assigned it. But blacklisted numbers are still getting through. I've tried inbound using Hunt Group and Auto Attendant neither block numbers on the blacklisting. I've made sure all extensions are set to reject blacklisted numbers. How does this feature work? It should not be this difficult it's even a star code! I've read the manual, searched and tore through it page by page. I just can't seem to make blacklistings work! Please let me know your black listing secrets!!! Thanks!
  3. I'm working with one of my clients who wishes to do a parallel ring to 4 cell phones. Hunt groups only call out to extensions, i did attempt to convince him to have the cell phones rung immediately when the service flag turns on. He did not like that. SOOOOOOO I've tried setting up a service flag and enabling it so that they all hit each redirect on a separate extension (4) but they don't all ring at the same time. no dice sooooo where should i turn now? I read on another PDF that parallel cell phone calling is available, is that in conjunction with the extension? I'm wanting to do multiple cell phones at the same time. How can I make this happen? thanks in advance
  4. 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
  5. in call recording has to be activated during the call by pressing (default *12/*13) you also have to have the email address set in place on the extension making the recording look at page 304 on PBXnSIP admin guide V4. Issue 3, July 2010 Some versions vary but it works on our version 3.3 here. It turns out it is a licensing thing if you do not see the in call recording star codes in Domains>settings>feature codes
  6. 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?
  7. 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.
  8. I've got a question I couldn't find a topic home for. Basically we have a customer that is going to have several Yeahlink phones. On these phones they want the ability to see a call put on hold. This would be indicated by a light of some sorts. Then able to be answered. by presssing a button or two How can we make this a reality using these phones? There's tons of BLF settings i just don't know where to start. Thanks
  9. Version: 3.1.0.3031 (Linux) Ive been having headaches with agent groups as well. Calls getting stuck in queue, not being answered by agents. When ringing if the agent doesnt pick it up, it gets stuck. Doing any redirect behavior like if ringing 25 sec redirect back into agent group only gets calls mixed up and sticky. the only savior we've had is *87 but still its an annoyance many times over
  10. He also replied that he is able to continue to get calls if he *64 (agent login) every 5 minutes. How can I avoid having him do this behavior every 5 minutes?
  11. our client still reports this "idle" status. he is logged in and all indicators show that he is and has been: Agent Name Availability Calls Duration (Hold) 7000 Karla Rowland 0 7003 Randy Martin 07:06-07:23 07:23- 21 0:18:12 0:00:06 the 7000 and 7003 are call takers. we setup a vm to catch calls that get stuck ringing for 25 seconds that dumps to 7103 2012/12/11 07:12:00 5128100858 5125877729 - 2101 7003 00:09 00:03 00:48 2012/12/11 07:23:19 ON-NET (5125877729@dblhorn-platformsvcs.net) 15125877729 - 2101 7003 00:05 00:01 00:05 2012/12/11 07:25:49 5122914000 5125877729 - 7103 7003 00:05 00:25 00:10 2012/12/11 07:26:38 ON-NET (5125877729@dblhorn-platformsvcs.net) 15125877729 - 2101 7003 00:05 00:01 00:04 2012/12/11 07:34:52 5125207840 5125877729 - 2101 7003 00:05 00:02 00:45 2012/12/11 07:40:16 ON-NET (5125877729@dblhorn-platformsvcs.net) 15125877729 - 7103 7003 00:05 00:25 00:01 2012/12/11 07:40:44 ON-NET (5125877729@dblhorn-platformsvcs.net) 15125877729 - 2101 7003 00:05 00:01 00:05 2012/12/11 07:42:59 5125172785 5125877729 - 2101 7003 00:05 00:02 00:47 2012/12/11 07:43:56 7024281245 5125877729 - 2101 7003 00:25 00:02 01:00 2012/12/11 07:47:13 5127078072 5125877729 - 2101 7003 00:09 00:02 00:25 2012/12/11 07:49:00 5127882762 5125877729 - 2101 7003 00:05 00:02 00:43 2012/12/11 07:51:09 8186690438 5125877729 - 2101 7003 00:05 00:07 00:23 2012/12/11 07:55:45 5129146357 5125877729 - 2101 7003 00:05 00:02 01:49 2012/12/11 08:12:34 3036388437 5125877729 - 7103 7003 00:09 00:25 00:11 2012/12/11 08:14:47 5129310207 5125877729 - 2101 7003 00:05 00:03 00:43 2012/12/11 08:26:15 3036388437 5125877729 - 2101 7003 00:06 00:01 01:41 2012/12/11 08:28:14 3036388437 5125877729 - 2101 7003 00:05 00:01 01:29 2012/12/11 08:36:40 8302001033 5125877729 - 2101 7003 00:15 00:10 01:24 2012/12/11 08:38:33 5122296711 5125877729 - 2101 7003 00:05 00:09 01:08 2012/12/11 08:40:28 5122296711 5125877729 - 2101 7003 00:05 00:02 01:36 2012/12/11 08:45:13 5124467677 5125877729 - 2101 7003 00:05 00:03 00:50 00:04 2012/12/11 08:46:08 5125385527 5125877729 - 2101 7003 00:27 00:02 00:57 2012/12/11 08:46:37 5129470966 5125877729 - 2101 7003 00:35 00:02 00:27 2012/12/11 08:47:38 5124467677 5125877729 - 2101 7003 00:38 00:01 01:03 00:02 During these 3 times (there are more from yesterday) it rings his extension for 25 seconds according to the call log. The agent says the call never rings. What should we do with this unexpected behavior?
  12. My main concern would be the actual behavior. The call in the Agent Group seems to get stuck if the call is not immediately answered. It rolls back to a waiting status and holds there until the caller hangs up. There is seemingly no way for the agent to answer the call stuck.
  13. I setup a plain agent group on PBXnSIP Version: 3.1.0.3031 (Linux) we have Additional license information: Extensions: 440/5000 Accounts: 607/9999 on the server. This new agent group has strange behavior. If a call comes in and rings until X time (this is a basic default setting agent group) the call will sit in either ringing or waiting. The call never gets answered. The caller eventually has to hang up and sometimes this process gets repeated thusly looking like a lot of dropped calls. I have set a if ringing 25 seconds fwd to voicemail setting but I would like to see it stay available for answer. I attempted to send it back into the same agent group by setting the same if ringing 20 seconds fwd to agent group but those calls do not get answered either. What is causing this behavior. There are only 2 agents taking calls or sometimes just 1. So they need to have calls that are queued go to them directly. They use Polycom 550/501 phones.
×
×
  • Create New...