Genesys Cloud - Main

Context for the Community

• In Genesys Cloud CX, the Set UUI Data action in Architect flows allows you to embed values into the x‑User‑To‑User header.
• This works fine for passing ABC/XYZ or other participant data, but it results in values being encapsulated inside x‑User‑To‑User rather than appearing as standalone custom SIP headers.
• The requirement is to send dynamic values directly into custom SIP headers (e.g., X‑ABC, X‑XYZ) without relying on x‑User‑To‑User.

What I've Observed

• External Trunk configuration supports adding custom SIP headers, but those are static values only - they don't resolve Architect variables at runtime.
• Architect Transfer to External Number/Trunk actions allow adding SIP headers, but again, the binding options are limited.
• Documentation suggests that outbound dynamic headers are generally supported only via UUI (x‑User‑To‑User).

Clarification Needed

1. Is there a supported way to bind dynamic participant data variables directly into custom SIP headers (e.g., X‑ABC, X‑XYZ) in Architect?
2. If not natively supported, is the recommended approach to continue using Set UUI Data and encapsulate values inside x‑User‑To‑User?
3. Are there any roadmap items or workarounds  that allow dynamic custom SIP headers outside of UUI?

#ArchitectFlow #ExternalTrunk #SIP #SIPHeader #customSIP header

#ArchitectandDesign

------------------------------
GM
------------------------------

Context for the Community

• In Genesys Cloud CX, the Set UUI Data action in Architect flows allows you to embed values into the x‑User‑To‑User header.
• This works fine for passing ABC/XYZ or other participant data, but it results in values being encapsulated inside x‑User‑To‑User rather than appearing as standalone custom SIP headers.
• The requirement is to send dynamic values directly into custom SIP headers (e.g., X‑ABC, X‑XYZ) without relying on x‑User‑To‑User.

What I've Observed

• External Trunk configuration supports adding custom SIP headers, but those are static values only - they don't resolve Architect variables at runtime.
• Architect Transfer to External Number/Trunk actions allow adding SIP headers, but again, the binding options are limited.
• Documentation suggests that outbound dynamic headers are generally supported only via UUI (x‑User‑To‑User).

Clarification Needed

1. Is there a supported way to bind dynamic participant data variables directly into custom SIP headers (e.g., X‑ABC, X‑XYZ) in Architect?
2. If not natively supported, is the recommended approach to continue using Set UUI Data and encapsulate values inside x‑User‑To‑User?
3. Are there any roadmap items or workarounds  that allow dynamic custom SIP headers outside of UUI?

#ArchitectFlow #ExternalTrunk #SIP #SIPHeader #customSIP header

#ArchitectandDesign

------------------------------
GM
------------------------------

Context for the Community

• In Genesys Cloud CX, the Set UUI Data action in Architect flows allows you to embed values into the x‑User‑To‑User header.
• This works fine for passing ABC/XYZ or other participant data, but it results in values being encapsulated inside x‑User‑To‑User rather than appearing as standalone custom SIP headers.
• The requirement is to send dynamic values directly into custom SIP headers (e.g., X‑ABC, X‑XYZ) without relying on x‑User‑To‑User.

What I've Observed

• External Trunk configuration supports adding custom SIP headers, but those are static values only - they don't resolve Architect variables at runtime.
• Architect Transfer to External Number/Trunk actions allow adding SIP headers, but again, the binding options are limited.
• Documentation suggests that outbound dynamic headers are generally supported only via UUI (x‑User‑To‑User).

Clarification Needed

1. Is there a supported way to bind dynamic participant data variables directly into custom SIP headers (e.g., X‑ABC, X‑XYZ) in Architect?
2. If not natively supported, is the recommended approach to continue using Set UUI Data and encapsulate values inside x‑User‑To‑User?
3. Are there any roadmap items or workarounds  that allow dynamic custom SIP headers outside of UUI?

#ArchitectFlow #ExternalTrunk #SIP #SIPHeader #customSIP header

#ArchitectandDesign

------------------------------
GM
------------------------------

Hi Mutthukumar! Your question has an answer on the newest episode of the Q&A Show. Chapter marker 6:13. Hope this helps you! 

Context for the Community

• In Genesys Cloud CX, the Set UUI Data action in Architect flows allows you to embed values into the x‑User‑To‑User header.
• This works fine for passing ABC/XYZ or other participant data, but it results in values being encapsulated inside x‑User‑To‑User rather than appearing as standalone custom SIP headers.
• The requirement is to send dynamic values directly into custom SIP headers (e.g., X‑ABC, X‑XYZ) without relying on x‑User‑To‑User.

What I've Observed

• External Trunk configuration supports adding custom SIP headers, but those are static values only - they don't resolve Architect variables at runtime.
• Architect Transfer to External Number/Trunk actions allow adding SIP headers, but again, the binding options are limited.
• Documentation suggests that outbound dynamic headers are generally supported only via UUI (x‑User‑To‑User).

Clarification Needed

1. Is there a supported way to bind dynamic participant data variables directly into custom SIP headers (e.g., X‑ABC, X‑XYZ) in Architect?
2. If not natively supported, is the recommended approach to continue using Set UUI Data and encapsulate values inside x‑User‑To‑User?
3. Are there any roadmap items or workarounds  that allow dynamic custom SIP headers outside of UUI?

#ArchitectFlow #ExternalTrunk #SIP #SIPHeader #customSIP header

#ArchitectandDesign

------------------------------
GM
------------------------------

Hi Mutthukumar! Your question has an answer on the newest episode of the Q&A Show. Chapter marker 6:13. Hope this helps you! 

Context for the Community

• In Genesys Cloud CX, the Set UUI Data action in Architect flows allows you to embed values into the x‑User‑To‑User header.
• This works fine for passing ABC/XYZ or other participant data, but it results in values being encapsulated inside x‑User‑To‑User rather than appearing as standalone custom SIP headers.
• The requirement is to send dynamic values directly into custom SIP headers (e.g., X‑ABC, X‑XYZ) without relying on x‑User‑To‑User.

What I've Observed

• External Trunk configuration supports adding custom SIP headers, but those are static values only - they don't resolve Architect variables at runtime.
• Architect Transfer to External Number/Trunk actions allow adding SIP headers, but again, the binding options are limited.
• Documentation suggests that outbound dynamic headers are generally supported only via UUI (x‑User‑To‑User).

Clarification Needed

1. Is there a supported way to bind dynamic participant data variables directly into custom SIP headers (e.g., X‑ABC, X‑XYZ) in Architect?
2. If not natively supported, is the recommended approach to continue using Set UUI Data and encapsulate values inside x‑User‑To‑User?
3. Are there any roadmap items or workarounds  that allow dynamic custom SIP headers outside of UUI?

#ArchitectFlow #ExternalTrunk #SIP #SIPHeader #customSIP header

#ArchitectandDesign

------------------------------
GM
------------------------------