Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

Register Log in
  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Recent content by wiredent

  1. wiredent

    Round Trip Delay Violation Warning

    I am receiving the warning below when I am making IP calls from a 50 to a 400. Round Trip Delay Violation Warning: 49ms, nearDN: 23164, source IP: 172xxx.xxx.xxx, source port: 51000, destination IP: 172xxx.xxx.xxx, destination port: 28000, ct 18, eT D, nLR 10, dR 9, bD 19, bL 0, gD 19, gL...
  2. wiredent

    IP 2002 MIC

    Ok I found that my DHCP for the 2002s had a bad router assignment. I corrected the issue and it resolved the one way speak.
  3. wiredent

    i2002 Firmware Update

    Does anyone know how to apply the IP 2002 firmware to the BCM 50 so that it can be sent to the phone? Or how to get the 2002s to update using TFTP?
  4. wiredent

    IP 2002 MIC

    Does anyone know how to apply the IP 2002 firmware to the BCM 50 so that it can be sent to the phone?
  5. wiredent

    How to reject call?

    You can enable "Call Screening" on the call pilot voice mail to be prompted to accept the call or not.
  6. wiredent

    IP 2002 MIC

    I am trying to find this. UNIStim Firmware Maintenance Release 0604DAX for Phase II IP Phones (2001, 2002 & 2004) It has in the release notes a fix for one way calling.
  7. wiredent

    IP 2002 MIC

    The payloads are set to 30 in all locations. The codec on the trunks are set to an ascending order on both sides. The IP phones are set to auto. I have tried setting a phone to each of the codecs with no success.
  8. wiredent

    IP 2002 MIC

    They are.
  9. wiredent

    IP 2002 MIC

    I have my VoIP setup but the IP phones when they connect do not have the MIC working. ie The person making the call cannot speak to the receiver. You can hear the receiver and but they cannot hear you. They can here number tones and the calls work from a digital DN.
  10. wiredent

    BCM 50 to 400 VoIP

    I have found that if you restart the "VoiceNetVoIPGateway" service it will accept any changes and allow the system to communicate with out having to reboot the system.
  11. wiredent

    BCM 50 to 400 VoIP

    Here is the scoop on IP Telephony with BCM 400 3.6 - 3.7 software. REBOOT THE 400 often!!!!!!! We have probably had the thing configured right for a week. So far I have found that if you change the system name (Business Name) you have to reboot. If you change a target line or extension name...
  12. wiredent

    BCM 50 to 400 VoIP

    If I understand you correctly: If one system is on 4 digit and one is on 3 digit they will not talk properly. So if I cannot change the 400 to 4 digit dialing I need to get the 50 to a set of extension that the 400 is not using. Can I disable extension in in the 400 or can they only be change...
  13. wiredent

    BCM 50 to 400 VoIP

    The rename of the DNs would be more trouble than it is worth. So I renumbered the 50 to start at dn 7000. I am getting the same result as before.
  14. wiredent

    BCM 50 to 400 VoIP

    I agree lets worry about the PRI Later. Recap: BCM 400 v3.6 DNs: 221 – 624 (only using 2s) PRI VoiceMail BCM 50 v2.0 DNs: 400 – 639 (only using 5s) I cannot configure destination code 4 or 5 (ip phones) in the 400 the extension set goes to high. Should I bump the 50 to 700 or 4 digit codes?
  15. wiredent

    BCM 50 to 400 VoIP

    Should I see digits being dialed on the receiving system? ie Start a call from the 50 (see digits in BCM Monitor) to 400 (VoIP line goes active but no digits).
See more

Part and Inventory Search

Back
Top