[Home]

Summary:ASTERISK-03241: Registration of Snom 190 failing
Reporter:amzaka (amzaka)Labels:
Date Opened:2005-01-10 09:03:47.000-0600Date Closed:2005-01-13 23:18:18.000-0600
Priority:MajorRegression?No
Status:Closed/CompleteComponents:Core/General
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:( 0) chan_sip.diff
Description:My snom 190 registration is getting fail once I have get the latest CVS this morning. I have set up the sip_notify.conf as well but it is still failing. Once I restore the old chan_sip.c it gets register successfully.
Comments:By: Clod Patry (junky) 2005-01-10 09:19:54.000-0600

Please attach your config.
By: Brian West (bkw918) 2005-01-10 10:08:03.000-0600

and a sip debug.
By: amzaka (amzaka) 2005-01-10 10:20:32.000-0600

I am using the realtime res_config_mysql. I got nothing on the asterisk console. My tethereal  trace is as under : -


4405.302967 Intel_d3:1e:88 -> Snom_Tec_22:03:c9 ARP Who has 192.168.1.100?  Tell 192.168.1.4
4405.303271 Snom_Tec_22:03:c9 -> Intel_d3:1e:88 ARP 192.168.1.100 is at 00:04:13:22:03:c9
4408.308685 192.168.1.100 -> 192.168.1.4  SIP Request: REGISTER sip:192.168.1.4
4408.308755  192.168.1.4 -> 192.168.1.100 ICMP Destination unreachable
4408.362234 192.168.1.100 -> 192.168.1.4  SIP Request: REGISTER sip:192.168.1.4
4408.362311  192.168.1.4 -> 192.168.1.100 ICMP Destination unreachable
4408.364618 192.168.1.100 -> 192.168.1.4  SIP Request: REGISTER sip:192.168.1.4

my sip_notify.conf is

[polycom-check-cfg]
Event=>check-sync
Content-Length=>0

; Untested
[sipura-check-cfg]
Event=>resync
Content-Length=>0

; Untested
[grandstream-check-cfg]
Event=>sys-control

; Untested
[cisco-check-cfg]
Event=>check-sync
Content-Length=>0

; Untested - from Snom docs
[reboot-snom]
Event=>reboot
Content-Length=>0


sip_buddies table in my sql is : -

mysql> select * from  sip_buddies  where name ='660';
+----------+------+-------------+----------+-----------+-------------------+-------------+---------+-----------+----------+----------+------------+---------+---------------+---------------+----------+----------+-------------+-----------+------+--------+------+-------------+------+---------+-------------+------------+----------------+--------+--------+----------+-------+----------+------------+---------------+
| uniqueid | name | accountcode | amaflags | callgroup | callerid          | canreinvite | context | defaultip | dtmfmode | fromuser | fromdomain | host    | incominglimit | outgoinglimit | insecure | language | mailbox     | md5secret | nat  | permit | deny | pickupgroup | port | qualify | restrictcid | rtptimeout | rtpholdtimeout | secret | type   | username | allow | disallow | regseconds | ipaddr        |
+----------+------+-------------+----------+-----------+-------------------+-------------+---------+-----------+----------+----------+------------+---------+---------------+---------------+----------+----------+-------------+-----------+------+--------+------+-------------+------+---------+-------------+------------+----------------+--------+--------+----------+-------+----------+------------+---------------+
|        5 | 660  | NULL        | NULL     | 1         | 08458900931 <660> | 0           | jsearch | NULL      | rfc2833  | NULL     | NULL       | dynamic | NULL          | NULL          | NULL     | NULL     | 08458900931 | NULL      | NULL | NULL
 | NULL | 1           | 5060 | 1       | 1           | NULL       | NULL           | alex   | friend | 660      | NULL  | NULL     | 1105374407 | 192.168.1.100 |
By: Brian West (bkw918) 2005-01-10 10:29:01.000-0600

