Genesys Cloud - Main

I am struggling to remember what carriers use for heartbeat to understand if the four load balancer addresses are up and available. Timeouts of 5 seconds clearly aren't acceptable, so in the absence of OPTIONS, what else is there for them to use? 

We have a situation where SIP calls will not be sent without a response to OPTIONS.
Some workarounds aren't pretty, but potentially could be anything that causes a bad Call-ID. However, not sure if too many of those would send out alarms.

In theory if you are talking about BYOC Cloud, the land balancers in front of the cloud edges should never get timeouts.  Your carrier should just send the calls and expect a reply.  Where is the timeout happening¹

I am struggling to remember what carriers use for heartbeat to understand if the four load balancer addresses are up and available. Timeouts of 5 seconds clearly aren't acceptable, so in the absence of OPTIONS, what else is there for them to use? 

We have a situation where SIP calls will not be sent without a response to OPTIONS.
Some workarounds aren't pretty, but potentially could be anything that causes a bad Call-ID. However, not sure if too many of those would send out alarms.

Robert,
The carrier in question requires a heartbeat reply or they do not send calls. They have never worked with a Cloud CX customer, though they have plenty of MultiCloud and Engage customers.  Their response was "Black holing SIP messages is non-conforming," and they are claiming that they have hard coded logic that prevents delivering any calls without a response.

So, no timeout as they can't deliver calls.

There is an Idea being voted on to add OPTIONS: TEL-I-244

In theory if you are talking about BYOC Cloud, the land balancers in front of the cloud edges should never get timeouts.  Your carrier should just send the calls and expect a reply.  Where is the timeout happening¹

I am struggling to remember what carriers use for heartbeat to understand if the four load balancer addresses are up and available. Timeouts of 5 seconds clearly aren't acceptable, so in the absence of OPTIONS, what else is there for them to use? 

We have a situation where SIP calls will not be sent without a response to OPTIONS.
Some workarounds aren't pretty, but potentially could be anything that causes a bad Call-ID. However, not sure if too many of those would send out alarms.

You might have to have an SBC in front of the GC trunk to get that.  Have you seen what this setting does?

Robert,
The carrier in question requires a heartbeat reply or they do not send calls. They have never worked with a Cloud CX customer, though they have plenty of MultiCloud and Engage customers.  Their response was "Black holing SIP messages is non-conforming," and they are claiming that they have hard coded logic that prevents delivering any calls without a response.

So, no timeout as they can't deliver calls.

There is an Idea being voted on to add OPTIONS: TEL-I-244

In theory if you are talking about BYOC Cloud, the land balancers in front of the cloud edges should never get timeouts.  Your carrier should just send the calls and expect a reply.  Where is the timeout happening¹

I am struggling to remember what carriers use for heartbeat to understand if the four load balancer addresses are up and available. Timeouts of 5 seconds clearly aren't acceptable, so in the absence of OPTIONS, what else is there for them to use? 

We have a situation where SIP calls will not be sent without a response to OPTIONS.
Some workarounds aren't pretty, but potentially could be anything that causes a bad Call-ID. However, not sure if too many of those would send out alarms.