Trouble registering a SIP Gateway

[Marc Z]

Troube registering a Gateway

Hi there,

I am trying to register a VOIP/ISDN gateway from Auerswald (actually, this device is manufactured by Tiptel) and I get a "407 Proxy Authentication Required" error.

The Gateway has been registered successfully on FreeCall so it seems to be ok. I can register OpenWengo on the local machine (the one that runs the 3CX server).

The 3CX server and the client gateway are connected through a simple local Ethernet switch and I seem to have deactivated all firewalls on the server.

Here are the Etherreal captures :

No. Time Source Destination Protocol Info
31 1.153645 192.168.0.4 192.168.0.11 SIP Request: REGISTER sip:192.168.0.11

Frame 31 (492 bytes on wire, 492 bytes captured)
Ethernet II, Src: Tiptel_60:01:bf (00:0c:c4:60:01:bf), Dst: Micro-St_68:fb:65 (00:0c:76:68:fb:65)
Internet Protocol, Src: 192.168.0.4 (192.168.0.4), Dst: 192.168.0.11 (192.168.0.11)
User Datagram Protocol, Src Port: 5060 (5060), Dst Port: 5060 (5060)
Session Initiation Protocol
Request-Line: REGISTER sip:192.168.0.11 SIP/2.0
Method: REGISTER
Resent Packet: False
Message Header
Via: SIP/2.0/UDP 0.0.0.0:0;branch=z9hG4bKd69bc69b369b269b
From: <sip:[email protected]>;tag=69c669c569c469bb
SIP from address: sip:[email protected]
SIP tag: 69c669c569c469bb
To: <sip:[email protected]>
SIP to address: sip:[email protected]
Call-ID: [email protected]
CSeq: 1 REGISTER
Contact: <sip:[email protected]:0>
Contact Binding: <sip:[email protected]:0>
Expires: 3600
User-Agent: Auerswald VoIP/ISDN Gateway Final Build 1.4.0
Max-Forwards: 70
Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,OPTIONS,INFO
Content-Length: 0

No. Time Source Destination Protocol Info
32 1.255922 192.168.0.11 192.168.0.4 SIP Status: 407 Proxy Authentication Required (0 bindings)

Frame 32 (488 bytes on wire, 488 bytes captured)
Ethernet II, Src: Micro-St_68:fb:65 (00:0c:76:68:fb:65), Dst: Tiptel_60:01:bf (00:0c:c4:60:01:bf)
Internet Protocol, Src: 192.168.0.11 (192.168.0.11), Dst: 192.168.0.4 (192.168.0.4)
User Datagram Protocol, Src Port: 5060 (5060), Dst Port: 5060 (5060)
Session Initiation Protocol
Status-Line: SIP/2.0 407 Proxy Authentication Required
Status-Code: 407
Resent Packet: False
Message Header
Via: SIP/2.0/UDP 0.0.0.0;branch=z9hG4bKd69bc69b369b269b;received=192.168.0.4;rport=5060
Proxy-Authenticate: Digest nonce="12836692853:1fa102b63934f156c04eb2f07414c9d4",algorithm=MD5,realm="3CXPhoneSystem"
Authentication Scheme: Digest
Nonce Value: "12836692853:1fa102b63934f156c04eb2f07414c9d4"
Algorithm: MD5
Realm: "3CXPhoneSystem"
To: <sip:[email protected]>;tag=ef156120
SIP to address: sip:[email protected]
SIP tag: ef156120
From: <sip:[email protected]>;tag=69c669c569c469bb
SIP from address: sip:[email protected]
SIP tag: 69c669c569c469bb
Call-ID: [email protected]
CSeq: 1 REGISTER
User-Agent: 3CXPhoneSystem
Content-Length: 0

Can someone help me understand ? I shall provide other info or Ethernet captures if necessary.

 

[Mirzab]

Any chance you can post logs from 3CX itself? I do better with those.

 

[LORD ORION]

Something in one of the authentication headers isn't right.

Usually your sip registration should look like this.

-> Register
<- Failed
-> Register with Credentials
<- Accepted or Failed

It's hard to tell without being able to look at the entire etheral capture, but it looks like it isn't responding to the initial challenge with credintial info?

In ethereal/wireshark look at "Statistics -> Flow Graph" to see if your endpoint responds to the initial fail message.

