Jump to content
Vodia PBX forum

Fred Gaston

Members
  • Content Count

    26
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Fred Gaston

  • Rank
    Member
  1. Thanks very much Hirosh: We have a different subnet on the 2nd NIC that is connected to the Intertex router which in turn is conncected straight to the internet. Should virtual ip address for openvpn be changed from 10.5.0.1 in your sample config to one from within that subnet? Can you explain the 2 IP addressed in the config file? Thanks, Fred
  2. Kristan: I'm not sure we ever got sip multicast to work properly but attached works for us and gets the phones provisioned with pbxnsip. I'm sure there are several ways to do this, and maybe some are simpler. Hope some or all of this helps. Regards, Fred Provisioning_Snom_360_Phones_2.doc snom360.htm
  3. Can you speak to the setup please? My understanding of the ports on home firewall that need to be opened are: TCP: 5060-5061 UDP: 5060,49152-64512 Does TLS pass through these ports, does the firewall have to support TLS? I could only get connection by setting ;transport=TLS switch via port 5061 in outbound proxy field. Should it be different setup if connecting from outside the domain? Thanks
  4. Thank you very much for the clarification. On another note, I'm trying to hook-up Snom 370's from employee's homes. I would like to use VPN feature, but the Snom directions seem geared more to Linux setup & are difficult to follow. I'm able to connect to pbxnsip (without phone VPN) with Intertex SIP router connected that that server however still have to jump through all the SIP hoops at home & if home router doesn't support SIP, it connects but no audio. Anyway with or without phone VPN to beat the home firewall configuration (ICE, STUN?) that you know of, and if via phone VPN any advice on configuration? Thanks, Fred
  5. Your reply makes no sense to me. You stated in August: "Well, with the snom we are in the middle of finishing something really nice. The 7.2 version will support "buttons", where the PBX can take full control over the LED. it will also support XML-based directory, where the phones pull the address book on the fly from the PBX. Unfortunately, there is no usable 7.2 version available yet..." I am simply following up on your historical post. Why would you indicate there is no need for 7.2 when you claimed in August it was being worked on? Familiarizing yourself with all prior posts before responding would be appreciated.
  6. Any update please on timeframe for v.7.20? Thanks, Fred
  7. Valerio: Thanks for the update. Did you force registration of ocs number in pbxnsip for each user? Can you provide example of dialplan which would enable the call forking?Assume no luck on presence from phone, correct? Regards, Fred
  8. Per MS: Qualified IP-PBXs for Microsoft Office Communicator 2007 Our IP-PBX Partners are currently developing solutions for integrating Office Communications Server 2007 with Direct SIP, Dual Forking, and Dual Forking with Remote Call Control. This section will be updated to reflect IP-PBX and firmware combinations that have been independently qualified for a given configuration. More information coming soon Perhaps you can contact them to investigate what's necessary for integration & let us know if it's doable and something you'll persue. I also found 3rd party CSTA server that is fully compliant with OCS. Depending on cost, it might be easier to use than you guys incorporating CSTA, if it would take months of development (I got impression from your 1st reply it didn't look that hard). It is: http://www.unigone.com/en/products/TelServer/description Thanks, Fred
  9. Charl: Let me clarify. OCS supports call forking but to invoke the pbx needs to support CSTA (please see post below), which does not sound like it's coming anytime soon. I searched for 3rd party solutions and found none. Perhaps TAPI will work. My tech did say in the absence of a presence/sip server like Cisco employs, you'd need to set static routes for each user in OCS. Perhaps this combined with setting static registration in pbxnsip for OC uri & it might work... Keep me in the loop on what you uncover. Thx, Fred http://forum.pbxnsip.com/index.php?showtopic=350
  10. Can you please advise if there is current workaround with 3rd party solution and/or your timeframe for implementing.
  11. OCS client doesn't register with pbxnsip. Is it possible to force a manual registration or denote the SIP address of the OCS client in pbxnsip, to permit forking?
  12. Interesting you ask this. I posted this question & received following answer from Admin. "Forking calls was supported since version 1.0. Just register an extension twice and they will ring at the same time. I don't know why some people have so many problems with this trivial feature." So while pbxnsip supports forking, UM/OCS apparently does not. Per my OCS expert, OCS will not register with pbxnsip, as endpoint, & you can't have both simultaneously ring. We reasoned that if someone wants to dial a hard phone they dial extension; if they want to connect to another OC client they just choose name. Still exploring PBX Integration field, but he is saying this is used with Cisco to light up MWI lamp on phone. I am exploring SIP server that would broadcast presense of phones via the SIP url to OC. Is your understanding on any of the above different? Regards, Fred
  13. Per the 2.1 release notes there is new feature in trunk: Feature: When a trunk initiates a redirect, there was a problem that there was no user available that could be used for charging (and for the dial plan). This was e.g. a problem when using Microsoft Exchange. This problem is now solved by a new setting that explicitly tells the PBX what accounts to charge for such redirected calls. Can someone explain the use of this please and what extension to designate. Thx
  14. Valerio: Couple of questions: What extension did use for Assume that call comes from user? Are you using Exchange UM Auto Attendant, and if so do you route from your external gateway through pbxnsip Can you provide contact information so I can bounce my configuration off you? Thanks, Fred
  15. I have reviewed that document. Here's my scenario 1. I can dial UM prefix + UM AA = 7222 internally & get to UM AA just fine. 2. But when I have an incoming call via another trunk it can resolve a pbxnsip AA extension (500) but not 7222. 3. I imagine there must be a code that will redirect it via another trunk to Exchange & ext 222. Basically I want to send all incoming calls to 7222, regardless of the trunk, but the ITSP doesn't know what to do with 7222. Thanks
×
×
  • Create New...