SIP Registration Failure - 484 Address Incomplete

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

SIP Registration Failure - 484 Address Incomplete

Mark Holloway
I have OpenSIPS 1.6.4 configured as a SIP Registrar with mysql. It is configured to challenge SIP registrations with authentication.  Keeping it simple, I've used opensipsctl to add user 1000 with password 1000 and set the IP/SIP Domain of OpenSIPS is 192.168.1.20. I am attempting to register using Counterpath Bria 3.1 (Mac).  Bria sends the initial registration to OpenSIPS and it properly responds with a 401 Unauthorized, but after Bria responds to the 401 challenge OpenSIPS responds with 484 Address Incomplete.

Looking at the docs I noticed OpenSIPS will send 484 if the username is not in the Request-Line. For example, OpenSIPS wants 1000@192.168.1.20 but Bria sends 192.168.1.20. The way Bria registers, the username portion (1000 in this case) is only in the Contact, To, and From headers. The R-URI line does not include the username portion.  Has anyone else encountered this?


==
Bria's response to 401 challenge
==

Session Initiation Protocol
    Request-Line: REGISTER <a href="sip:192.168.1.20">sip:192.168.1.20 SIP/2.0
        Method: REGISTER
        [Resent Packet: False]


       Contact: <<a href="sip:1000@192.168.1.116:62018;rinstance=3b31a8f560e5c3bc;transport=udp">sip:1000@192.168.1.116:62018;rinstance=3b31a8f560e5c3bc;transport=udp>
            Contact Binding: <<a href="sip:1000@192.168.1.116:62018;rinstance=3b31a8f560e5c3bc;transport=udp">sip:1000@192.168.1.116:62018;rinstance=3b31a8f560e5c3bc;transport=udp>
        To: "Mark"<<a href="sip:1000@192.168.1.20">sip:1000@192.168.1.20>
            SIP Display info: "Mark"
            SIP to address: <a href="sip:1000@192.168.1.20">sip:1000@192.168.1.20
        From: "Mark"<<a href="sip:1000@192.168.1.20">sip:1000@192.168.1.20>;tag=fbaf644d
            SIP Display info: "Mark"
            SIP from address: <a href="sip:1000@192.168.1.20">sip:1000@192.168.1.20
            SIP tag: fbaf644d



_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: SIP Registration Failure - 484 Address Incomplete

Mark Holloway
I resolved it.  Forgot to uncomment one very important part of the cfg file.

if (!save("location"))
			sl_reply_error();

		exit;
	}


On Jul 3, 2011, at 11:31 AM, Mark Holloway wrote:

I have OpenSIPS 1.6.4 configured as a SIP Registrar with mysql. It is configured to challenge SIP registrations with authentication.  Keeping it simple, I've used opensipsctl to add user 1000 with password 1000 and set the IP/SIP Domain of OpenSIPS is 192.168.1.20. I am attempting to register using Counterpath Bria 3.1 (Mac).  Bria sends the initial registration to OpenSIPS and it properly responds with a 401 Unauthorized, but after Bria responds to the 401 challenge OpenSIPS responds with 484 Address Incomplete.

Looking at the docs I noticed OpenSIPS will send 484 if the username is not in the Request-Line. For example, OpenSIPS wants 1000@192.168.1.20 but Bria sends 192.168.1.20. The way Bria registers, the username portion (1000 in this case) is only in the Contact, To, and From headers. The R-URI line does not include the username portion.  Has anyone else encountered this?


==
Bria's response to 401 challenge
==

Session Initiation Protocol
    Request-Line: REGISTER <a href="sip:192.168.1.20">sip:192.168.1.20 SIP/2.0
        Method: REGISTER
        [Resent Packet: False]


       Contact: <<a href="sip:1000@192.168.1.116:62018;rinstance=3b31a8f560e5c3bc;transport=udp">sip:1000@192.168.1.116:62018;rinstance=3b31a8f560e5c3bc;transport=udp>
            Contact Binding: <<a href="sip:1000@192.168.1.116:62018;rinstance=3b31a8f560e5c3bc;transport=udp">sip:1000@192.168.1.116:62018;rinstance=3b31a8f560e5c3bc;transport=udp>
        To: "Mark"<<a href="sip:1000@192.168.1.20">sip:1000@192.168.1.20>
            SIP Display info: "Mark"
            SIP to address: <a href="sip:1000@192.168.1.20">sip:1000@192.168.1.20
        From: "Mark"<<a href="sip:1000@192.168.1.20">sip:1000@192.168.1.20>;tag=fbaf644d
            SIP Display info: "Mark"
            SIP from address: <a href="sip:1000@192.168.1.20">sip:1000@192.168.1.20
            SIP tag: fbaf644d


