[asterisk-bugs] [Asterisk 0012560]: [patch] Problems with NOTIFY due to Asterisk sending wrong CALL-ID and duplicate sip: tag in header of NOTIFY
Asterisk Bug Tracker
noreply at bugs.digium.com
Mon Nov 3 02:54:04 CST 2008
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=12560
======================================================================
Reported By: vsauer
Assigned To: oej
======================================================================
Project: Asterisk
Issue ID: 12560
Category: Channels/chan_sip/Subscriptions
Reproducibility: always
Severity: major
Priority: normal
Status: assigned
Asterisk Version: 1.4.19
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Disclaimer on File?: N/A
Request Review:
======================================================================
Date Submitted: 2008-04-30 14:10 CDT
Last Modified: 2008-11-03 02:54 CST
======================================================================
Summary: [patch] Problems with NOTIFY due to Asterisk sending
wrong CALL-ID and duplicate sip: tag in header of NOTIFY
Description:
Hi,
(first of all: I'm not an expert on SIP. So I might be completly wrong.
Don't take it personally).
I have the following problem with 1.4.19:
Leaving ore deleting a message on/from the voicemail does not correctly
trigger the MWI LED on a Siemens Gigaset S685 while it does on a Snom 370.
A lot of people may claim this is a bug of the 685, but I think it isn't.
It's related to Asterisk.
For some reason the Snom behaves more tolerant (Snoms have options like
"accept broken registrar" etc), but the 685 doesn't.
Here's the exakt problem:
Step 1) Restart Asterisk, Shut down Siemens S685
Step 2) Leave a message on voicemail
VM is registerd in all phones and setup in voicemail.conf
Snom phone (which is on all the time) starts blinking
Step 3) Power on Siemens S685
Siemens get subscription:
arthur*CLI> sip show subscriptions
Peer User Call ID Extension Last state
Type Mailbox
192.168.0.15 gigaset11 1259484430@ -- <none>
mwi 101 at defaul
MWI LED starts blinking.
Step 4) Take another phone (like the Snom), goto mailbox and delete
message
-> Snom stops blinking
-> S685 doesn't, MWI still blinking
After deletion of the messgae, CLI shows:
[Apr 30 20:33:27] WARNING[16137]: chan_sip.c:12814 handle_response: Remote
host can't match request NOTIFY to call
'67ffd8e6092c427f3e23547d06841655 at volker-sauer.de'. Giving up.
See dump of packages in additional information.
You can see, that in Packet 1, the Call-ID of the subscriprion is
1259484430 at 192_168_0_15
In Packet 3 - which is the notify of changed count of messages in VM, the
Call-ID is:
67ffd8e6092c427f3e23547d06841655 at volker-sauer.de
which is therefore rejected by the Siemens in Packet 4:
481 Call Leg/Transaction Does Not Exist
Somehow Snom phons accept this, though.
What is weired, too:
Look at the To field in packet 1:
To: <sip:sip:gigaset11 at 192.168.0.15:5060>;tag=4293876579
why "sip:sip:...." is this correct? Lookes like a typo..
and somehow it's correct in package 3:
To: <sip:gigaset11 at 192.168.0.15:5060>
I'll add a wireshark dump of the 4 packages in case additional information
is needed.
To my understanding, the Siemens seems to be right by rejecting the
NOTIFY. And this could be a bug of Asterisk.
Maybe it's related too:
http://bugs.digium.com/view.php?id=6848
See the message of caspy on 04-03-06 06:25
"It seems, that this is because NOTIFY request come with 'tag' field in
"From:" header different to one, that was given by phone in SUBSCRIBE
request."
Maybe this could be related, too.
Regards
Volker
======================================================================
----------------------------------------------------------------------
(0094514) ibercom (reporter) - 2008-11-03 02:54
http://bugs.digium.com/view.php?id=12560#c94514
----------------------------------------------------------------------
I think so that it is a subscriptions problem.
I have a Thomson ST2030, I wrote the note (0089978) and I have been
investigating something more. If I apply this:
--- if (strcmp(event, "message-summary") && gotdest) {
--->
+++ if (gotdest) {
The telephone don't subscribe to MWI and no errors, it don't find the
extension (config problem), it is OK.
The problem is when the telephone try subscribe, correctly, to MWI. The
first time something happens, until a pair of re-subscribed it doesn't
become stable and OK:
asterisk1*CLI> sip show subscriptions
Peer User Call ID Extension Last state
Type Mailbox
172.19.12.4 20087 3c8015-c0a8 -- <none>
mwi 20087 at aste
172.19.12.39 43140 329f7a-c0a8 -- <none>
mwi 43140 at aste
172.19.23.212 20170 5442-c0a801 -- <none>
mwi 20170 at aste
172.19.23.196 46135 5a09-c0a801 -- <none>
mwi 46135 at aste
172.19.22.139 20205 412d-c0a801 -- <none>
mwi 20205 at aste
172.19.22.139 20205 49fe-c0a801 -- <none>
mwi 20205 at aste
172.19.23.195 43462 61b8-c0a801 -- <none>
mwi 43462 at aste
172.19.12.3 20097 2a545c-c0a8 -- <none>
mwi 20097 at aste
172.19.11.162 20091 2a4999-c0a8 -- <none>
mwi 20091 at aste
172.19.11.161 44232 2a5b13-c0a8 -- <none>
mwi 44232 at aste
10 active SIP subscriptions
[Nov 3 08:43:03] NOTICE[30123] chan_sip.c: Peer '20205' is now
UNREACHABLE! Last qualify: 16
[Nov 3 08:43:26] NOTICE[30123] chan_sip.c: Peer '20205' is now Reachable.
(33ms / 2000ms)
[Nov 3 08:43:26] WARNING[30123] chan_sip.c: Remote host can't match
request NOTIFY to call '49fe-c0a80101-d-2 at 172.19.22.139'. Giving up.
[Nov 3 08:44:30] NOTICE[30123] chan_sip.c: Peer '20205' is now
UNREACHABLE! Last qualify: 33
[Nov 3 08:45:27] NOTICE[30123] chan_sip.c: Peer '20205' is now Reachable.
(20ms / 2000ms)
[Nov 3 08:45:27] WARNING[30123] chan_sip.c: Remote host can't match
request NOTIFY to call '412d-c0a80101-d-2 at 172.19.22.139'. Giving up.
asterisk1*CLI> sip show subscriptions
Peer User Call ID Extension Last state
Type Mailbox
172.19.22.139 20205 1796ab-c0a8 -- <none>
mwi 20205 at aste
172.19.12.4 20087 3c8015-c0a8 -- <none>
mwi 20087 at aste
172.19.12.39 43140 329f7a-c0a8 -- <none>
mwi 43140 at aste
172.19.23.212 20170 5442-c0a801 -- <none>
mwi 20170 at aste
172.19.23.196 46135 5a09-c0a801 -- <none>
mwi 46135 at aste
172.19.22.139 20205 49fe-c0a801 -- <none>
mwi 20205 at aste
172.19.23.195 43462 61b8-c0a801 -- <none>
mwi 43462 at aste
172.19.12.3 20097 2a545c-c0a8 -- <none>
mwi 20097 at aste
172.19.11.162 20091 2a4999-c0a8 -- <none>
mwi 20091 at aste
172.19.11.161 44232 2a5b13-c0a8 -- <none>
mwi 44232 at aste
10 active SIP subscriptions
[Nov 3 09:15:47] WARNING[30123] chan_sip.c: Remote host can't match
request NOTIFY to call '1796ab-c0a80101-d-4 at 172.19.22.139'. Giving up.
I have two subscriptions for 20205 in Asterisk, is it possible ? And the
telephone try again:
asterisk1*CLI> sip show subscriptions
Peer User Call ID Extension Last state
Type Mailbox
172.19.23.212 20170 2a53fe-c0a8 -- <none>
mwi 20170 at aste
172.19.23.196 46135 1c1b4e-c0a8 -- <none>
mwi 46135 at aste
172.19.11.242 20084 e55b9-c0a80 -- <none>
mwi 20084 at aste
172.19.22.139 20205 3390dd-c0a8 -- <none>
mwi 20205 at aste
172.19.21.16 20338 4e86-c0a801 -- <none>
mwi 20338 at aste
172.19.23.195 43462 1c24cc-c0a8 -- <none>
mwi 43462 at aste
172.19.12.4 20087 3c8015-c0a8 -- <none>
mwi 20087 at aste
172.19.12.39 43140 329f7a-c0a8 -- <none>
mwi 43140 at aste
172.19.12.3 20097 2a545c-c0a8 -- <none>
mwi 20097 at aste
172.19.11.162 20091 2a4999-c0a8 -- <none>
mwi 20091 at aste
172.19.11.161 44232 2a5b13-c0a8 -- <none>
mwi 44232 at aste
11 active SIP subscriptions
Now it is OK, I have a subscription for 20205. The log is empty, no more
error "Remote host can't match request NOTIFY".
What's happens ???
Issue History
Date Modified Username Field Change
======================================================================
2008-11-03 02:54 ibercom Note Added: 0094514
======================================================================
More information about the asterisk-bugs
mailing list