I am hoping that you are able to assist me. We are using LogicMonitor to monitor the EDGEs and trunks, however, we have noticed that the EDGE and TRUNK IDs change often which causes the monitoring service to break and alert.
Is there a way around this at all, please?
Hi Chris,
Sorry I did not get back to you sooner on this due to the long holiday weekend. It sounds like you are a BYOC (Bring Your Own Carrier)/PCV (PureCloud Voice) customer.
So the original implementation of our telephony platform involved rolling out individual single-tenant edge servers to our customers running in AWS.
Every time a new version of the edge was released, the old servers were torn down, and brand new servers running the new version of the Edge software were started. This means that the new servers would get a brand new edge id and new trunks created for them. This is why you are having problems with your monitoring solution.
The edge team is actively working on decomposing these single-tenant servers into a multi-tenant set of microservices. This means that eventually these edge servers running in AWS will be completely replaced with microservices. (On-premise servers will still be around). So for the immediate future, there is nothing that can really be done about the changing edge and trunk ids.
However, I just got off the phone with the product manager of the edge team. They are beginning the rollout of the new SIP service to our production regions. Once the new SIP service is in place, your trunk configuration will remain stable. I do not have the details of the exact date of that cutover. Eventually, though the concept of an edge in AWS will disappear and the whole notion of monitoring edges will not be necessary.
I hope that answers your question.
Thanks,
John Carnell
Manager, Developer Engagement
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.