Genesys to Omnichannel SBC Setup -- 2
Budget: ₹37,500 – ₹75,000 INR
I am moving our voice workload from a legacy Genesys environment into Microsoft Dynamics 365 Omnichannel and need an engineer who can get our AudioCodes Mediant 2600 SBC ready for the cut-over. The immediate task is a routing configuration—specifically a new SIP-trunk setup that will let Omnichannel handle inbound and outbound calls while the old Genesys trunks are decommissioned.
What I already have
• The Mediant 2600 is in production, running stable firmware and registered in our DMZ.
• All carrier trunks are active and reachable; firewall rules are in place.
• Test numbers for acceptance are available.
What I need from you
• Design and apply a clean SIP trunk configuration on the Mediant 2600 for Microsoft Omnichannel.
• Preserve existing call flows until final migration day, then switch traffic to the new trunk with minimal downtime.
• Validate codec negotiation, TLS/SRTP where required, and fail-over behaviour.
• Provide a short run-book so my internal team can reproduce or roll back the changes.
Acceptance criteria
1. Inbound and outbound calls reach Microsoft Omnichannel with correct caller ID and media quality.
2. Genesys trunks remain functional until we give the go-ahead for final cut-over.
3. Post-change call quality tests (MOS ≥ 4.0) pass on at least three carriers.
4. All changes are documented and exported from the SBC.
You should be comfortable with AudioCodes CLI and Web GUI, SIP ladder analysis (Wireshark or Audiocodes Syslog), and Microsoft Teams/Omnichannel voice architecture. I have remote Console and RDP access ready once an NDA is in place, and I am happy to schedule the work during off-peak hours to keep risk low.
If you have completed similar Genesys-to-Microsoft migrations or complex SIP trunk deployments, I would love to see a brief summary when you reply.
What I already have
• The Mediant 2600 is in production, running stable firmware and registered in our DMZ.
• All carrier trunks are active and reachable; firewall rules are in place.
• Test numbers for acceptance are available.
What I need from you
• Design and apply a clean SIP trunk configuration on the Mediant 2600 for Microsoft Omnichannel.
• Preserve existing call flows until final migration day, then switch traffic to the new trunk with minimal downtime.
• Validate codec negotiation, TLS/SRTP where required, and fail-over behaviour.
• Provide a short run-book so my internal team can reproduce or roll back the changes.
Acceptance criteria
1. Inbound and outbound calls reach Microsoft Omnichannel with correct caller ID and media quality.
2. Genesys trunks remain functional until we give the go-ahead for final cut-over.
3. Post-change call quality tests (MOS ≥ 4.0) pass on at least three carriers.
4. All changes are documented and exported from the SBC.
You should be comfortable with AudioCodes CLI and Web GUI, SIP ladder analysis (Wireshark or Audiocodes Syslog), and Microsoft Teams/Omnichannel voice architecture. I have remote Console and RDP access ready once an NDA is in place, and I am happy to schedule the work during off-peak hours to keep risk low.
If you have completed similar Genesys-to-Microsoft migrations or complex SIP trunk deployments, I would love to see a brief summary when you reply.
Related categories:
Asterisk PBX
Cisco
VoIP
Microsoft
Network Administration
Documentation
Cloud Networking
SIP