Jump to content

voipguy

Members
  • Posts

    293
  • Joined

  • Last visited

Everything posted by voipguy

  1. This feature request now sounds like two seperate feature requests.... The original one.. 1. Pull a call that you just missed out of voicemail back to your phone. I'm using the latest build and I've tested this feature and it's working great - THANKS. and the new one... 2. Call screening....person calls your phone and you want to screen the call so you can hear the caller talking/leaving a message then decide if you want to take the call.
  2. Hi pbxnsip, This new file didn't fix the problem. I put the file in the proper place and then restarted the PBXNSIP program. A customer just recorded a greeting and you can hear the beep tone at the very start of their out going greeting.
  3. You don't know and it doesn't matter if the user knows or not....what this feature is for is if you heard your phone ring and you weren't able to make it back in time to answer it so the call is now gone to your voicemail box....the caller might not have even started recording their message yet because the caller could still be listening to your out going voicemail box greeting...again it doesn't matter...this feature is so that we can pull the caller out of the voicemail box and bring them back to your desk phone - of course this only works if the caller is still on the line and you would know this after entering *86* - you either get the caller back or a message saying feature not available or something like that.
  4. nope.....when a mailbox owner sets up his mailbox and records his out going greeting with an ATA there is always a quick tone that is at the very start of the mailbox owners out going greeting....not the tone at the end of the greeting. Take an ATA and reg it to an extension and record your outgoing greeting...you will hear a 300 to 500ms tone at the begining of your out going greeting. Then when your friends call you and it goes to your mailbox instead of hearing "Hi you reached jeff leave a message" you hear this instead...."300 to 500ms tone Hi you reached jeff leave a message"......you can not record your out going greeting without that tone being heard in your greeting at the very begining....use a VoIP phone such as a SNOM 370 and you don't get the tone in your out going greeting...it just records "Hi you reached jeff leave a message". Thanks
  5. Yes, a star code would be great so all users can access this feature. You would barge into the call but at the same time the voicemail box would stop playing your out going greeting soon as you enter the star code at your desk to intercept/barge into the missed call. It would be easier with PAC/WAC but not all users use that or even have access to it or maybe you got auto logged out after x hours of idle time so it would be hard to login real quick to take the missed call with PAC/WAC....using the star code would be my first bet then add PAC/WAC support....my previous phone system had a great GUI and also the star code. I think if you add this to PBXNSIP it would get you some free press...it's a powerful option that a lot of phone systems just don't have...I know I miss 1 or 2 phone calls a day from not getting back to my desk quick enough before my mailbox picks up. Thanks
  6. Hi, using ver 4.1.0.4031 Linux centos 32 bit I've noticed this bug for a long time but never reported it until now - customers are now noticing it. When your using an ATA such as Linksys SPA2102 or PAP2NT for an extension instead of a VoIP phone and you record your out going mailbox greeting or name PBXNSIP always records/puts a dtmf tone at the very start of the mailbox recording...it's a very short quick tone - maybe 300 to 500ms in length - not a full second. This happens with all of my customers that are using ATA's including myself. I think PBXNSIP needs to shave off 500ms from the very beginning/start of the mailbox recording when saving the users mailbox greetings and mailbox name recordings.....don't confuse this with people calling these mailboxes and leaving recordings as those are fine...it's just the mailbox owners setting up their mailboxes. Thanks
  7. Hi, This would be a great selling feature if you add it to PBXNSIP. Pull a caller out of voicemail. How many times have you heard your office/desk phone ring and you ran to your phone and the caller already went to voicemail? It would be great to be able to pickup the phone and enter a star code to pull the caller out of the voicemail and bring him back to your phone so you can talk to him. Before switching to PBXNSIP our previous phone system (not a VoIP system) had this feature and it got a lot of press as the other phone systems never had this option. I don't think it would be that hard to implement. Thanks
  8. Hi pbx support, It's 100% a bug in ver 4 like I reported months ago.
  9. Hi reco, I don't think the tftp directory is supose to be off of the html directory....I have mine as pbxdir/tftp/snom_870_custom.xml and my custom files work.
  10. I got an answer on this from another thread. The location of the setting was moved to Accounts/General tab at the bottom. It has also been added to the end users web interface so they can turn it on/off themselves which is great. Thanks
  11. That's great....I'm glad it wasn't removed....I also see you added it to the end users web login screen so they can turn it on/off themselves. Thanks
  12. When you use PAC and click on the feature Codes button it displays all the * codes to the right but on the left there are no names list at all - it should list the name of the feature like it did before = bug.
  13. We just loaded ver 4.0.1.3499 and just got a complaint from a customer - his call waiting is now turned back on? I looked and the setting "Enable Call Waiting" was removed from the Registration tab?? Now if I want to disable his call waiting feature I have to use the "Lines:" field and put a 1 in there which disabled his call waiting but it now also prevents him from doing a 3 way call/conference call. The customer needs to make 3-way calls but wants to disable his call waiting - this worked in ver 4.0.1.3475. Can you add back the Enable/Disable Call Waiting feature? maybe also add it into the end user's web interface but make it a UserPage-Control setting as well. Thanks
  14. In version 4.0.1.3499 they removed the "Enable Call waiting feature" why? Now if a customer wants call waiting disabled we have to set the Lines: value to 1 which disabled call waiting but it also disables the customers cobference/2 way calling feature. Why remove something that was working just fine?
  15. Hi pbx support, The account login details I PM'd you a few days ago have since been deleted. I know what should happen - that's why I'm reporting this as a bug! Please read the second line in my very first post "When I login as admin and check the feature code list for that domain the codes are there - only when you login as a user do some of the codes disappear." that's the bug....I don't know how much clearer I can say it? All the PBXNSIP team has to do is try and duplicate the bug by logging in as a end user and you will see that you will be missing the 6 feature codes I listed up above....but instead we post to this thread back and forth for over 2 weeks?? Anyway pbxnsip posted to my other thread that he tested it and confirmed it is a bug and that it will be fixed, you can see his post at the end of this thread: http://forum.pbxnsip.com/index.php?showtopic=3520&hl= Once this bug gets fixed the PAC bug should no longer exist. Thanks
  16. No, it's not an upgrade problem....it's a bug. There were no new feature codes in the upgrade. I just created a new domain to test what you said, also created a new user in that new domain...then I logged in as end user and the feature code list is still missing the above feature codes. Can you guys not duplicate the bug on your end? When I gave you a test account didn't you see the missing codes on your screen?
  17. ??? not sure what your getting at? "Those fields are empty. User can not save/change them anyways." we know that...those 2 feature codes have nothing to do with this bug. There are 6 * codes that are not being listed in the end users feature code list.....I was just letting you know that I removed the *67 and *68 codes so you wouldn't think they are apart of this bug but did you also look and see that there are 6 more feature codes that are not being displayed? That is the bug I'm talking about. Also....use your PAC....click on Feature codes button and none of the feature names are listed anymore except 1 - that's also a bug. This is the thread I started last week reporting the bug: http://forum.pbxnsip.com/index.php?showtopic=3457&hl= Missing feature codes not being displayed in end users web interface: 1. Call return 2. Hot desking 3. Forward calls to domain accounts 4. Send voicemails deactivate 5. Agent logout 6. Record off key Thanks.
  18. Yes, whatever is in the domain page feature list should also appear in the end users feature list. I sent you a message with a test end users login details to my PBXNSIP so you can see the missing feature codes. Thanks,
  19. I have no idea how to show you the xml records or even which ones your referring too. I can give you access to remote into my desktop via an invite with gotomypc and then from within my desktop we can remote into my linux box for you to look around. Thanks
  20. It's defenitly not sorted in my end users web interface - I can give you access to it so you can see with your own eyes. I understand about the whole thing about when the call was disconnected etc but in my list it's off by days. This is what it shows at the top of my Call Log: TIME 2010/04/22 10:01:44 ....THEN CALL DETAILS 2010/04/19 19:52:09 ....THEN CALL DETAILS 2010/04/15 12:11:23 ....THEN CALL DETAILS 2010/04/19 13:01:21 ....THEN CALL DETAILS 2010/04/21 09:57:16 ....THEN CALL DETAILS 2010/04/19 10:26:55 ....THEN CALL DETAILS 2010/04/21 09:56:33 ....THEN CALL DETAILS 2010/04/16 15:13:40 ....THEN CALL DETAILS So you can see it's not in order. Thanks,
  21. Yes, I noticed the double recording was fixed - great! The "the feature code list in the user interface was incomplete" still isn't fixed - I posted info about it in my other thread. Thanks
  22. Were using 4.0.1.3475 linux. I've noticed for awhile now but never posted until now that when a end user logs into the web interface and clicks on Lists then Missed-Calls the list is not in order - it should be sorted by date & time. It's the same thing when the end user clicks on the Call Log it's also all mixed up - it should be sorted as well. This has been a bug for a long time. Thanks
×
×
  • Create New...