407 Proxy Authentication

[DadoD]

Hi,
Please, can someone explain whay the second invite listed below require authorisation and the first one don't.

1.
Session Initiation Protocol (INVITE)
Request-Line: INVITE sip:[email protected] SIP/2.0
Method: INVITE
Request-URI: sip:[email protected]
[Resent Packet: False]
Message Header
Record-Route: <sip:172.17.19.13:5060;lr>
Via: SIP/2.0/UDP 172.17.19.13:5060;branch=z9hG4bKhqdpfshwlln085bh-1gd
Via: SIP/2.0/UDP 10.40.0.2:5060;branch=z9hG4bK1396499474
From: "EAS 114" <sip:[email protected]>;tag=ewen0g68
To: "MOS PBX station" <sip:[email protected]>
Call-ID: [email protected]
[Generated Call-ID: [email protected]]
CSeq: 49759 INVITE
Sequence Number: 49759
Method: INVITE
Contact: <sip:[email protected]>
Max-Forwards: 69
User-Agent: AlphaSip gateway / 0161
X-Detect: Request=CPT,PTT
Subject: Forwarding AlphaCom call
Expires: 120
Allow: INVITE, REGISTER, ACK, BYE, CANCEL, INFO
Content-Type: application/sdp
Content-Length: 140
Message Body
Session Description Protocol
Session Description Protocol Version (v): 0
Owner/Creator, Session Id (o): 4114 20000001 20000001 IN IP4 172.17.19.13
Session Name (s): call
Connection Information (c): IN IP4 172.17.19.13
Time Description, active time (t): 0 0
Media Description, name and address (m): audio 61002 RTP/AVP 0
Media Attribute (a): rtpmap:0 PCMU/8000
Media Attribute (a):
[Generated Call-ID: [email protected]]
[Generated Call-ID: [email protected]]

2.
Session Initiation Protocol (INVITE)
Request-Line: INVITE sip:[email protected] SIP/2.0
Method: INVITE
Request-URI: sip:[email protected]
[Resent Packet: False]
Message Header
Record-Route: <sip:172.17.19.13:5060;lr>
Via: SIP/2.0/UDP 172.17.19.13:5060;branch=z9hG4bK7-ooi7mg2mjyr9h7bwa6
Via: SIP/2.0/UDP 172.17.19.13:6150;rport=6150;branch=z9hG4bKa2yqgrto-niud7l5ye5u
Contact: <sip:[email protected]>
To: <sip:[email protected]>
From: <sip:[email protected]>;tag=dzmr8ed4
Call-ID: BEJoRFVLMdlwFigVMAkxhZhiLMksSpWPGhKXAsmG
[Generated Call-ID: BEJoRFVLMdlwFigVMAkxhZhiLMksSpWPGhKXAsmG]
Allow: INVITE, ACK, CANCEL, BYE, INFO, NOTIFY
Max-Forwards: 69
CSeq: 511 INVITE
User-Agent: Telegra SIP phone
Content-Type: application/sdp
Content-Length: 162
Message Body
Session Description Protocol
Session Description Protocol Version (v): 0
Owner/Creator, Session Id (o): - 1587720240 1587720240 IN IP4 172.17.19.13
Session Name (s): Telegra SIP agent
Connection Information (c): IN IP4 172.17.19.13
Time Description, active time (t): 0 0
Media Description, name and address (m): audio 61002 RTP/AVP 0
Media Attribute (a): rtpmap:0 PCMU/8000
Media Attribute (a): sendrecv
[Generated Call-ID: dX2h4yfZsjWa2vRuS0J2kQ..]

 

[JohnS_3CX]

Hi,

This is standard procedure, the device is getting a challenge request to authenticate.

 

[DadoD]

Thank you for your response.
Im getting challenge only for the second invite, first one is connecting without challenge response. Is there any reason why first invite is treated differently?

 

[cobaltit]

Well the invites aren't identical. You have different devices taking different routes so this isn't apples to apples. And where is 3CX in this?

 

[DadoD]

Yes i agree with you , invites are't identical, my question is why one getting 407 and the otherone don't?
3CX is 172.17.19.15.

 

[DadoD]

Is there any way to disable proxy authorisation?

 

[YiannisH_3CX]

Yes i agree with you , invites are't identical, my question is why one getting 407 and the otherone don't?
3CX is 172.17.19.15.

That depends on how the device that sends the invite to 3CX registers to 3CX. If for example one of devices connects to the PBX using only its IP then the PBX will not request for authentication. If the device registers to the PBX using a username and password then the PBX will most likely request authentication.
Authentication is not something you can disable and it is a fundamental function of SIP. If your device cannot handle this correctly then i would advice you to change the device.