This seems to be a local network issue... not an asterisk issue.

192.168.1.4 -> 192.168.1.100 can't talk.

bkw
By: amzaka (amzaka) 2005-01-10 10:32:30.000-0600

No its an asterisk issue since once i downgraded the chan_sip.c the phone registered successfully. The feature of the sip_notify.conf is not tested with SNOM. It needs to be resolution.
By: Mark Spencer (markster) 2005-01-10 10:48:14.000-0600

What is the last version of chan_sip.c to work, and what is the first version of chan_sip.c not to work?  you can use:

cvs update -r 1.625 channels/chan_sip.c

to check out each version (simply place 1.624, 1.623, etc in place of 1.625).  When done you can do:

cvs update -A channels/chan_sip.c

to remove the "sticky" bit and allow CVS to return to normal functioning.

By knowing exactly which one introduced the failure we can better identify the problem.
By: Kevin P. Fleming (kpfleming) 2005-01-10 11:21:49.000-0600

The "sip_notify" feature has nothing to do with this problem, amzaka. It's only an addition that is not even used unless you issue a "sip notify" command from the CLI prompt.
By: Brian West (bkw918) 2005-01-10 15:00:12.000-0600

does this happen when you dont use res_config?  and did you Make clean and reinstall asterisk.. and make clean and reinstall res_config_mysql too?  Anytime any structs change you MUST make clean...

bkw
By: amzaka (amzaka) 2005-01-11 04:16:47.000-0600

I have tried today with the new CVS today with all directories libpri, zaptel, asterisk, asterisk-addons and still experiencing problems.
By: amzaka (amzaka) 2005-01-11 04:36:17.000-0600

The chan_sip.diff is the the diff of the one working and latest CVS one.
By: Olle Johansson (oej) 2005-01-11 08:56:22.000-0600

Please add a sip debug...
By: amzaka (amzaka) 2005-01-11 08:59:47.000-0600

well there was no sip debug message on the asterisk console.

My tethereal trace is as under : -


4405.302967 Intel_d3:1e:88 -> Snom_Tec_22:03:c9 ARP Who has 192.168.1.100? Tell 192.168.1.4
4405.303271 Snom_Tec_22:03:c9 -> Intel_d3:1e:88 ARP 192.168.1.100 is at 00:04:13:22:03:c9
4408.308685 192.168.1.100 -> 192.168.1.4 SIP Request: REGISTER sip:192.168.1.4
4408.308755 192.168.1.4 -> 192.168.1.100 ICMP Destination unreachable
4408.362234 192.168.1.100 -> 192.168.1.4 SIP Request: REGISTER sip:192.168.1.4
4408.362311 192.168.1.4 -> 192.168.1.100 ICMP Destination unreachable
4408.364618 192.168.1.100 -> 192.168.1.4 SIP Request: REGISTER sip:192.168.1.4
By: Mark Spencer (markster) 2005-01-12 10:42:19.000-0600

The diff you attached runs across many versions.  We need the diff between the two.  What was the last version which worked and the first one which did not work as per the commands I specified above?
By: amzaka (amzaka) 2005-01-13 07:33:05.000-0600

Well! this is the diff between one working and the latest CVS chan_sip.c. When I try use your method of downgrade until version 1.620 the problem is remains there.  Therefore, I updated a diff between the which works fine and latest CVS one.
By: Mark Spencer (markster) 2005-01-13 08:41:17.000-0600

You need to keep going down until you get the one that clears the problem.  It could easily be as many as 15 versions ago, but we need the exact versions which are the last one to work and the first one to not work.
By: () 2005-01-13 13:48:12.000-0600

Sounds like the related bug in :

http://bugs.digium.com/bug_view_page.php?bug_id=0003332

Apply the patch chan_sip.diff and let us know if that works for you.
By: Mark Spencer (markster) 2005-01-13 21:32:34.000-0600

This should definitely be fixed by the earlier patch today.  If not, feel free to reopen.