Re: Direct Routing for Microsoft Phone System with Cisco Unified Border Element

takahashi-ta · ‎02-23-2021

I am using vCUBE (on CSR1000v) to build direct routing for Microsoft Teams Phone System.
ITSP is using Twilio.
In this environment, I can make and receive outgoing calls from Microsoft Teams Client to Twlio direction, but the signaling is not working well from Twilio to Microsoft Teams Client direction.
I used TranslatorX to draw a SIP ladder sequence from the results of the debug ccsip messages and found that the CUBE is not receiving any response to the INVITE it sent to the Micorosoft Teams Phone System.

The TLS connection is normally working as shown below.

(ex)
Remote-Agent:52.114.76.76, Connections-Count:3
Remote-Port Conn-Id Conn-State WriteQ-Size Local-Address TLS-Version Cipher Curve
=========== ======= =========== =========== ============= =========== ============================== =====
5061 140 Established 0 x.x.x.x TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384 P-384
3521 142 Established 0 x.x.x.x TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384 P-256
3520 141 Established 0 x.x.x.x TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384 P-256

However, the moment I make a call from Twilio to the Micorosoft Teams Client, I get the following message.

%SIP-3-INTERNAL: Connection failed for addr=52.114.76.76, port=5061, connId=140

For some reason, the TCP TLS connection seems to be failing momentarily, and I suspect this is why the signaling is not working properly.

Is there any configuration I should review?

By the way, I am referring to the following document for setting up the CUBE.
https://www.cisco.com/c/dam/en/us/solutions/collateral/enterprise/interoperability-portal/direct-routing-with-cube.pdf

rchaseling · ‎03-26-2021

Did you get this resolved?

I'm seeing the same - my dialpeer is going up and down every minute or so even though SIP Options appears to be working fine

Mar 26 17:37:41.574 GMT: %SIP-3-INTERNAL: Connection failed for addr=52.114.76.76, port=5061, connId=38

Carl Ratcliffe · ‎03-26-2021

Hi, I have successfully setup CSR1000v CUBE for Teams Direct Routing following the same guide and have inbound and outbound calls connecting with no issues using this flow - Provider SIP > CUBE > CUCM > CUBE Direct Routing > Teams.

The message " Mar 26 17:37:41.574 GMT: %SIP-3-INTERNAL: Connection failed for addr=52.114.76.76, port=5061, connId=38" is possibly a red herring as I was also getting the same message all the time when connected to the CLI even when not making calls along with other IP addresses and it didn't seem to affect calls.

For reference i upgraded to the latest version and don't seem to get the error anymore - csr1000v-universalk9.17.03.03.SPA.bin

Thanks, Carl Ratcliffe

rchaseling · ‎03-27-2021

Thanks. 
I don't going its a red herring though as I see the socket close and the dialpeer goes down (options ping) so it might failover to other Microsoft IP and still work but this is not ideal for production.

It's strange cause I'm getting replies to options ping bug then the TLS socket just closes. 

I've copied the config and details from the "new" guide too.

I'll do some more testing and revert

Carl Ratcliffe · ‎03-28-2021

I actually have a transfer issue with Teams Direct Routing that I have posted on here however I think the troubleshooting I have done on that could be linked to your issue and maybe that IP is literally the "route" to all our problems. I don't know why yet but if you have any ideas it might be the fix for both issues.

As i mentioned Inbound / Outbound calls work no issue for me but when i request to transfer i receive the REFER then you get a really long wait time with nothing happening then the transfer will wither eventually complete ( 60 seconds plus end to end ) or fail.

When i say nothing happening the debug ccsip all and debug voip ccapi inout have nothing except responding to a few OPTIONS so this made me think is it the CUBE itself not the VoIP so first of all i took the easy way out and upgraded the IOS but it didn't fix my issue.

Next i went to the network/routing/firewall layer and all seemed fine so i took the final step of debug ip packet as i really needed to see what was happening between the REFER and the transfer seen as no voice messages were output and this is my findings.

The REFER message has this field and notice the IP - VIA: SIP/2.0/TLS 52.114.76.76:5061;branch=z9hG4bK24ece8b0

