Issue with inbound calls on new vCUBE

[campbech1]

I'm attempting to replace our on-prem CUBE with a vCUBE in Azure and running into some issues.

Outbound calls are working well but inbound calls are ringing internal phones, but then instantly drop. I know I'm missing something simple, but I'm struggling to find it.

Attaching some logs hoping this is a quick fix.

[Roger Kallberg]

If the call instantly drops at answer it is very likely an issue with codec. Make sure that your calls are using the intended dial peer(s) so that it is not using the default always present dreadful dial peer 0 as that will cause you to age prematurely. Joke aside, you should always make sure that this dial peer is not used as it would cause you issues.

[b.winter]

Hi,

on the initial incoming INVITE, the CUBE responds with "100 Trying".

After this "100 Trying", the CUBE with multiple "180 Ringing".

In the "180 Ringing", the CUBE says, that I must receive a PRACK (SIP header "Require: 100rel")

But the external side isn't answering this Ringing messages with a 200 OK.

After 3 seconds, the external side cancels the call, probably because of an internal timer, where there is no "200 OK" back from CUBE to external side. (Have seen this with different providers)

CUBE isn't sending the "200 OK" to external, because it hasn't received the "200 OK" from CUCM yet.

For the PRACK problem, you could try the following towards the external side:

Either disable PRACK completely (command "rel1xx disable")

or set it to default with the command "no rel1xx require 100rel"

For the timeout problem:

Check the CUCM logs, why it doesn't connect the call.

The problem may also be the called endpoint.