Call Rejected to Local Client - Same SIP Trunk Provider (407 Proxy Authentication Required) 1

[dsm600rr]

Hello all,

So we have an IPO on R11.1 SP1 with a NexVortex SIP Trunk

Our client has on IPO R11.0 with a NexVortex SIP Trunk.

This could be a coincidence however we have defiantly called this client before. The only change that has been made is updating our in-house IPO to R11.1 SP1.

I ran a monitor trance on the call. few things that stuck out:

08:03:15 66788570mS SIP Rx: UDP 104.219.XXX.XXX:5060 -> 192.168.1.251:5060
[highlight #FCE94F]SIP/2.0 407 Proxy Authentication Required[/highlight]
Via: SIP/2.0/UDP 173.162.XXX.XXX:5060;received=173.162.XXX.XXX;rport=5060;branch=z9hG4bK4e56f59d1c389cd6b82d235b16f68e19
From: "586961XXXX" <sip:586961XXXX@px1.nexvortex.com>;tag=3c291e7c3d4ee6c4
To: <sip:248380XXXX@px1.nexvortex.com>;tag=134e05171e7c22f4d450ef7f18a602bc.a12c
Call-ID: 4dfbb7e52c929a5841e4cb449e55be5d
CSeq: 1544032059 INVITE
Proxy-Authenticate: Digest realm="nexvortex.com", nonce="X+x7v1/sepMXiKjdbtDyiwSNVuuPMHx9"
Content-Length: 0


ACSS

 

[G van Hamburg]

That message only states you need to authenticate to the provider. See the line: Proxy-Authenticate: Digest realm="nexvortex.com", nonce="X+x7v1/sepMXiKjdbtDyiwSNVuuPMHx9”
So after this, the IPO should send a new invite with the authentication parameters. This is normal behaviour, if applicable to your situation of course. I’d look for the issue is other (later) SIP messages.

Freelance Certified Avaya Aura Engineer

 

[dsm600rr]

Found out the issue. NexVortex made a mistake and the numbers were in partial port status.

ACSS