My debug IP Packet from the REFER to the next SIP Message is littered with these and 1.2.3.4 is my interface used to Teams.

Mar 28 09:00:33.341: FIBipv4-packet-proc: route packet from GigabitEthernet1 src 52.114.76.76 dst 1.2.3.4
Mar 28 09:00:33.341: FIBfwd-proc: EURODC1-CUBE-Outside:1.2.3.4/32 receive entry
Mar 28 09:00:33.341: FIBipv4-packet-proc: packet routing failed
Mar 28 09:00:33.341: IP: tableid=3, s=52.114.76.76 (GigabitEthernet1), d=1.2.3.4 (GigabitEthernet1) nexthop=1.2.3.4, routed via RIB

So the bottom line is it can't communicate with that IP hence my transfer delay and maybe the reason for your Failed Connection however i don't think its that simple as i can communicate with that IP and this is from the same trace which indicates i can communicate ( at least some of the time ).

Mar 28 09:00:26.168: //-1/xxxxxxxxxxxx/SIP/Transport/sip_tls_tcp_handshake_proc: TLS HANDSHAKE is successful with trunk peer 52.114.76.76

Thanks, Carl Ratcliffe

rchaseling · ‎03-29-2021

Hi,

Update my side (I haven't actually tsted any calls yet as waiting for Teams side to be configured)

I didn't have a DNS server avialable before so I had static host records configured on CUBE. I have since configured DNS servers and the dial-peer going up and down every minute has stopped.....but issue not completely resolved!!!

Rather than every minute it is not happening every hour..... nearly on the dot but dialpeer is not going down anymore

See screenshot of logging I've had running

Connection fails to 52.114.76.76 at 13:53 mins past the hour (but not every hour)

Connection fails to 52.114.132.46 at 02:26 past the hour (but not every hour)

Surely this is something on the microsft side but I guess could be CUBE or firewall also....

Carl Ratcliffe · ‎03-29-2021

I honestly don't know but I also thought it has to be the Microsoft side especially since you posted the same IP address but at the same time the CUBE is definitely doing something weird.

As I mentioned inbound/outbound calls setup perfectly every single time and I only get the issue with a transfer ( REFER ) so you would think that setup is the issue but the CUBE does just seem to stop processing VoIP traffic so it is either a CSR1000v issue or something it receives in the REFER it doesn't like ( even though it accepts it ) but then if that was the case you would still expect to see SIP messages. It's the same every time, REFER > ACCEPT then 25-30 seconds of zero SIP messages until it eventually decides to send the NOTIFY then it will either complete the transfer or just say cant complete.

I have a ticket logged with Microsoft so will see what they come back with. I also want to log with Cisco but as its a proof of concept i only used trial CSR1000v licenses so not sure if i can log anything yet.

Keep in touch as it will be interesting to see if you get the same issue with transfer.

Thanks, Carl Ratcliffe

rchaseling · ‎03-29-2021

So I'm deployed on a pair of 4331 configure in HA so if I have the same issue as you we'll know its not a CSR1000v issue

I should hopefully get to start getting test calls in/out of the coming days. I'll ket you know

Carl Ratcliffe · ‎03-29-2021

One thing I do now know is that it isn't just that IP address, at least for my issue.

I noticed that my home internet resolved to a different Microsoft Teams signaling address for sip.pstnhub.microsoft.com compared to my CUBE so i forced the CUBE to use this same DNS and it forced it to 52.114.7.24 but my issue still persists for transfers.

Carl Ratcliffe · ‎04-02-2021

Hi, did you mange to test any calls yet?

I still have a transfer issue and have tickets logged with both cisco and Microsoft but no solution yet.

Thanks, Carl Ratcliffe

rchaseling · ‎04-02-2021

Hi,

So basic calls are working but customer having problems getting my Teams account working so have not done any testing myself yet.

BUT I am still getting lots of disconnects that sometimes cause a dialpeer to go down. This could well be causing a problem if this was production. Have a look at logging for overnight last night! THis cannot be right! Is this similar to what you are seeing?

Carl Ratcliffe · ‎04-02-2021

Definitely something not right especially with them being at regular intervals.

Although not ideal, users may not notice any issue as they are signaling addresses not media so connected calls should not be affected and on the off chance it happened during call setup it should just use another dial-peer after a slight delay.

Not long after I wrote the previous update I got a fix / workaround for my call transfers issue and it was relating to this bug and the fix is to basically block REFER and force Microsoft to use re-INITE although Microsoft say this isn't possible or supported with Teams but it certainly works for me so if you do have issues with transfer try this.

In typical Microsoft / Cisco rivalry Cisco are quick to point out the issue is not the CUBE but I'm not sure if that is strictly true because just receiving that REFER seems to completely lock up voice services on the CUBE and I'm not sure Microsoft could be at fault with that.

" The race condition is on the peer device and not CUBE, which falls outside of the CUBE control. REFER/BYE scenarios like this are in accordance to RFC 5589."

https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvv13018/?rfs=iqvred

Thanks, Carl Ratcliffe

rchaseling · ‎04-06-2021

Very interesting and noted!

Just to finish this off - are you still seeing the same connection failure messages but everything is working fine?

Carl Ratcliffe · ‎04-06-2021

Yes I am and like yours there is a definite pattern.

I haven't noticed any issues but we are in proof of concept so only have limited users so that isn't to say it isn't causing an issue.

Apr 3 10:12:30.716: %SIP-3-INTERNAL: Connection failed for addr=52.114.75.24, port=6657, connId=841

Apr 3 10:34:45.817: %SIP-3-INTERNAL: Connection failed for addr=52.114.132.46, port=8512, connId=842

Apr 3 11:35:20.652: %SIP-3-INTERNAL: Connection failed for addr=52.114.7.24, port=1281, connId=843

Apr 3 12:12:30.716: %SIP-3-INTERNAL: Connection failed for addr=52.114.75.24, port=6656, connId=844

Apr 3 12:34:45.817: %SIP-3-INTERNAL: Connection failed for addr=52.114.132.46, port=8513, connId=845

Apr 3 13:35:20.652: %SIP-3-INTERNAL: Connection failed for addr=52.114.7.24, port=1280, connId=846

Apr 3 14:12:30.716: %SIP-3-INTERNAL: Connection failed for addr=52.114.75.24, port=6657, connId=847

Apr 3 14:34:45.817: %SIP-3-INTERNAL: Connection failed for addr=52.114.132.46, port=8512, connId=848

Apr 3 15:35:20.653: %SIP-3-INTERNAL: Connection failed for addr=52.114.7.24, port=1281, connId=849

Apr 3 16:12:30.716: %SIP-3-INTERNAL: Connection failed for addr=52.114.75.24, port=6656, connId=850

Apr 3 16:34:45.818: %SIP-3-INTERNAL: Connection failed for addr=52.114.132.46, port=8513, connId=851

Apr 3 17:35:20.654: %SIP-3-INTERNAL: Connection failed for addr=52.114.7.24, port=1280, connId=852

Apr 3 18:12:30.716: %SIP-3-INTERNAL: Connection failed for addr=52.114.75.24, port=6657, connId=853

Apr 3 18:34:45.818: %SIP-3-INTERNAL: Connection failed for addr=52.114.132.46, port=8512, connId=854

Apr 3 19:35:20.655: %SIP-3-INTERNAL: Connection failed for addr=52.114.7.24, port=1281, connId=855

Apr 3 20:12:30.716: %SIP-3-INTERNAL: Connection failed for addr=52.114.75.24, port=6656, connId=856

Apr 3 20:34:45.818: %SIP-3-INTERNAL: Connection failed for addr=52.114.132.46, port=8513, connId=857

Apr 3 21:35:20.655: %SIP-3-INTERNAL: Connection failed for addr=52.114.7.24, port=1280, connId=858

Apr 3 22:12:30.716: %SIP-3-INTERNAL: Connection failed for addr=52.114.75.24, port=6657, connId=859

Apr 3 22:34:45.819: %SIP-3-INTERNAL: Connection failed for addr=52.114.132.46, port=8512, connId=860

Apr 3 23:35:20.655: %SIP-3-INTERNAL: Connection failed for addr=52.114.7.24, port=1281, connId=861

Apr 4 00:12:30.716: %SIP-3-INTERNAL: Connection failed for addr=52.114.75.24, port=6656, connId=862

Apr 4 00:34:45.819: %SIP-3-INTERNAL: Connection failed for addr=52.114.132.46, port=8513, connId=863

Apr 4 01:35:20.655: %SIP-3-INTERNAL: Connection failed for addr=52.114.7.24, port=1280, connId=864

Apr 4 02:12:30.717: %SIP-3-INTERNAL: Connection failed for addr=52.114.75.24, port=6657, connId=865

Apr 4 02:34:45.819: %SIP-3-INTERNAL: Connection failed for addr=52.114.132.46, port=8512, connId=866

Apr 4 03:35:20.656: %SIP-3-INTERNAL: Connection failed for addr=52.114.7.24, port=1281, connId=867

Apr 4 04:12:30.717: %SIP-3-INTERNAL: Connection failed for addr=52.114.75.24, port=6656, connId=868

Apr 4 04:24:42.582: %SIP-3-INTERNAL: Connection failed for addr=52.114.75.24, port=6152, connId=342

Apr 4 04:25:22.550: %SIP-3-INTERNAL: Connection successful for addr=52.114.75.24, port=5061, connId=872

Apr 4 04:30:54.251: %SIP-3-INTERNAL: Connection failed for addr=52.114.7.24, port=5061, connId=400

Apr 4 04:31:38.009: %SIP-3-INTERNAL: Connection successful for addr=52.114.7.24, port=5061, connId=875

Apr 4 04:34:45.819: %SIP-3-INTERNAL: Connection failed for addr=52.114.132.46, port=8513, connId=869

Apr 4 04:37:38.400: %SIP-3-INTERNAL: Connection failed for addr=52.114.75.24, port=5061, connId=872

Apr 4 04:37:44.775: %SIP-3-INTERNAL: Connection successful for addr=52.114.75.24, port=5061, connId=879

Apr 4 04:47:03.040: %SIP-3-INTERNAL: Connection failed for addr=52.114.75.24, port=10368, connId=873

Apr 4 05:02:23.221: %SIP-3-INTERNAL: Connection failed for addr=52.114.7.24, port=1280, connId=870

Apr 4 05:18:02.927: %SIP-3-INTERNAL: Connection failed for addr=52.114.75.24, port=5061, connId=879

Apr 4 05:18:08.792: %SIP-3-INTERNAL: Connection successful for addr=52.114.75.24, port=5061, connId=882

Apr 4 05:24:41.082: %SIP-3-INTERNAL: Connection failed for addr=52.114.7.24, port=7168, connId=876

Apr 4 05:25:02.470: %SIP-3-INTERNAL: Connection successful for addr=52.114.7.24, port=5061, connId=885

Apr 4 05:33:44.678: %SIP-3-INTERNAL: Connection failed for addr=52.114.132.46, port=5061, connId=419

Apr 4 05:34:32.282: %SIP-3-INTERNAL: Connection successful for addr=52.114.132.46, port=5061, connId=888

Apr 4 05:45:27.002: %SIP-3-INTERNAL: Connection failed for addr=52.114.7.24, port=5061, connId=885

Apr 4 05:46:11.425: %SIP-3-INTERNAL: Connection successful for addr=52.114.7.24, port=5061, connId=891

Apr 4 05:46:33.253: %SIP-3-INTERNAL: Connection failed for addr=52.114.7.24, port=2304, connId=886

Apr 4 05:46:34.514: %SIP-3-INTERNAL: Connection failed for addr=52.114.7.24, port=2305, connId=887

Apr 4 06:05:31.219: %SIP-3-INTERNAL: Connection failed for addr=52.114.132.46, port=8256, connId=420

Apr 4 06:12:30.718: %SIP-3-INTERNAL: Connection failed for addr=52.114.75.24, port=7177, connId=881

Apr 4 06:27:37.756: %SIP-3-INTERNAL: Connection failed for addr=52.114.7.24, port=5061, connId=891

Apr 4 06:28:28.822: %SIP-3-INTERNAL: Connection successful for addr=52.114.7.24, port=5061, connId=894

Apr 4 06:40:30.312: %SIP-3-INTERNAL: Connection failed for addr=52.114.75.24, port=5061, connId=882

Apr 4 06:40:32.973: %SIP-3-INTERNAL: Connection successful for addr=52.114.75.24, port=5061, connId=897

Apr 4 06:48:01.366: %SIP-3-INTERNAL: Connection failed for addr=52.114.132.46, port=5061, connId=888

Apr 4 06:48:59.202: %SIP-3-INTERNAL: Connection successful for addr=52.114.132.46, port=5061, connId=898

Apr 4 07:12:30.718: %SIP-3-INTERNAL: Connection failed for addr=52.114.75.24, port=7176, connId=880

Apr 4 07:35:20.657: %SIP-3-INTERNAL: Connection failed for addr=52.114.7.24, port=1088, connId=892

Apr 4 07:39:30.338: %SIP-3-INTERNAL: Connection failed for addr=52.114.132.46, port=5061, connId=898

Apr 4 07:40:14.246: %SIP-3-INTERNAL: Connection successful for addr=52.114.132.46, port=5061, connId=903

Apr 4 08:34:45.819: %SIP-3-INTERNAL: Connection failed for addr=52.114.132.46, port=3201, connId=900

Apr 4 09:12:30.719: %SIP-3-INTERNAL: Connection failed for addr=52.114.75.24, port=1218, connId=901

Apr 4 09:34:45.820: %SIP-3-INTERNAL: Connection failed for addr=52.114.132.46, port=9793, connId=905

Apr 4 09:35:20.657: %SIP-3-INTERNAL: Connection failed for addr=52.114.7.24, port=5066, connId=902

Apr 4 11:12:30.719: %SIP-3-INTERNAL: Connection failed for addr=52.114.75.24, port=1024, connId=906

Apr 4 11:34:45.821: %SIP-3-INTERNAL: Connection failed for addr=52.114.132.46, port=1088, connId=907

Apr 4 11:35:20.657: %SIP-3-INTERNAL: Connection failed for addr=52.114.7.24, port=4416, connId=908

Apr 4 13:12:30.720: %SIP-3-INTERNAL: Connection failed for addr=52.114.75.24, port=1217, connId=909

Apr 4 13:34:45.822: %SIP-3-INTERNAL: Connection failed for addr=52.114.132.46, port=1089, connId=910

Apr 4 13:35:20.658: %SIP-3-INTERNAL: Connection failed for addr=52.114.7.24, port=4417, connId=911

Apr 4 15:12:30.720: %SIP-3-INTERNAL: Connection failed for addr=52.114.75.24, port=1344, connId=912

Apr 4 15:34:45.822: %SIP-3-INTERNAL: Connection failed for addr=52.114.132.46, port=1088, connId=913

Apr 4 15:35:20.658: %SIP-3-INTERNAL: Connection failed for addr=52.114.7.24, port=4416, connId=914

Apr 4 17:12:30.720: %SIP-3-INTERNAL: Connection failed for addr=52.114.75.24, port=1536, connId=915

Apr 4 17:34:45.822: %SIP-3-INTERNAL: Connection failed for addr=52.114.132.46, port=1089, connId=916

Apr 4 17:35:20.658: %SIP-3-INTERNAL: Connection failed for addr=52.114.7.24, port=4417, connId=917

Apr 4 19:12:30.720: %SIP-3-INTERNAL: Connection failed for addr=52.114.75.24, port=1537, connId=918

Apr 4 19:34:45.823: %SIP-3-INTERNAL: Connection failed for addr=52.114.132.46, port=1088, connId=919

Apr 4 19:35:20.658: %SIP-3-INTERNAL: Connection failed for addr=52.114.7.24, port=4416, connId=920

Apr 4 21:12:30.721: %SIP-3-INTERNAL: Connection failed for addr=52.114.75.24, port=1217, connId=921

Apr 4 21:34:45.823: %SIP-3-INTERNAL: Connection failed for addr=52.114.132.46, port=1089, connId=922

Apr 4 21:35:20.659: %SIP-3-INTERNAL: Connection failed for addr=52.114.7.24, port=4417, connId=923

Apr 4 23:12:30.721: %SIP-3-INTERNAL: Connection failed for addr=52.114.75.24, port=1218, connId=924

Apr 4 23:34:45.823: %SIP-3-INTERNAL: Connection failed for addr=52.114.132.46, port=1088, connId=925

Apr 4 23:35:20.660: %SIP-3-INTERNAL: Connection failed for addr=52.114.7.24, port=4416, connId=926

Apr 5 01:12:30.721: %SIP-3-INTERNAL: Connection failed for addr=52.114.75.24, port=1217, connId=927

Apr 5 01:34:45.823: %SIP-3-INTERNAL: Connection failed for addr=52.114.132.46, port=1089, connId=928

Apr 5 01:35:20.660: %SIP-3-INTERNAL: Connection failed for addr=52.114.7.24, port=4417, connId=929

Apr 5 03:12:30.721: %SIP-3-INTERNAL: Connection failed for addr=52.114.75.24, port=1218, connId=930

Apr 5 03:34:45.824: %SIP-3-INTERNAL: Connection failed for addr=52.114.132.46, port=1088, connId=931

Apr 5 03:35:20.660: %SIP-3-INTERNAL: Connection failed for addr=52.114.7.24, port=4416, connId=932

Apr 5 05:12:30.721: %SIP-3-INTERNAL: Connection failed for addr=52.114.75.24, port=1217, connId=933

Apr 5 05:34:45.825: %SIP-3-INTERNAL: Connection failed for addr=52.114.132.46, port=1089, connId=934

Apr 5 05:35:20.660: %SIP-3-INTERNAL: Connection failed for addr=52.114.7.24, port=4417, connId=935

Apr 5 07:12:30.721: %SIP-3-INTERNAL: Connection failed for addr=52.114.75.24, port=1218, connId=936

Apr 5 07:34:45.826: %SIP-3-INTERNAL: Connection failed for addr=52.114.132.46, port=1088, connId=937

Apr 5 07:35:20.660: %SIP-3-INTERNAL: Connection failed for addr=52.114.7.24, port=4416, connId=938

Apr 5 09:12:30.721: %SIP-3-INTERNAL: Connection failed for addr=52.114.75.24, port=1217, connId=939

Apr 5 09:34:45.826: %SIP-3-INTERNAL: Connection failed for addr=52.114.132.46, port=1089, connId=941

Apr 5 09:35:20.660: %SIP-3-INTERNAL: Connection failed for addr=52.114.7.24, port=4417, connId=940

Apr 5 11:12:30.722: %SIP-3-INTERNAL: Connection failed for addr=52.114.75.24, port=1344, connId=942

Apr 5 11:34:45.826: %SIP-3-INTERNAL: Connection failed for addr=52.114.132.46, port=1088, connId=943

Apr 5 11:35:20.660: %SIP-3-INTERNAL: Connection failed for addr=52.114.7.24, port=4416, connId=944

Apr 5 13:12:30.722: %SIP-3-INTERNAL: Connection failed for addr=52.114.75.24, port=1345, connId=945

Apr 5 13:34:45.826: %SIP-3-INTERNAL: Connection failed for addr=52.114.132.46, port=1089, connId=946

Apr 5 13:35:20.660: %SIP-3-INTERNAL: Connection failed for addr=52.114.7.24, port=4417, connId=947

Apr 5 15:12:30.722: %SIP-3-INTERNAL: Connection failed for addr=52.114.75.24, port=1344, connId=948

Apr 5 15:34:45.827: %SIP-3-INTERNAL: Connection failed for addr=52.114.132.46, port=1024, connId=949

Apr 5 15:35:20.660: %SIP-3-INTERNAL: Connection failed for addr=52.114.7.24, port=4416, connId=950

Apr 5 17:12:30.722: %SIP-3-INTERNAL: Connection failed for addr=52.114.75.24, port=1217, connId=951

Apr 5 17:34:45.828: %SIP-3-INTERNAL: Connection failed for addr=52.114.132.46, port=1025, connId=952

Apr 5 17:35:20.660: %SIP-3-INTERNAL: Connection failed for addr=52.114.7.24, port=4417, connId=953

Apr 5 19:12:30.723: %SIP-3-INTERNAL: Connection failed for addr=52.114.75.24, port=1218, connId=954

Apr 5 19:34:45.828: %SIP-3-INTERNAL: Connection failed for addr=52.114.132.46, port=1088, connId=955

Apr 5 19:35:20.660: %SIP-3-INTERNAL: Connection failed for addr=52.114.7.24, port=4416, connId=956

Apr 5 21:12:30.723: %SIP-3-INTERNAL: Connection failed for addr=52.114.75.24, port=1217, connId=957

Apr 5 21:34:45.828: %SIP-3-INTERNAL: Connection failed for addr=52.114.132.46, port=1089, connId=958

Apr 5 21:35:20.660: %SIP-3-INTERNAL: Connection failed for addr=52.114.7.24, port=4417, connId=959

Apr 5 23:12:30.723: %SIP-3-INTERNAL: Connection failed for addr=52.114.75.24, port=1218, connId=960

Apr 5 23:34:45.829: %SIP-3-INTERNAL: Connection failed for addr=52.114.132.46, port=1984, connId=961

Apr 5 23:35:20.661: %SIP-3-INTERNAL: Connection failed for addr=52.114.7.24, port=4416, connId=962

Apr 6 01:12:30.723: %SIP-3-INTERNAL: Connection failed for addr=52.114.75.24, port=1217, connId=963

Apr 6 01:34:45.830: %SIP-3-INTERNAL: Connection failed for addr=52.114.132.46, port=1024, connId=964

Apr 6 01:35:20.661: %SIP-3-INTERNAL: Connection failed for addr=52.114.7.24, port=4417, connId=965

Apr 6 03:12:30.724: %SIP-3-INTERNAL: Connection failed for addr=52.114.75.24, port=1218, connId=966

Apr 6 03:34:45.830: %SIP-3-INTERNAL: Connection failed for addr=52.114.132.46, port=1984, connId=967

Apr 6 03:35:20.661: %SIP-3-INTERNAL: Connection failed for addr=52.114.7.24, port=4672, connId=968

Apr 6 05:12:30.724: %SIP-3-INTERNAL: Connection failed for addr=52.114.75.24, port=1217, connId=969

Apr 6 05:34:45.830: %SIP-3-INTERNAL: Connection failed for addr=52.114.132.46, port=1985, connId=970

Apr 6 05:35:20.661: %SIP-3-INTERNAL: Connection failed for addr=52.114.7.24, port=4673, connId=971

Apr 6 07:12:30.724: %SIP-3-INTERNAL: Connection failed for addr=52.114.75.24, port=1218, connId=972

Apr 6 07:34:45.830: %SIP-3-INTERNAL: Connection failed for addr=52.114.132.46, port=1984, connId=973

Apr 6 07:35:20.661: %SIP-3-INTERNAL: Connection failed for addr=52.114.7.24, port=4672, connId=974

Scott Leport · ‎04-06-2021

Hey Guys,

Sorry to hijack this thread. Been following it with interest on and off lets say.

A few quick questions, just to see what "sticks":

1. Is your IP routing towards the MS Teams SIP proxies, media servers and the DNS servers from the guide going out the same path?

2. Do you have SIP ALG disabled on your upstream Firewalls or ALG disabled from your CUBE if it's the Internet gateway?

3. Is your SIP signalling and media both bound to the correct interfaces?

4. Random one, have either of you tried disabling CRL checking on the Baltimore cert? I had a weird issue where I couldn't get the trunk up between CUBE and Teams and that was the fix for me. May not be either of your issues here and to be honest, you'd probably see something in the logs regarding a CRL checking issue, but figured I'd ask!