If it didn't respond, something in the ID settings didn't match as expected, so no challenge was issued. (usually realm setting or endpoint IP setting)

 

[Marc Z]

Thanks Mirzab and LORD ORION...

Regarding Etherreal, I can see no other interesting frames, but I shall register on an Internet VOIP provider, make other captures and compare..

Here is a 3CX log from 3CXPhoneSystem.trace.log :
192.168.0.4 is the Gateway
192.168.0.11 is the PC\Windows running 3CX

10:48:14.890|Transport.cxx(259)|Debug8|Resip|>>:incoming from: [ V4 192.168.0.4:5060 UDP target domain=unspecified received on: Transport: [ V4 0.0.0.0:5060 UDP target domain=unspecified connectionId=0 ] connectionId=0 ]
10:48:14.890|TransactionUser.cxx(66)|Debug8|Resip|>>:Checking if SipReq: REGISTER 192.168.0.11 tid=87f697f667f677f6 cseq=REGISTER [email protected] / 1 from(wire) is for me
10:48:14.890|TransactionUser.cxx(71)|Debug8|Resip|>>:Checking rule...
10:48:14.890|MessageFilterRule.cxx(42)|Debug8|Resip|>>:Matching rule for REGISTER sip:192.168.0.11 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.4:5060;branch=z9hG4bK87f697f667f677f6
Max-Forwards: 70
Contact: <sip:[email protected]>
To: <sip:[email protected]>
From: <sip:[email protected]>;tag=7f537f507f517f6e
Call-ID: [email protected]
CSeq: 1 REGISTER
Expires: 3600
Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, OPTIONS, INFO
User-Agent: Auerswald VoIP/ISDN Gateway Final Build 1.4.0
Content-Length: 0


10:48:14.890|TransactionUser.cxx(74)|Debug8|Resip|>>:Match!
10:48:14.890|TransactionState.cxx(1721)|Debug8|Resip|>>:Send to TU: TU: DialogUsageManager size=0 REGISTER sip:192.168.0.11 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.4:5060;branch=z9hG4bK87f697f667f677f6
Max-Forwards: 70
Contact: <sip:[email protected]>
To: <sip:[email protected]>
From: <sip:[email protected]>;tag=7f537f507f517f6e
Call-ID: [email protected]
CSeq: 1 REGISTER
Expires: 3600
Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, OPTIONS, INFO
User-Agent: Auerswald VoIP/ISDN Gateway Final Build 1.4.0
Content-Length: 0


10:48:14.890|.\Authorization.cpp(165)|Message5|Authorization|AuthMgr::handle:handle:
REGISTER sip:192.168.0.11 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.4:5060;branch=z9hG4bK87f697f667f677f6
Max-Forwards: 70
Contact: <sip:[email protected]>
To: <sip:[email protected]>
From: <sip:[email protected]>;tag=7f537f507f517f6e
Call-ID: [email protected]
CSeq: 1 REGISTER
Expires: 3600
Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, OPTIONS, INFO
User-Agent: Auerswald VoIP/ISDN Gateway Final Build 1.4.0
Content-Length: 0


