We gave the system a solid 5 minutes before testing the second time, however, the SIP message received is still following the old identifier.
Noted on the outbound route, did for both inbound and outbound.
Raised a case to Care.
Do we need to request to start EDGE? Any cached settings on EDGE?
------------------------------
Jin Huey Boey
ITApps Sdn Bhd
------------------------------
Original Message:
Sent: 08-13-2019 14:23
From: George Ganahl
Subject: Trunk settings changes not taking effect immediately
From Dev:
Saving a trunkbase [trunk settings] should kick off a notification event. The changes are not immediate but should be very quick (less than 10 seconds). The trunk must assigned to a Site's OUTBOUND route, even if the trunk is only used of INBOUND traffic.
If this is not the behavior you are seeing, you should contact Care to open a case.
------------------------------
George Ganahl GCP (PureCloud) ICCE CCXP
Principal Technology Consultant
Genesys
Original Message:
Sent: 08-13-2019 06:38
From: Jin Huey Boey
Subject: Trunk settings changes not taking effect immediately
We have done a few test calls today using some trunk settings with different Unique Identifier for Inbound SIP Termination Identifier and Outbound SIP DNIS as per our external SIP provider requests. We realised that the changes are not taking effect immediately after making changes to the settings.
Is there a periodic update from our org before our settings take effect? Do we need to restart Edge / Phones every time we make some changes? If I'm using Edge from AWS and not having access to Edge logs, how to I force the changes to update before the next test?
#ArchitectureandDesign
#Outbound
#SIP/VolP
#Telephony
------------------------------
Jin Huey Boey
ITApps Sdn Bhd
------------------------------