topic Re: Broadworks - DUT sends Bye to internal ip instead of Outbound proxy ip in Cloud Calling

Broadworks - DUT sends Bye to internal ip instead of Outbound proxy ip

GuyPothiboon4406 — Tue, 24 Sep 2019 18:28:59 GMT

Hi Support team,

I am testing on Broadworks server with DevNet Sandbox.

Procedure:

- incoming Invite to DUT

- DUT answers the call

- DUT ends call

Problem:

- DUT sends Bye to internal ip 10.10.20.137 instead of outbound proxy ip 64.103.37.43

Analysis:

- I believe this is caused by the internal ip is presented in the Via header in incoming Invite (see attached capture)

Re: Broadworks - DUT sends Bye to internal ip instead of Outbound proxy ip

jaylefor — Tue, 24 Sep 2019 23:55:15 GMT

I will take a closer look and look at logs on the Application Server.

I thought the route header that was used by the clients; however, I do need to look closer at what is sent in the messages.

Re: Broadworks - DUT sends Bye to internal ip instead of Outbound proxy ip

jaylefor — Wed, 25 Sep 2019 17:06:12 GMT

Greetings,

We did attempt a few calls and the results are as expected.

Attached are logs from our Application Server and Edge (SSE/SBC).

Scenarios:

Attached are SSE and AS log.

Scenario 1: call 1

9736722151 calls 2152
9736722152 answers
9736722151 & 9736722152 are connected
9736722152 hangs up
9736722152 sends BYE to SSE
SSE sends BYE to AS
AS sends BYE to SSE
SSE sends BYE to 9736722151

Scenario 2: call 2

9736722151 calls 2152
9736722152 answers
9736722151 & 9736722151 are connected
9736722151 hangs up
9736722151 sends BYE to SSE
SSE sends BYE to AS
AS sends BYE to SSE
SSE sends BYE to 9736722152

Re: Broadworks - DUT sends Bye to internal ip instead of Outbound proxy ip

GuyPothiboon4406 — Wed, 25 Sep 2019 18:15:38 GMT

Hi,

In Scenario 1, my phone sends Bye to SSE @10.10.30.137 however this is an internal IP so the signal can never reach your server. I know it will be ok if the Bye is sent to Outbound Proxy.

I think this is due to the internal IP presented in Via header in incoming INVITE.

(Via:SIP/2.0/UDP 10.10.30.137:5683; branch=z9hG4bKBroadworksSSE.-206.108.192.124V60794-0-843233555-1422834453-1569349530148-)

Please see attached "Bye_OK.pcapng" that it the Outbound Proxy IP in Via header

(Via: SIP/2.0/UDP 192.65.79.250:5060;branch=z9hG4bK4b0feh2050elcrs56-)3.1

I have no problem in Scenario 2 because DUT is the calling party and when it ends call, it sends Bye to Outbound Proxy @ 64.103.37.43 directly.

Re: Broadworks - DUT sends Bye to internal ip instead of Outbound proxy ip

skumar1 — Wed, 25 Sep 2019 19:17:13 GMT

Could you let me know the ooutbound proxy server used for your testing? your logs states that : 192.65.79.250.

Re: Broadworks - DUT sends Bye to internal ip instead of Outbound proxy ip

jaylefor — Wed, 25 Sep 2019 19:36:27 GMT

Outbound proxy is: 64.103.37.43:5683

I attached another trace from the phones perspective. The phone is on a network where we are still experiencing blocked ports, but SIP should be OK.

I also asked our support contact to take a look and respond.

Re: Broadworks - DUT sends Bye to internal ip instead of Outbound proxy ip

GuyPothiboon4406 — Thu, 26 Sep 2019 21:43:59 GMT

attached another capture showing Yealink phone has the same issue

Re: Broadworks - DUT sends Bye to internal ip instead of Outbound proxy ip

jaylefor — Fri, 27 Sep 2019 18:34:07 GMT

An internal Cisco PR has been opened regarding the VIA having the internal/private IP. Feedback will be provided when available.

Re: Broadworks - DUT sends Bye to internal ip instead of Outbound proxy ip

GuyPothiboon4406 — Mon, 07 Oct 2019 18:52:04 GMT

Any update on this issue?

Re: Broadworks - DUT sends Bye to internal ip instead of Outbound proxy ip

SathiyaGeorge85053 — Tue, 08 Oct 2019 09:45:40 GMT

I am also facing the same issue.Bye sent to 10.10.30.137 ip instead of 64.103.37.43 due to via header in INVITE.Kindly check and resolve this issue ASAP.

Re: Broadworks - DUT sends Bye to internal ip instead of Outbound proxy ip

Kishore M — Wed, 09 Oct 2019 22:22:37 GMT

We do not have an estimate at this time. We will respond as soon as we hear from the team looking into the issue.