10:48:14.906|Helper.cxx(302)|Debug8|Resip|>>:Helper::makeResponse(SipReq: REGISTER 192.168.0.11 tid=87f697f667f677f6 cseq=REGISTER [email protected] / 1 from(wire) code=407 reason=
10:48:14.906|ServerAuthManager.cxx(363)|Trace5|Resip|>>:Sending challenge to SipReq: REGISTER 192.168.0.11 tid=87f697f667f677f6 cseq=REGISTER [email protected] / 1 from(wire)
10:48:14.906|DialogUsageManager.cxx(800)|Debug8|Resip|>>:SEND: SIP/2.0 407 Proxy Authentication Required
Via: SIP/2.0/UDP 192.168.0.4:5060;branch=z9hG4bK87f697f667f677f6
Proxy-Authenticate: Digest nonce="12836738894:d239e7f759bcd2575b8c960a82e52bb5",algorithm=MD5,realm="3CXPhoneSystem"
To: <sip:[email protected]>;tag=1f489c1c
From: <sip:[email protected]>;tag=7f537f507f517f6e
Call-ID: [email protected]
CSeq: 1 REGISTER
User-Agent: 3CXPhoneSystem
Content-Length: 0


10:48:14.906|SipStack.cxx(278)|Debug8|Resip|>>:SEND: SipResp: 407 tid=87f697f667f677f6 cseq=REGISTER / 1 from(tu)
10:48:14.906|ServerAuthManager.cxx(41)|Trace5|Resip|>>:ServerAuth challenged request SipReq: REGISTER 192.168.0.11 tid=87f697f667f677f6 cseq=REGISTER [email protected] / 1 from(wire)
10:48:15.000|TimerQueue.cxx(85)|Debug8|Resip|>>:Adding timer: Timer J tid=87f697f667f677f6 ms=32000
10:48:15.000|TransportSelector.cxx(525)|Debug8|Resip|>>:Looked up source for destination: [ V4 192.168.0.4:5060 UDP target domain=unspecified received on: Transport: [ V4 0.0.0.0:5060 UDP target domain=unspecified connectionId=0 ] connectionId=0 ] -> [ V4 192.168.0.11:0 UDP target domain=unspecified received on: Transport: [ V4 0.0.0.0:5060 UDP target domain=unspecified connectionId=0 ] connectionId=0 ] sent-by=192.168.0.4 sent-port=5060
10:48:15.000|TransportSelector.cxx(766)|Debug8|Resip|>>:Transmitting to [ V4 192.168.0.4:5060 UDP target domain=unspecified received on: Transport: [ V4 0.0.0.0:5060 UDP target domain=unspecified connectionId=0 ] connectionId=0 ] tlsDomain= via [ V4 192.168.0.11:5060 UDP target domain=unspecified received on: Transport: [ V4 0.0.0.0:5060 UDP target domain=unspecified connectionId=0 ] connectionId=0 ]SIP/2.0 407 Proxy Authentication Required
Via: SIP/2.0/UDP 192.168.0.4:5060;branch=z9hG4bK87f697f667f677f6
Proxy-Authenticate: Digest nonce="12836738894:d239e7f759bcd2575b8c960a82e52bb5",algorithm=MD5,realm="3CXPhoneSystem"
To: <sip:[email protected]>;tag=1f489c1c
From: <sip:[email protected]>;tag=7f537f507f517f6e
Call-ID: [email protected]
CSeq: 1 REGISTER
User-Agent: 3CXPhoneSystem
Content-Length: 0


10:48:15.000|Transport.cxx(209)|Debug8|Resip|>>:Adding message to tx buffer to: [ V4 192.168.0.4:5060 UDP target domain=unspecified received on: Transport: [ V4 0.0.0.0:5060 UDP target domain=unspecified connectionId=0 ] connectionId=0 ]
10:48:51.093|TuSelector.cxx(70)|Trace5|Resip|>>:Stats message

 

[Arnaud]

Hi, did you ever managed to get this to work ? I'm facing the same challenge. Also bought a VOIP Gateway from Auerswald, to connect my public BRI as PSTN to the 3CX PBX, but am unable to get the device to properly register.
I could start capturing some logs to publish, but was first of all interested if someone got this to work in the first place, and if so, please share some configuration tips.
Thanks,
Arnaud

 

[Marc Z]

Hi, did you ever managed to get this to work ?

No, I did'nt :cry:
Actually I posted the logs above, hoping someone would have a clue about it.

As 3CX usage was just for test purposes, I bypassed that test and the Auerswald adapter has been cut into service for one week, in conjunction with a SIP Telco (Free Telecom).

It seems that sometime it logs on to the SIP server, sometimes not (but if the "authentification" field is altered, it seems to log again). As I am not there to monitor the adaptater, I have no more information at the moment (the PBX is configured so that calls are routed transparently). I will take care of it again mid-december.

 

[gold_god]

I have the same problem with tiptel 40 VoIP (lastest firmware 1.4.3) trying to connect to 3CX Free Server 5.1.4128.0.

After having analysed tiptel's trace log and 3CX trace log, I found what was the problem but I still have no solution to fix it :
tiptel 40 VoIP tries first to connect without authentification and if the server's respons is "401 Unauthorized", tiptel will then try to authenticate.

The point is 3CX Server sends SIP response "407 Proxy Authentication Required" but tiptel does not ricognize that code.

I have just send an email to tiptel support this morning.

May be 3CX's developers team could add a "compatibility mode" which replaces 407 error code by 401 error code...