Summary: | ASTERISK-10721: Problem when using NAT and Subscriptions | ||
Reporter: | Joerg Staedele (brainy) | Labels: | |
Date Opened: | 2007-11-08 16:39:45.000-0600 | Date Closed: | 2011-06-07 14:08:11 |
Priority: | Minor | Regression? | No |
Status: | Closed/Complete | Components: | Channels/chan_sip/Subscriptions |
Versions: | Frequency of Occurrence | ||
Related Issues: | |||
Environment: | Attachments: | ||
Description: | Scenario: Several Snom IP Phones behind a NAT Gateway (no Portforwards exist). Everything is working fine but then a NOTIFY goes out from Asterisk to a Phone, the Phone sends back the ACK (the ACK is definititly seen by Asterisk) it does not recognize it as the right ACK packet. Thats resulting in Retransmission of already sent and received Packets. Tests were made with Asterisk 1.4.13 In the Additional Info you can see: Retransmission #3, then the ACK packet but after that, there's Retransmission #4 because it didnt recognize the ACK successfully. ****** ADDITIONAL INFORMATION ****** Retransmitting #3 (NAT) to 81.92.165.150:2054: NOTIFY sip:dkrejci@172.16.16.253:2054;line=u067m71v SIP/2.0 Via: SIP/2.0/UDP 81.92.164.137:5060;branch=z9hG4bK13ee8a25;rport From: <sip:12@voip.tnib.de;user=phone>;tag=as1a4e756f To: <sip:dkrejci@voip.tnib.de>;tag=5pujc8rf55 Contact: <sip:12@81.92.164.137> Call-ID: 3c26756fb219-yoz4ryexunwv CSeq: 105 NOTIFY User-Agent: Asterisk PBX Max-Forwards: 70 Event: dialog Content-Type: application/dialog-info+xml Subscription-State: active Content-Length: 218 <?xml version="1.0"?> <dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="3" state="full" entity="sip:12@voip.tnib.de"> <dialog id="12" direction="recipient"> <state>early</state> </dialog> </dialog-info> <--- SIP read from 81.92.165.150:2054 ---> SIP/2.0 200 Ok Via: SIP/2.0/UDP 81.92.164.137:5060;branch=z9hG4bK13ee8a25;rport=5060 From: <sip:12@voip.tnib.de;user=phone>;tag=as1a4e756f To: <sip:dkrejci@voip.tnib.de>;tag=5pujc8rf55 Call-ID: 3c26756fb219-yoz4ryexunwv CSeq: 105 NOTIFY Content-Length: 0 Retransmitting #4 (NAT) to 81.92.165.150:2054: NOTIFY sip:dkrejci@172.16.16.253:2054;line=u067m71v SIP/2.0 Via: SIP/2.0/UDP 81.92.164.137:5060;branch=z9hG4bK13ee8a25;rport From: <sip:12@voip.tnib.de;user=phone>;tag=as1a4e756f To: <sip:dkrejci@voip.tnib.de>;tag=5pujc8rf55 Contact: <sip:12@81.92.164.137> Call-ID: 3c26756fb219-yoz4ryexunwv CSeq: 105 NOTIFY User-Agent: Asterisk PBX Max-Forwards: 70 Event: dialog Content-Type: application/dialog-info+xml Subscription-State: active Content-Length: 218 <?xml version="1.0"?> <dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="3" state="full" entity="sip:12@voip.tnib.de"> <dialog id="12" direction="recipient"> <state>early</state> </dialog> </dialog-info> | ||
Comments: | By: Joerg Staedele (brainy) 2007-11-08 18:55:32.000-0600 Finally i fixed it with that patch! http://bugs.digium.com/file_download.php?file_id=16131&type=bug By: Joshua C. Colp (jcolp) 2007-11-12 07:55:13.000-0600 This issue has already been fixed in 1.4 and trunk, and will be in the next release. |