Unified Communications
Hello
Can anyone help me, please?
I cannot register standard SIP intercom Loxone to MyPBX.
Thank you very much
Date
Votes
9 comments
-
Oscar Colka There are kinds of reasons that a SIP device can't register to a SIP server:
1. Password or account incorrect;
2. SIP host or SIP port was not configured correctly;
3. PBX and SIP device are not int the same local network;
Please check above and if still no luck, please try capture some SIP packets on both MyPBX and the SIP intercom device then post the packets here.
-
JosefVachta Hello
It is in the same local network. The problem is that we cannot register that, the PBX has the problem to receive the name and the password.
Thanks
-
Oscar Colka Josef, If you ping from the PBX to the SIP intercom device, are you able to get ping response?
Can you get some SIP logs on both the S series PBX and the SIP intercom device?
-
-
JosefVachta I also tried to connect intercom directly to sip.antisip.com and it was working.
-
Oscar Colka Josef,
Can you try get the SIP pcap logs on the SIP intercom and the SIP pcap logs on the PBX?
See below screenshot of the page to capture pcap logs for S PBX:
-
JosefVachta Ôòˇ ˙˙ q `[ćXeî ¤ ¤ tř`B: E ” Ş €°öŔ¨bŔ¨ÄÄ€żQREGISTER sip:192.168.3.6 SIP/2.0
Via: SIP/2.0/UDP 192.168.3.98:5060;branch=z9hG4bKQmkomsuI4GYySge80;rport
From: "Branka" <sip:30@192.168.3.6>;tag=1AMa6QigaUwEYyOi
To: "Branka" <sip:30@192.168.3.6>
Call-ID: 8WuAQiigg6WuEWoy@192.168.3.98
CSeq: 28 REGISTER
Contact: <sip:30@192.168.3.98:5060>
Expires: 60
Max-Forwards: 70
User-Agent: BSIP 0.63.035
Content-Length: 0`[ćXŇú ) ) ôµIđÄĎ E`¦Ü@ @ ßŔ¨Ŕ¨bÄÄťuSIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.3.98:5060;rport=5060;received=192.168.3.98;branch=z9hG4bKQmkomsuI4GYySge80
Call-ID: 8WuAQiigg6WuEWoy@192.168.3.98
From: "Branka" <sip:30@192.168.3.6>;tag=1AMa6QigaUwEYyOi
To: "Branka" <sip:30@192.168.3.6>;tag=z9hG4bKQmkomsuI4GYySge80
CSeq: 28 REGISTER
WWW-Authenticate: Digest realm="YSAsterisk",nonce="1491491680/952ad36cd76b99db838c5a4c3666a2ce",opaque="7388056b7baf3f6f",algorithm=md5,qop="auth"
Server: Yeastar S50-30.4.0.6
Content-Length: 0`[ćX= Ž Ž tř`B: E ~ Ż €°Ŕ¨bŔ¨ÄÄjîŕREGISTER sip:192.168.3.6 SIP/2.0
Via: SIP/2.0/UDP 192.168.3.98:5060;branch=z9hG4bKXyOeebYEYsCUqyMa2;rport
From: "Branka" <sip:30@192.168.3.6>;tag=1AMa6QigaUwEYyOi
To: "Branka" <sip:30@192.168.3.6>
Call-ID: 8WuAQiigg6WuEWoy@192.168.3.98
CSeq: 29 REGISTER
Contact: <sip:30@192.168.3.98:5060>
Expires: 60
Max-Forwards: 70
User-Agent: BSIP 0.63.035
Authorization: Digest username="30",nonce="1491491680/952ad36cd76b99db838c5a4c3666a2ce",uri="sip:192.168.3.6",qop=auth,nc=00000001,cnonce="0a4f113b",opaque="7388056b7baf3f6f",algorithm=MD5,response="c982c362ad179b36e1da7e4c879282f9"
Content-Length: 0`[ćXľ$ ) ) ôµIđÄĎ E`§@ @ ¬Ŕ¨Ŕ¨bÄÄHSIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.3.98:5060;rport=5060;received=192.168.3.98;branch=z9hG4bKXyOeebYEYsCUqyMa2
Call-ID: 8WuAQiigg6WuEWoy@192.168.3.98
From: "Branka" <sip:30@192.168.3.6>;tag=1AMa6QigaUwEYyOi
To: "Branka" <sip:30@192.168.3.6>;tag=z9hG4bKXyOeebYEYsCUqyMa2
CSeq: 29 REGISTER
WWW-Authenticate: Digest realm="YSAsterisk",nonce="1491491680/952ad36cd76b99db838c5a4c3666a2ce",opaque="4f3961f25a66628c",algorithm=md5,qop="auth"
Server: Yeastar S50-30.4.0.6
Content-Length: 0`[ćXV Ž Ž tř`B: E ~ ˛ €°Ŕ¨bŔ¨ÄÄj•OREGISTER sip:192.168.3.6 SIP/2.0
Via: SIP/2.0/UDP 192.168.3.98:5060;branch=z9hG4bKb6Mg8WAQc6SswI2Mc;rport
From: "Branka" <sip:30@192.168.3.6>;tag=1AMa6QigaUwEYyOi
To: "Branka" <sip:30@192.168.3.6>
Call-ID: 8WuAQiigg6WuEWoy@192.168.3.98
CSeq: 30 REGISTER
Contact: <sip:30@192.168.3.98:5060>
Expires: 60
Max-Forwards: 70
User-Agent: BSIP 0.63.035
Authorization: Digest username="30",nonce="1491491680/952ad36cd76b99db838c5a4c3666a2ce",uri="sip:192.168.3.6",qop=auth,nc=00000001,cnonce="0a4f113b",opaque="4f3961f25a66628c",algorithm=MD5,response="c982c362ad179b36e1da7e4c879282f9"
Content-Length: 0 -
Oscar Colka Josef,
This looks like:
1. The PBX don't understand the authorization information sent from SIP intercom device to the PBX; - A compatibility issue between the SIP intercom and the PBX;
2. The SIP intercom was not configured with correct password - Please try using a soft phone to register the same extension and see if you can register successfully;
-
Oscar Colka I think the problem is probably the password incorrect, I try to register the Zoiper softphone in my office with incorrect password and I got similar SIP logs.
Do you use Registration password in the extension page? If not, please try use Registration password and try again.
Please sign in to leave a comment.