94
« Last post by victor on June 05, 2024, 11:02:09 AM »
Brilliant!
[quote author=hsujdik link=topic=12486.msg55486#msg55486 date=1701866391]
I have a suggestion that might work but I'm not entirely sure since I do not have anything prepared to test it. It will depend a lot on your architecture though.
1. The agents SIP Endpoints would need to be directly registered to Genesys SIP Server (and not through a Session Border Controller);
2. You would need the option "internal-registrar-persistent" set to True on your SIP Server. And also, for this to work, the account that SIP Server is starting as (usually "SYSTEM") would need to have change permissions on the extensions DNs. This way, whenever a SIP Endpoint registers to an Extension, SIP Server would update its "Annex" tab / "contact" option with the SIP URI to reach the Endpoint (e.g. TServer\contact = sip:10.10.10.10:5090)
3. Instead of a regular "Select Target" block on your strategy, you use the "expanded" version: SelectDN, SuspendForDN, TRoute... This way you are able to get the DN that has been targeted (another approach would be to use the "Custom Routing" on the General tab of the "Select Target" block);
4. Once you have the DN that has been selected using the step 3 above, use URS function "GetObjectProperty" to retrieve the option TServer\contact of that given DN;
5. Parse the retrieved result form step 4 by removing the "sip:" prefix and the port number suffix (if applicable).
Again, I'm not sure if this will work since I cannot test it, and also depends if your environment falls on condition "1" above and your SIP Server is configured as "2" above.
[/quote]