_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: SIP Registration Failure - 484 Address Incomplete

Mark Holloway
Odd, even though I now get 200 OK from OpenSIPS after registering I still receive 484 Address Incomplete after the 200 OK even though the endpoint is registered. 


On Jul 3, 2011, at 11:35 AM, Mark Holloway wrote:

I resolved it.  Forgot to uncomment one very important part of the cfg file.

if (!save("location"))
			sl_reply_error();

		exit;
	}


On Jul 3, 2011, at 11:31 AM, Mark Holloway wrote:

I have OpenSIPS 1.6.4 configured as a SIP Registrar with mysql. It is configured to challenge SIP registrations with authentication.  Keeping it simple, I've used opensipsctl to add user 1000 with password 1000 and set the IP/SIP Domain of OpenSIPS is 192.168.1.20. I am attempting to register using Counterpath Bria 3.1 (Mac).  Bria sends the initial registration to OpenSIPS and it properly responds with a 401 Unauthorized, but after Bria responds to the 401 challenge OpenSIPS responds with 484 Address Incomplete.

Looking at the docs I noticed OpenSIPS will send 484 if the username is not in the Request-Line. For example, OpenSIPS wants 1000@192.168.1.20 but Bria sends 192.168.1.20. The way Bria registers, the username portion (1000 in this case) is only in the Contact, To, and From headers. The R-URI line does not include the username portion.  Has anyone else encountered this?


==
Bria's response to 401 challenge
==

Session Initiation Protocol
    Request-Line: REGISTER <a href="sip:192.168.1.20">sip:192.168.1.20 SIP/2.0
        Method: REGISTER
        [Resent Packet: False]


       Contact: <<a href="sip:1000@192.168.1.116:62018;rinstance=3b31a8f560e5c3bc;transport=udp">sip:1000@192.168.1.116:62018;rinstance=3b31a8f560e5c3bc;transport=udp>
            Contact Binding: <<a href="sip:1000@192.168.1.116:62018;rinstance=3b31a8f560e5c3bc;transport=udp">sip:1000@192.168.1.116:62018;rinstance=3b31a8f560e5c3bc;transport=udp>
        To: "Mark"<<a href="sip:1000@192.168.1.20">sip:1000@192.168.1.20>
            SIP Display info: "Mark"
            SIP to address: <a href="sip:1000@192.168.1.20">sip:1000@192.168.1.20
        From: "Mark"<<a href="sip:1000@192.168.1.20">sip:1000@192.168.1.20>;tag=fbaf644d
            SIP Display info: "Mark"
            SIP from address: <a href="sip:1000@192.168.1.20">sip:1000@192.168.1.20
            SIP tag: fbaf644d


_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
bll
Reply | Threaded
Open this post in threaded view
|

Re: SIP Registration Failure - 484 Address Incomplete

bll
Hi,

We also use Bria as SIP client and OpenSIPs and works very well together, so if you see errors like registering or so on, that is on your side.
Possible problems:
1. Bria incorrect settings, for Presence set Presence Agent (not peer2peer)
2. Incorrect script in opensips.cfg


We started few month ago from the ground to build a NAT traversal solution and I can list here few resources will help you pass the beginners problems: 
    Will help you to solve: basic script for REGISTER/PUBLISH/NOTIFY, MySQL authorization, far-end NAT traversal with rtpproxy, accounting
2. Examples from the above book, should be downloaded
3. This user list, usually we got quick answers, mostly from developers of ag-projects
4. Book: SIP Handbook. Services, Technologies, and Security of Session Initiation Protocol (CRC Press 2009)
5. Book: Wiley.Internet.Communications.Using.SIP.Delivering.VoIP.and.Multimedia.Services.with.Session.Init


Regards,
Liviu



From: Mark Holloway <[hidden email]>
To: OpenSIPS users mailling list <[hidden email]>
Sent: Mon, July 4, 2011 6:23:56 AM
Subject: Re: [OpenSIPS-Users] SIP Registration Failure - 484 Address Incomplete

