Summary:	ASTERISK-14334: On upgrade from version 1.6.0.6 to 1.6.1.0 Error: "No matching peer found"
Reporter:	Marco Kalis (zimbokraut)	Labels:
Date Opened:	2009-06-18 06:17:59	Date Closed:	2009-09-15 13:49:19
Priority:	Major	Regression?	No
Status:	Closed/Complete	Components:	Channels/chan_sip/Registration
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:
Description:	- Running 1.6.0.6 - ATAs (Fritz!Box Fon, Nokia E70, Nokia E90) work perfectly with no problem. backed up config - still worked... - installed asterisk-1.6.1.1 - installed asterisk-addons-1.6.1.0 - installed asterisk-gui (rev. 4877) from svn - restored config from GUI - No clients could access Asterisk anymore Error message: snip.... [Jun 18 08:45:16] NOTICE[21269] chan_sip.c: Registration from '<sip:6001@virgin-gw.kalis.cc>' failed for '192.168.179.4' - No match ing peer found [Jun 18 08:45:21] NOTICE[21269] chan_sip.c: Registration from '<sip:6002@virgin-gw.kalis.cc>' failed for '192.168.179.4' - No match ing peer found [Jun 18 08:45:21] NOTICE[21269] chan_sip.c: Registration from '<sip:6003@virgin-gw.kalis.cc>' failed for '192.168.179.4' - No match ing peer found snip..... tried various changes in the config files to no avail... reverted back to asterisk-1.6.0.6 and asterisk-addons-1.6.0.1, but stayed with GUI rev. 4877 restored backup and worked like a charm. ****** ADDITIONAL INFORMATION ****** I suspect, that for some reason, Asterisk does not read the config from the user.conf, to which the GUI writes to. Therefore it cannot find the data to authenticate the clients. Is it possible, that the user.conf just gets ignored? I have also looked in the update docs but couldn't find any hints. would be greate to hear what this could be.
Comments:	By: Leif Madsen (lmadsen) 2009-06-24 13:46:19 Assigned to awk in case something in the particular GUI revision would have caused any sorts of issues. There is a very real possibility this has nothing to do with the GUI though, but I'd have expected very few changes in users.conf between 1.6.0.x and 1.6.1.x. If it is an Asterisk problem, the reporter will need to provide console output of the error, SIP debug data, along with the output of 'sip show peers' and 'sip show users'. The relevant configuration files (sip.conf, users.conf) may also be useful. By: Marco Kalis (zimbokraut) 2009-06-24 14:39:07 thnx for looking at this.... I am still reasonably new to asterisk, so you might have to hold my hand a little. getting the sip show peers and sip show users data is no prob. in terms of SIP debug data, could you elaborate on that? would you like me to run a sniffer like TCPdump or wireshark? In regards to the console output, would you be happy with the relevant logs? maybe some sort of "before upgrade", "after upgrade" logs...? Or should I just set the verbosity to X and attache the "screenshot" sorry to be a pain, but even though I can read code, I am not a developer and still fairly new to asterisk. Apart from that, I will prob. need one ore two days to get the info,.since I have a little bit of a time problem at the moment thnx ZimboKraut By: umesh keerthy (umesh_asterisk) 2009-06-27 03:26:27 some more info regarding this: Through gui if i add users in 1.6.1.0, then CLI command "sip show users" doesnt show anything. Through gui if i add users in 1.4.15, then CLI command "sip show users" shows the addded users. Both cases i enter the same entries and settings for users. All are SIP Users with RFC2833 enabled and Insecure=very. Below is the debug errors i get when using 1.6.1.0 for the endpoint registering: ------------------------ CLI> [Jun  4 10:18:24] NOTICE[12669]: chan_sip.c:19536 handle_request_register: Registration from '"6000"<sip:6000@192.168.53.114>' failed for '192.168.53.156' - No matching peer found [Jun  4 10:18:45] NOTICE[12669]: chan_sip.c:19536 handle_request_register: Registration from '"6000"<sip:6000@192.168.53.114>' failed for '192.168.53.156' - No matching peer found ------------------------ As erver is currently being used for testing purposes, i am still using the stable 1.4.25 Regards, Umesh By: Leif Madsen (lmadsen) 2009-06-29 11:14:23 ZimboKraut: you can get the sip debug via:  sip set debug on A PCAP trace may also be useful -- yes, just use wireshark with appropriate filters. Yes, relevant logs would be useful, but you need to capture the console output where it is failing: asterisk -cvvvn | tee /tmp/console_output_verbose_level_3.txt By: Christophe PEREZ (novazur) 2009-07-01 14:33:33 Same problem here with asterisk 1.6.1.0 on gentoo By: Jason Girdner (jgirdner) 2009-07-01 16:22:11 I have the same problem with the following setup Asterisk/1.6.1.0 Asterisk GUI-version : SVN-branch-2.0-r4954 By: Christophe PEREZ (novazur) 2009-07-01 16:43:19 I found a solution that worked for me. Remove all extensions, reload GUI (button up right), create extensions. By: Jason Girdner (jgirdner) 2009-07-01 16:49:49 luckly i only have one test extension to delete...I deleted reloaded and then added again, and it still doesnt work. By: Ryan Brindley (rbrindley) 2009-07-01 16:54:04 jgirdner, do your peers defined by the GUI in users.conf have a "type=peer" line? If not, add that to your test extension, reload Asterisk, and see if it registers then. This is one of the known SIP differences between 1.6.0 and 1.6.1 that has effected the GUI. Also, if you did delete, the reload the GUI and re-add the extension, make sure you applied changes (aka reloaded Asterisk). By: Ryan Brindley (rbrindley) 2009-07-01 16:55:22 I did recently commit a patch that should be adding that type=peer line when a user is added. If this isn't happening, then I need to determine why that is the case. If it is happening and you're still having registration issues, when I need to see what other SIP changes btw 1.6.0 and 1.6.1 caused this issue. By: Jason Girdner (jgirdner) 2009-07-01 17:00:02 I added type=peer in the user.conf file and the extension registered.  Do you know what file would need to be updated with your revision to add type=peer when an extension is created? By: Ryan Brindley (rbrindley) 2009-07-02 09:10:19 config/js/pbx2.js is the library for any config file updating. Its not used in every situation (like it should), but the GUI is getting there. Anyway, pbx.users.{add|edit} are the functions that should be updated. By: Russell Bryant (russell) 2009-09-15 13:49:18 There have been a number of fixes to peer matching since this report, so this has most likely been fixed. If you still have a problem, feel free to open a new report against the latest version. Thanks.