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!

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

Search results for query: *

  • Users: jtc22
  • Order by date
  1. jtc22

    Utility Server 7.1 won't let me replace 96x1Huapgrade.txt file

    You can download the 96x1Hupgrade.txt file, modify it and re-upload via the Utility Server custom file upload. jtc22
  2. jtc22

    Would Like to know if anyone Upgraded their AYAYA Aura 6.x to 7.x Using existing Servers????

    Here's some of the system and licensing changes from 6.3 to 7.1 1. Although it is $0 license SMGR 7.1 now is licensed so make sure this is in the quote file. 2. Utility Services 7.1 is also licensed. US 7.1 support for HTTP is disabled by default it needs to be manually enabled in CLI. 3...
  3. jtc22

    Would Like to know if anyone Upgraded their AYAYA Aura 6.x to 7.x Using existing Servers????

    Have done it for a number of customers of ours. You basically backup the old servers - the application backups and if you can do old server image backup using backup softwares like Acronis that will be much better. If you don't make sure you have copy of all the 6.x softwares (SP,CM ISO...
  4. jtc22

    Change the passwords on the platform

    Can you indicate what software versions these servers are running?
  5. jtc22

    SMGR upgrade from 7.0 to 7.1 with data migration

    Is the vFQDN the same on both 7.0 and 7.1 SMGR?
  6. jtc22

    Number and type of OVAs on S8300E / WebLM

    Forgot to add CMM 7.1 as well.
  7. jtc22

    Number and type of OVAs on S8300E / WebLM

    You can deploy AVP,US,CM all 7.1 and WebLM 7.0. The WebLM 7.1 footprint is not supported because of resource limitations.
  8. jtc22

    Number and type of OVAs on S8300E / WebLM

    There is a deployment scenario where only CM/G4x0 on S8300E purely H.323 and TDM with no SMGR. In this case standalone weblm is needed to be hosted in S8300E.
  9. jtc22

    Number and type of OVAs on S8300E / WebLM

    For WebLM you cannot install 7.1 on S8300E because if resource limitation. Deploy WebLM 7.0 instead this has minimal resource requirement.
  10. jtc22

    Converting an H.323 Extension to a SIP Ext: Two Issues that came up.

    Run a full-sync between and SMGR. You don’t need to make changes in the CM for type from 96x1 to 96x1SIP as soon as you add CM endpoint profile in SMGR it will push it to CM adding user extension and map OPS automatically. This is considering your CM & SMGR are synced.
  11. jtc22

    International trunk-group in U.K. inserting a comma in the incoming caller id header

    list trace tac # what does it shows coming in?
  12. jtc22

    Hunt Group/Agent Logins

    Is your agent in Available state when you monitor hunt-group 1, command i think is “monitor hunt-group 1.”
  13. jtc22

    System Manager 7.1 "Public Contacts" bulk Import - how can I do?

    Were you able to figure this out? On the same situation have to import H.323 contact list to make it available on SIP phones.
  14. jtc22

    help avaya g450+ s8300e

    You can’t install SMGR on S8300E not enough resources.
  15. jtc22

    Cannot deploy Utility Server 7.1 on AVP (S8300E)

    Workaround is to login to AVP with vSphere client and run the Utility server config wizard setup as if you are deploying US on VMware. The issue you are getting when deploying on AVP using SDM client is because the network interface config is not able to setup successfully. Once you run ythe...
  16. jtc22

    System Manager adding new user - what's next?

    Hello, I got my System Manager synced with AD, sync all good and completed. CM template and User Provisioning Rule were added. Now how do I add new user via the users from AD? Never tried this before it's all manual user add with the User Provisioning Rule. Any help is appreciated.
  17. jtc22

    Avaya SBCE+EMS 7.2.1

    3 IPs: Management, A1 for internal communications to SM/CM, and B1 facing internet for remote workers.
  18. jtc22

    CM to Session Manager - 404 Not found (No route available)

    The obvious difference is the number you are calling. The dialed number in the left may not be in the SM dial patterns or the originating CM is not allowed to make that call.
  19. jtc22

    Avaya Communicator for Windows through SBC

    Have you tried running traceSBC inthe SBC and register Avaya Communicator? From there you should see what’s going on if the client attempts to register to the IPO via the SBC. You can also include capturing SIP and TLS Handshake in the trace. If I remember it right there is also a specific...
  20. jtc22

    Avaya IP phones through SBC

    It is an IP Office product limitation as it doesn’t support 96x1 SIP only H.323.

Part and Inventory Search

Back
Top