Odd, even though I now get 200 OK from OpenSIPS after registering I still receive 484 Address Incomplete after the 200 OK even though the endpoint is registered. 


On Jul 3, 2011, at 11:35 AM, Mark Holloway wrote:

I resolved it.  Forgot to uncomment one very important part of the cfg file.

if (!save("location"))
			sl_reply_error();

		exit;
	}


On Jul 3, 2011, at 11:31 AM, Mark Holloway wrote:

I have OpenSIPS 1.6.4 configured as a SIP Registrar with mysql. It is configured to challenge SIP registrations with authentication.  Keeping it simple, I've used opensipsctl to add user 1000 with password 1000 and set the IP/SIP Domain of OpenSIPS is 192.168.1.20. I am attempting to register using Counterpath Bria 3.1 (Mac).  Bria sends the initial registration to OpenSIPS and it properly responds with a 401 Unauthorized, but after Bria responds to the 401 challenge OpenSIPS responds with 484 Address Incomplete.

Looking at the docs I noticed OpenSIPS will send 484 if the username is not in the Request-Line. For example, OpenSIPS wants 1000@192.168.1.20 but Bria sends 192.168.1.20. The way Bria registers, the username portion (1000 in this case) is only in the Contact, To, and From headers. The R-URI line does not include the username portion.  Has anyone else encountered this?


==
Bria's response to 401 challenge
==

Session Initiation Protocol
    Request-Line: REGISTER sip:192.168.1.20 SIP/2.0
        Method: REGISTER
        [Resent Packet: False]


        To: "Mark"<sip:1000@192.168.1.20>
            SIP Display info: "Mark"
            SIP to address: sip:1000@192.168.1.20
        From: "Mark"<sip:1000@192.168.1.20>;tag=fbaf644d
            SIP Display info: "Mark"
            SIP from address: sip:1000@192.168.1.20
            SIP tag: fbaf644d


_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: SIP Registration Failure - 484 Address Incomplete

Bogdan-Andrei Iancu-2
In reply to this post by Mark Holloway
Hi Mark,

Probably you miss an "exit" after the save(location) block:
if (!save("location"))
	sl_reply_error();
	exit;
}
exit;

Regards,
Bogdan

On 07/04/2011 06:23 AM, Mark Holloway wrote:
Odd, even though I now get 200 OK from OpenSIPS after registering I still receive 484 Address Incomplete after the 200 OK even though the endpoint is registered. 


On Jul 3, 2011, at 11:35 AM, Mark Holloway wrote:

I resolved it.  Forgot to uncomment one very important part of the cfg file.

if (!save("location"))
			sl_reply_error();

		exit;
	}


On Jul 3, 2011, at 11:31 AM, Mark Holloway wrote:

I have OpenSIPS 1.6.4 configured as a SIP Registrar with mysql. It is configured to challenge SIP registrations with authentication.  Keeping it simple, I've used opensipsctl to add user 1000 with password 1000 and set the IP/SIP Domain of OpenSIPS is 192.168.1.20. I am attempting to register using Counterpath Bria 3.1 (Mac).  Bria sends the initial registration to OpenSIPS and it properly responds with a 401 Unauthorized, but after Bria responds to the 401 challenge OpenSIPS responds with 484 Address Incomplete.

Looking at the docs I noticed OpenSIPS will send 484 if the username is not in the Request-Line. For example, OpenSIPS wants [hidden email] but Bria sends 192.168.1.20. The way Bria registers, the username portion (1000 in this case) is only in the Contact, To, and From headers. The R-URI line does not include the username portion.  Has anyone else encountered this?


==
Bria's response to 401 challenge
==

