- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
-
Porting Numbers: Primarily you need to raise a support ticket with AWS with the LOA to port the numbers to Amazon Connect. Please refer the section "Porting numbers purchased from other contact center providers" in the document.
https://docs.aws.amazon.com/connect/latest/adminguide/what-numbers-can-be-ported.html -
There is a soft limit of 10 Concurrent calls per instance and can be increased by raising a service quota request form. Please refer the document for opening the support request: https://docs.aws.amazon.com/connect/latest/adminguide/amazon-connect-service-limits.html
-
Calls will be charged as per the usage /pricing (minutes), but not by concurrency.
- I've seen customers do different things. First, is to port the numbers to AWS like it was mentioned. The other is to have the telco provider forward calls to a new dummy number which AWS owns. This way you can control your main DIDs if you ever need to do any sort of DR or alternative routing.
- There's no charge for creating a service request to increase your limit.
I have a lot of UCCX experience, make sure you do a deep dive into Connect works to avoid any surprises. Because UCCX is so tightly coupled with UCM you can do some cool telephony things when it comes to transfers/outbound calls, but this is not the case in Connect.
Relevanter Inhalt
- Wie verbinde ich verschiedene Zweigstellen mithilfe von AWS Site-to-Site VPN und AWS Direct Connect?AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor 4 Jahren
Thank you Phani_L for your time and answeres.
With related to the answeres on the 2nd question, If that raised by service quota request form does that chargable?