|Summary:||ASTERISK-07914: Device get registered only if debug is activated for his IP address|
|Date Opened:||2006-10-11 10:27:35||Date Closed:||2006-10-29 02:55:42.000-0600|
|Environment:||Attachments:||( 0) sip.debug.registration|
|Description:||We have a device -IP phone Tiger IP202- that we ask to register. If asterisk is restarted or the registration delay has expiry, the registration is not done, sip list peers shows UNKNOWN (we qualify in sip.conf) w/o IP address.|
Now in CLI, we run sip debug IP <Phone IP> and automagically registration is done! See attached file.
|Comments:||By: tootai (tootai) 2006-10-12 15:07:54|
I made the test on running sip debug command in CLI (instead of debugging the ip): it does also make the registration executed properly.
By: Olle Johansson (oej) 2006-10-27 12:28:31
This is not the debug file we need. You need to capture ALL output with SIP debug turned on and debug and verbose set to level 4. We need to see what's going on.
Try capturing a failure and a success (if capturing a failure is possible).
By: Serge Vecher (serge-v) 2006-10-27 13:25:12
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 Asterik.
4) Enable SIP transaction logging with the following CLI commands:
set debug 4
set verbose 4
5) Save complete console log to file and _attach_ said file to the bug.
i.e. asterisk -Tvvvvvdddddgc | tee /tmp/sipdebug.txt
By: Olle Johansson (oej) 2006-10-28 10:37:05
I have read through the code and can say with 200% accuracy that this can't happen. Yet it does. Software technology is amazing. We do the impossible!!! :-)
I really need more information. Do whatever you can to find patterns and describe your system in detail - if you use any modules not included, realtime, anything. Thanks.
By: tootai (tootai) 2006-10-29 02:22:37.000-0600
Since 24hours I try to reproduce the problem from all angles and couldn't. I then discover that colleagues made an CVS update on the 18 of october. What is not cool -and that's why I didn't search on another direction- is that the revision number in CLI 'show version' is still the same that the one from the time I opened the bug:
keewi*CLI> show version
Asterisk SVN-trunk-r44241 built by root @ keewi on a i686 running Linux on 2006-10-18 17:01:07 UTC
So the problem seems to have been solved between the 11 october SVN trunk version and the 18th one. Can this be confirmed?
By: Olle Johansson (oej) 2006-10-29 02:55:42.000-0600
Well, if it's fixed it's all for the good. Please re-open if it turnes up again. Thanks for spending time trying to resolve this with me!