Session Initiation Protocol
    Request-Line: REGISTER <a moz-do-not-send="true" href="sip:192.168.1.20">sip:192.168.1.20 SIP/2.0
        Method: REGISTER
        [Resent Packet: False]


       Contact: <<a moz-do-not-send="true" href="sip:1000@192.168.1.116:62018;rinstance=3b31a8f560e5c3bc;transport=udp">sip:1000@192.168.1.116:62018;rinstance=3b31a8f560e5c3bc;transport=udp>
            Contact Binding: <<a moz-do-not-send="true" href="sip:1000@192.168.1.116:62018;rinstance=3b31a8f560e5c3bc;transport=udp">sip:1000@192.168.1.116:62018;rinstance=3b31a8f560e5c3bc;transport=udp>
        To: "Mark"<<a moz-do-not-send="true" href="sip:1000@192.168.1.20">sip:1000@192.168.1.20>
            SIP Display info: "Mark"
            SIP to address: <a moz-do-not-send="true" href="sip:1000@192.168.1.20">sip:1000@192.168.1.20
        From: "Mark"<<a moz-do-not-send="true" href="sip:1000@192.168.1.20">sip:1000@192.168.1.20>;tag=fbaf644d
            SIP Display info: "Mark"
            SIP from address: <a moz-do-not-send="true" href="sip:1000@192.168.1.20">sip:1000@192.168.1.20
            SIP tag: fbaf644d



-- 
Bogdan-Andrei Iancu
OpenSIPS solutions and "know-how"

_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: SIP Registration Failure - 484 Address Incomplete

Mark Holloway
Thanks Bogdan, that was it.


On Jul 4, 2011, at 5:59 AM, Bogdan-Andrei Iancu wrote:

Hi Mark,

Probably you miss an "exit" after the save(location) block:
if (!save("location"))
	sl_reply_error();
	exit;
}
exit;

Regards,
Bogdan

On 07/04/2011 06:23 AM, Mark Holloway wrote:
Odd, even though I now get 200 OK from OpenSIPS after registering I still receive 484 Address Incomplete after the 200 OK even though the endpoint is registered. 


On Jul 3, 2011, at 11:35 AM, Mark Holloway wrote:

I resolved it.  Forgot to uncomment one very important part of the cfg file.

if (!save("location"))
			sl_reply_error();

		exit;
	}


On Jul 3, 2011, at 11:31 AM, Mark Holloway wrote:

I have OpenSIPS 1.6.4 configured as a SIP Registrar with mysql. It is configured to challenge SIP registrations with authentication.  Keeping it simple, I've used opensipsctl to add user 1000 with password 1000 and set the IP/SIP Domain of OpenSIPS is 192.168.1.20. I am attempting to register using Counterpath Bria 3.1 (Mac).  Bria sends the initial registration to OpenSIPS and it properly responds with a 401 Unauthorized, but after Bria responds to the 401 challenge OpenSIPS responds with 484 Address Incomplete.

Looking at the docs I noticed OpenSIPS will send 484 if the username is not in the Request-Line. For example, OpenSIPS wants [hidden email] but Bria sends 192.168.1.20. The way Bria registers, the username portion (1000 in this case) is only in the Contact, To, and From headers. The R-URI line does not include the username portion.  Has anyone else encountered this?


==
Bria's response to 401 challenge
==

Session Initiation Protocol
    Request-Line: REGISTER <a moz-do-not-send="true" href="sip:192.168.1.20">sip:192.168.1.20 SIP/2.0
        Method: REGISTER
        [Resent Packet: False]


       Contact: <<a moz-do-not-send="true" href="sip:1000@192.168.1.116:62018;rinstance=3b31a8f560e5c3bc;transport=udp">sip:1000@192.168.1.116:62018;rinstance=3b31a8f560e5c3bc;transport=udp>
            Contact Binding: <<a moz-do-not-send="true" href="sip:1000@192.168.1.116:62018;rinstance=3b31a8f560e5c3bc;transport=udp">sip:1000@192.168.1.116:62018;rinstance=3b31a8f560e5c3bc;transport=udp>
        To: "Mark"<<a moz-do-not-send="true" href="sip:1000@192.168.1.20">sip:1000@192.168.1.20>
            SIP Display info: "Mark"
            SIP to address: <a moz-do-not-send="true" href="sip:1000@192.168.1.20">sip:1000@192.168.1.20
        From: "Mark"<<a moz-do-not-send="true" href="sip:1000@192.168.1.20">sip:1000@192.168.1.20>;tag=fbaf644d
            SIP Display info: "Mark"
            SIP from address: <a moz-do-not-send="true" href="sip:1000@192.168.1.20">sip:1000@192.168.1.20
            SIP tag: fbaf644d



-- 
Bogdan-Andrei Iancu
OpenSIPS solutions and "know-how"


_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users