SIP trunk between Unify Openscape 4000 V8 and Avaya

Omenas · Nov 4, 2020

I'm having trouble with the SIP trunk between Openscape 4000 V8 and Avaya. At first, everything works fine, but after a few days something happens in the SIP. We can call from Avaya to Unify, but from Unify to Avaya - not. After the HG Gateway reset, everything is fine again.
After making the HG trace, I found the following message:

(SIP_SA 05 0x49be "11/04/2020 12: 21: 38.248661" CSipPacketLog.cpp 235)
>> IN << from 193.219.14.105:
SIP / 2.0 403 Forbidden (Unknown Far-End)
From: "LA LA LA" <sip: +111111111@172.16.10.15; user = phone>; tag = b4a7d6e7c3
To: <sip: 713@193.219.14.105>; tag = 0c8b117ab30eb1c1e5dbaeaa900
Call-ID: 118a90a847db6962
CSeq: 1326672853 INVITE
Via: SIP / 2.

(SIP_SA 05 0x49be "11/04/2020 12: 21: 38.249007" CSipPacketLog.cpp 235)
>> IN << from 193.219.14.105:
0 / TCP 172.16.10.15; alias; branch = z9hG4bKa13dc80cc7a157846
Server: Avaya CM / R015x.02.1.016.4
Content-Length: 0

(SIP_SA 05 0x49be "11/04/2020 12: 21: 38.249318" CSipPacketLog.cpp 336)
TMT <<
193.219.14.105:118a90a847db6962:SRC_STATE,
SSA: 118a90a847db6962: DEST_STATE
-Forbidden (Unknown Far-End) to INVITE (1531)
MsgID: Forbidden (Unknown Far-End) to INVITE (0X800258), SubID: 0, ParamCount: 0, ReturnCode: 0
TMT >>

Where to look for problems - Unify or Avaya side?

thepfy · Nov 5, 2020

Could you post examples of working and non working traces?

Can see 193.219.14.105 is rejecting the call as it doesn't see believe it is a trunk endpoint.
Is the STMI card up to date?

Are you using the Avaya Profile in the Unify card or just a generic one?
What is the Avaya system? Is it a rebadged Nortel?

Omenas · Nov 5, 2020

Trace done when it didn’t work.

This is a virtual vHG board

I use SIP trunk profile "NatTrkWithoutRegistration"
I am using the SIP trunk profile NatTrkWithoutRegistration because I did not find a profile named Avaya.
The customer has not yet answered me what kind of Avaya system they have.

Omenas · Nov 5, 2020

I got information about Avaya: Avaya Aura Communication Manager (CM), Releases 5.0

thepfy · Nov 5, 2020

It will be easier to troubleshoot by comparing working and non-working call traces.

thepfy · Nov 5, 2020

This is an older Avaya Doc for Hipath 4000 v5 SIP, but it should help.
Avaya documentation is pretty good for the configuration on both sides.

https://www.devconnectprogram.com/fileMedia/download/3736caec-0a79-4b0b-b125-1efda762ac7f

Omenas · Nov 6, 2020

Ok. here is a full trace of a bad call:

https://files.engineering.com/getfi...file=172.16.10.15-gw-2020-11-04-trace-bad.log

And here’s the good, the same when everything works:

https://files.engineering.com/getfi...ile=172.16.10.15-gw-2020-11-04-trace-good.log

I have already read that documentation. As I mentioned, I don't have an Avaya profile in my choices. Also, I didn't check "specify port" in the proxy settings, but left it by default. And everything else looks the same as in the documentation. Yesterday, I also sent this documentation to the Avaya administrator to check the Avaya settings

Moriendi · Nov 6, 2020

This looks like an issue with the Avaya. From the gateway logs the outgoing invites are identical apart from the origin/session info, which is normal. It's interesting that an STMI reset solves it, because the STMI won't be registering to the Avaya. So what changes? A different TCP session? I would pursue this on the Avaya side, not 4K, make them tell you what's wrong. Maybe changing to UDP might help but I'd still push Avaya for the solution.

Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

SIP trunk between Unify Openscape 4000 V8 and Avaya

Omenas

Systems Engineer

thepfy

IS-IT--Management

Omenas

Systems Engineer

Omenas

Systems Engineer

thepfy

IS-IT--Management

thepfy

IS-IT--Management

Omenas

Systems Engineer

Moriendi

Technical User

Similar threads

Part and Inventory Search

Sponsor