Genesys Cloud - Main

Hi There,

We do have an inbound call flow which transfers to an external number. The problem is the CLI displayed on the other end is the Genesys cloud trunk caller ID.

The customer prefers to have the originating Caller ID needs to be passed from Genesys during external transfers.

We use BYOC cloud and Audio codes SBC.

I would like to know how others implemented the above requirement. Any Thoughts?

Thanks

Hi Prem,

On the SIP trunk you can set Diversion Method under Protocol.

If you look at the PCAP for the call Genesys will forward the original ANI if this is configured properly, but it also depends on what method your SIP provider supports.

Hi There,

We do have an inbound call flow which transfers to an external number. The problem is the CLI displayed on the other end is the Genesys cloud trunk caller ID.

The customer prefers to have the originating Caller ID needs to be passed from Genesys during external transfers.

We use BYOC cloud and Audio codes SBC.

I would like to know how others implemented the above requirement. Any Thoughts?

Thanks

@Jan Heinonen  Thank you, for the update. Tested by setting the Diversion method, and I can see the diversion header added in the Invite messages, but the value is the DNIS, not the original ANI. Anything I am missing here on the SIP trunk configuration?

Hi Prem,

On the SIP trunk you can set Diversion Method under Protocol.

If you look at the PCAP for the call Genesys will forward the original ANI if this is configured properly, but it also depends on what method your SIP provider supports.

Hi There,

We do have an inbound call flow which transfers to an external number. The problem is the CLI displayed on the other end is the Genesys cloud trunk caller ID.

The customer prefers to have the originating Caller ID needs to be passed from Genesys during external transfers.

We use BYOC cloud and Audio codes SBC.

I would like to know how others implemented the above requirement. Any Thoughts?

Thanks

The Diversion header should be the DNIS, the original ANI should be in the From and Contact header.

@Jan Heinonen  Thank you, for the update. Tested by setting the Diversion method, and I can see the diversion header added in the Invite messages, but the value is the DNIS, not the original ANI. Anything I am missing here on the SIP trunk configuration?

Hi Prem,

On the SIP trunk you can set Diversion Method under Protocol.

If you look at the PCAP for the call Genesys will forward the original ANI if this is configured properly, but it also depends on what method your SIP provider supports.

Hi There,

We do have an inbound call flow which transfers to an external number. The problem is the CLI displayed on the other end is the Genesys cloud trunk caller ID.

The customer prefers to have the originating Caller ID needs to be passed from Genesys during external transfers.

We use BYOC cloud and Audio codes SBC.

I would like to know how others implemented the above requirement. Any Thoughts?

Thanks

I verified the Invite message from GC, the original ANI is not in the from or contact header. Both headers display the GC trunk CLI.

The Diversion header should be the DNIS, the original ANI should be in the From and Contact header.

@Jan Heinonen  Thank you, for the update. Tested by setting the Diversion method, and I can see the diversion header added in the Invite messages, but the value is the DNIS, not the original ANI. Anything I am missing here on the SIP trunk configuration?

Hi Prem,

On the SIP trunk you can set Diversion Method under Protocol.

If you look at the PCAP for the call Genesys will forward the original ANI if this is configured properly, but it also depends on what method your SIP provider supports.

Hi There,

We do have an inbound call flow which transfers to an external number. The problem is the CLI displayed on the other end is the Genesys cloud trunk caller ID.

The customer prefers to have the originating Caller ID needs to be passed from Genesys during external transfers.

We use BYOC cloud and Audio codes SBC.

I would like to know how others implemented the above requirement. Any Thoughts?

Thanks

What do you have as Prioritized Caller Selection on the trunk?

I believe this needs to be set to Call Source.

I verified the Invite message from GC, the original ANI is not in the from or contact header. Both headers display the GC trunk CLI.

The Diversion header should be the DNIS, the original ANI should be in the From and Contact header.

@Jan Heinonen  Thank you, for the update. Tested by setting the Diversion method, and I can see the diversion header added in the Invite messages, but the value is the DNIS, not the original ANI. Anything I am missing here on the SIP trunk configuration?

Hi Prem,

On the SIP trunk you can set Diversion Method under Protocol.

If you look at the PCAP for the call Genesys will forward the original ANI if this is configured properly, but it also depends on what method your SIP provider supports.

Hi There,

We do have an inbound call flow which transfers to an external number. The problem is the CLI displayed on the other end is the Genesys cloud trunk caller ID.

The customer prefers to have the originating Caller ID needs to be passed from Genesys during external transfers.

We use BYOC cloud and Audio codes SBC.

I would like to know how others implemented the above requirement. Any Thoughts?

Thanks