Jump to content
Vodia PBX forum

kellenw

Members
  • Content Count

    44
  • Joined

  • Last visited

Community Reputation

0 Neutral

About kellenw

  • Rank
    Advanced Member
  1. Hello, I've got a couple CS410's and about 15 phones (a mix of Snom 320's and 360's) sitting in our "IT boneyard" collecting dust. They've not been touched in about 4 or 5 years at least. The CS410's have some old PBXNSIP firmware on them. Originally, I authorized purchase of them to deploy in a couple small branch offices of ours, but after trying for months and months to get them to function reliably, I made the decision to scrap the project. We encountered constant issues between the PBXNSIP software and SNOM firmware (there always seemed to be a couple of glitches between the two back then). Each time we'd upgrade one or the other to fix a problem, they'd seemingly introduce some other issue. hehe... They've sat in storage ever since. Now present day, a friend of mine who owns a small business said he was looking for a simple cheap pbx to deploy, and I casually said he could have one of the CS410's and as many Snom phones as he'd like if wanted to try them. He'd probably use no more than 4 or 5 phones. I'd have to help him get it all setup and working properly, so I would like to avoid a big time sink if these just aren't up to the task. My questions are: - Are the CS410's still supported? - What are my firmware options for them at this point? - Are the CS410's considered reliable/stable at this point? - Is this worth my time, or should I tell my friend to look for a different option? Thanks for any thoughts, advice or comments. Sincerely, Kellen
  2. I'm having this issue all of the sudden also.
  3. Thanks for the info Alex. I'm not sure what I should do at this point. I may need to just scrap pbxnsip for something more capable. That would be quite a let down considering the amount of time and money we have already invested in it, but if it's not the best route to go....
  4. Okay. I setup an extension (900) on the "HQ" box in the lab, and a trunk on the "branch" box to register to it. Both boxes show the extension is correctly registered. Now, how do I go about paging, transferring and using phone lines from one box on the other? I've tried the usual, but I'm stumped. Thanks!
  5. This would probably work out perfectly. I figured I would have to setup "gateway" trunks and so forth. Simple exensions and registrations would be a breeze, if they can accomplish what I'm looking for. I'm going to work on setting this up in the lab between the two CS410's I have, and I'll report back. Thanks pbxnsip!
  6. I have gone through the knowledge base and searched the forums, which shed a little light on this topic, but I'm still having a hard time wrapping my mind around the full concept and setup process. I currently have 2 CS410's running the latest v4 beta in the testing lab that will be placed in the branch offices. I plan to purchase a windows pbxnsip license for HQ. The system needs to do the following: - All users in all 3 locations can intercom each other. - Calls can be transferred from one office to any of the others. - Users can dial out on CO lines of other offices. Things I would like the system to do, but could live without if I had to: - BLF possible for CO lines of other offices. (without registing phone to other office's pbx) - Ability to pickup another office's ringing CO line (also without registering phone to other office's pbx... multiple registrations cause too many issues for me). - BLF for phone extensions of other offices (again, without registering phone to other office's pbx). Is this possible? Am I crazy for wanting to try it? Can someone point me to any documentation that covers this? Thanks for any input or advice!
  7. PNP Buttons setup: I have ext's 40, 41, 42, 43 on BLF for 4 SNOM 360's. I have ext's 651, 652, 653, 654 for park orbits. For example, when I dial ext 42 from ext 41 and answer the page/call, the correct BLF's for 42 and 41 light up (as they should). However, when I place one of the ext's (we'll say 42) into park orbit (on 651), the call parks correctly, the extension that was placed on park (42) hears MOH and the lamp for park orbit extension 651 lights up, but the BLF light for extension 42 that was placed on park orbit goes away. The extension 42 is still actively on a "call", so shouldn't it remain lit? Obviously 41 is not busy at the moment so it should not be lit (and it is not, so that's correct), but 42 should be lit up. It's busy on a call, regardless of whether it is parked or not. I've noticed this with all prior releases I've used as well.
  8. I too am waiting for a fix for this. Seems logical that when you pull a call from park orbit (regardless of method such as BLF or direct star code) that it should display the caller id associated with the party you are pulling from orbit. It's no fun having to ask "who am I speaking with" after they've already told you once before. It can be a little annoying for the caller.
  9. I just tried a demo account with Voicepulse and they support custom outgoing ANI (works perfect), so if PBXNSIP was capable of handing off the incoming caller id as a custom ANI in real time on a forwarded call, it would work like a dream. In the v4 beta, if you include a cell phone in a hunt group (under redirection settings in a user account/ext) and enable "press 1 to connect", the PBX will at least read back the incoming caller id when you answer and give you the choice of accepting the call (pressing 1) or hanging up (which keeps the call ringing to other phones in the hunt group). It isn't quite as you would like, but it's SOMEWHAT of a solution that will be out soon in a production ready release. I actually wouldn't mind having custom ANI on a forwarded call as a feature, though it isn't high on my list.... still would be handy though.
  10. My issue is a little different than shopcomputer's. Caller calls into system. Hunt group phones ring. Cell phone rings. If you answer cell phone, you get dead air... no connection to caller and caller's phone still continues to get ringing because system has not answered their call. If the snom hunt group phones pick up, all is normal. Simply put, the call isn't being connected to the cell phone when the cell phone is placed in the hunt group.
  11. pbx support - CS410 version. Single hunt group with incoming calls on 4 line sip trunk coming directly into hunt group (no AA). Calls are not "answered" by system until someone in hunt group picks up the call. Also single PSTN line on FXO port 1. Both the PSTN trunk and the sip trunk behave the same. Very basic setup.
  12. You could also put them in seperate VLAN's if your routers/switches have the ability to do so.
×
×
  • Create New...