Jump to content
Vodia PBX forum

Doug

Members
  • Content Count

    30
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Doug

  • Rank
    Advanced Member
  1. No we are trying to block calls from certain callerid's. Thanks. Doug
  2. Saving changes to the Address book at the domain level just doesn't seem to work. I try changing the name or number and it doesn't save. After about 10 tries i finally saved 1 entry with Blacklist type and my cell number. I then set the account attached to the trunk to "reject" or "busy" and the call goes through as if nothing has been set. I must not be doing something correct. I am at 3.3.2.3183 (Win32). Thanks for any ideas. Doug
  3. We have pbxnsip working with Exchnage UM. We have 10 DID numbers inbound in on a SIP trunk that handles 4 concurrent calls. Because each DID goes to a different Exchange AA or OCS user is there a way to route these to Exchange/OCS without defining an extension for each DID in pbxnsip? This adds an 10 more users to the cost for pbxnsip in additional to the real telephone extensions for these same users to call their OCS Communicators and secondary phones in pbxnsip. Or are we doing the DID routing wrong? Thanks for any ideas. Doug
  4. I have pbxnsip working with Exchange and OCS. All trunks come into pbxnsip then are routed to Exchange/OCS. I want to "blacklist" certain callerid's for all trunks going to Exchange/OCS. I tried adding a number to the address book and making the type Blacklist, but whenever I save it, the contact type reverts to regular contact. How do I make it save as "Blacklist"? Then on the Account under redirection I still want anonymous calls to route but block "Blacklist" calls. How do I define that? Or is there a better way? Thanks for the help. Doug
  5. With version -3.3.2.3183 and setting an alias on the hunt group 110 of +110. Calls to hunt groups are working. You guys are great. Thanks.
  6. With version -3.3.2.3183 and setting an alias on the hunt group 110 of +110. Calls to hunt groups are working. You guys are great. Thanks.
  7. When I make a call from the OCS trunk to pbxnsip calls are handled differently that calls coming in from my carrier trunks or other pbxnsip phones If I call an extension from another pbxnsip extension or my carrier trunks the extension rings and the cell phone rings If a call an extension from Communicator the extension rings but the cell phone does not ring. If I call a hunt group from another pbxnsip phone or carrier the extensions in the hunt group ring. If I call the hunt group from Communicator I got an error in the log indicated it was not an extension that I was calling. Calls from Exchange AA to the hunt also have this error. Shouldn't the calls work the same regardless of the source being the carrier trunks, pbxnsip phones, or OCS/Exchange calls? This seems to be a critical need on our part. Thanks, Doug
  8. Hi we are testing pbxnsip with OCS and Exchange. I believe I heard OCS will only use the 711 codec. I have OCS pointing to pbxnsip as the gateway. Then pbxnsip points to the SIP trunks . The issue is being able to use G729 codec on the trunk from pbxnsip to the carrier. Our trunk carrier can give preference to 729 over 711. We want to save bandwidth so we want whenever possible to use 729. So I set the trunks from pbxnsip to the carrier to prefer 729 then 711. If I make a call from a phone connected to pbxnsip all audio quality seems fine. The carrier says it is using 729. If I make a call from Communicator out the inbound audio is fine but the person I call says it sounds very bad. The carrier says it is using 711. Since I am codec impaired I really need to know how to specify the codec to use on the trunks so the OCS communicators sound as good as the voip phones. What are the correct settings to use? Thanks, Doug
  9. Sorry to be a pest. Is there anything new for me to try? This is an important feature for us. Thanks. Doug
  10. I took the sample XML file on the interop support page for the Cisco phone and copied critical differences from my old XML file. It now works without losing the registration. When I have nothing to do I will try to determine the problem, but for now it works. Thanks for everyones help. Doug
  11. I put firmware 8.4.4 on the phone and the registration still gets "lost" after about 15 minutes. Any ideas? Thanks Doug
  12. I was able to modify the route patterns in OCS and made it accept 313105551212 for 1 callerid 413105551212 for another. Then in pbxnsip defined multiple trunks with different ANI's. Then in the dial plan for a trunk +31* and replace with 1* for another trunk +41* and replace with 1*. Since Broadvox supports non-registered trunks with static IP, it all works great. Thanks for everyones hjelp. Doug
  13. The call route was: From outsiude phone inbound to Broadvox trunk, routed to Exchange UM. Today it is ringing. yesterday it was not. Thanks for the replies. I will watch for things. Doug
  14. The timeout is set to 3600. The nat_enabled only seems to apply to the 7960 serirs config files. I am not sure how to enter that in the XML format. I will try to get firware 8.4.3 or higher. I will let you know. Thanks. Doug
  15. I have a Cisco 7971G. When it starts it registers with no problems. It seems o work fine. After about 10 minutes it loses the registration. When I reboot it, it registers fine again but loses the registration. If I manual register it, all seems to work. Initially I see the automatic registration along with the manual one, but then the automatic one disappears. The firmware versio is SIP70.8-3.2S. This phone works fine on other IP PBX systems. Doug
×
×
  • Create New...