[Home]

Summary:ASTERISK-08905: SIP NOTIFY messages for hints are sent with wrong request-URI
Reporter:Steve Langstaff (srl100)Labels:
Date Opened:2007-02-28 08:58:56.000-0600Date Closed:2007-04-30 02:12:16
Priority:MajorRegression?No
Status:Closed/CompleteComponents:Channels/chan_sip/Subscriptions
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:( 0) ethereal.txt
( 1) full.txt
( 2) verbosedebug.txt
Description:The request URI for a NOTIFY message should be the contact address used in the associated SUBSCRIBE. This is not the case. The attached file shows the complete SUBSCRIBE/200/NOTIFY/404 trace, but a summary is:

1) Asterisk<--UserAgentA: SUBSCRIBE sip:6000@register SIP/2.0
                        Contact: sip:line52@192.168.5.203:5067
2) Asterisk-->UserAgentA: SIP/2.0 200 OK
3) Asterisk-->UserAgentA: NOTIFY sip:6001@10.7.1.111 SIP/2.0
4) Asterisk<--UserAgentA: SIP/2.0 404 Not Found

The NOTIFY in message 4 above should have been:

4) Asterisk-->UserAgentA: NOTIFY sip:line52@192.168.5.203:5067 SIP/2.0


****** ADDITIONAL INFORMATION ******

This is on the AsteriskNow Beta 4 VMware image.
Comments:By: Joshua C. Colp (jcolp) 2007-02-28 10:47:12.000-0600

Can you please get a sip debug from Asterisk? thanks.
By: Steve Langstaff (srl100) 2007-02-28 11:20:13.000-0600

Added 'full.txt' with 'sip set debug' output.
By: Serge Vecher (serge-v) 2007-02-28 11:41:11.000-0600

Try these instructions:
1) Prepare test environment (reduce the amount of unrelated traffic on the server);
2) Make sure your logger.conf has the following line:
  console => notice,warning,error,debug
3) restart Asterisk with the following command:
  'asterisk -Tvvvvvdddddngc | tee /tmp/verbosedebug.txt'
4) Enable SIP transaction logging with the following CLI commands:
set debug 4
set verbose 4
sip debug
5) Reproduce the problem
6) Trim startup information and attach verbosedebug.txt to the issue.
By: Steve Langstaff (srl100) 2007-02-28 14:57:51.000-0600

I think that your instructions ('sip debug') relate to Asterisk 1.2 rather than Asterisk 1.4.

Doesn't the full.txt log file have the debug info that you want in it?
By: Serge Vecher (serge-v) 2007-02-28 15:22:55.000-0600

yes, "sip debug" is a 1.2-style command. It has been deprecated in 1.4, but entering it will show you the new style. And yes, the file you've posted is not complete, that's why I've posted the instructions.
By: Steve Langstaff (srl100) 2007-03-01 03:55:47.000-0600

Added verbose trimmed debug as per request.
By: Steve Langstaff (srl100) 2007-03-02 07:28:35.000-0600

Maybe the title of this defect should be changed from:
   SIP NOTIFY messages for hints are sent to wrong contact address
to:
   SIP NOTIFY messages for hints are sent with wrong request-URI
By: Serge Vecher (serge-v) 2007-03-02 09:47:40.000-0600

did that. What happens if you use 1.4 checked out from SVN instead of an AsteriskNOW CD?
By: Steve Langstaff (srl100) 2007-03-02 09:53:59.000-0600

I'm not really in a position to learn about SVN right now, sorry. Has this issue been fixed in SVN?
By: Serge Vecher (serge-v) 2007-03-02 09:59:27.000-0600

there has been a significant amount of work on hints in 1.4, since the 1.4.0 release.
By: Steve Langstaff (srl100) 2007-03-02 10:20:00.000-0600

I'm getting out of my depth here.. I've done a SVN trunk checkout of zaptel, libpri and asterisk, but am having trouble compiling asterisk (the others compiled OK).

   sudo make clean

works OK but then

   sudo make install

complains
   "The configure script must be executed before running 'make'.

but
   sudo make configure

says
   "make: Nothing to be done for 'configure'.
By: Serge Vecher (serge-v) 2007-03-02 10:24:18.000-0600

it's ./configure you need to run. Always good to do some googling http://astrecipes.net/?n=216 (the title is for beta, but applies to release)
By: Steve Langstaff (srl100) 2007-03-02 10:39:26.000-0600

Right. Configured, built and installed OK, but segfaults when running.
   "Asterisk ended with exit status 139".

I'll leave the SVN trunk stuff to the experts, and wait for the next beta release of AsteriskNow to test this.
By: Steve Langstaff (srl100) 2007-03-05 07:54:02.000-0600

Still seems to be an issue in Asterisk 1.4.1
By: Olle Johansson (oej) 2007-03-07 01:59:21.000-0600

I need to recheck the RFCs, but it seems like you've found a bug that most phones doesn't care about. I will look into this and fix it.
By: Olle Johansson (oej) 2007-04-27 09:56:57

Please check with latest svn versions of Asterisk. I believe I fixed this last week during SIPit.
By: Olle Johansson (oej) 2007-04-30 02:12:05

No answer, so I'm assuming this is fixed. Please re-open if there's still a problem. THanks.