Summary: | ASTERISK-11941: [SIP/TCP] received 302 Moved Temporarily via TCP, but invite sent via UDP | ||
Reporter: | Paul Belanger (pabelanger) | Labels: | |
Date Opened: | 2008-04-29 11:32:05 | Date Closed: | 2008-04-29 11:33:31 |
Priority: | Minor | Regression? | No |
Status: | Closed/Complete | Components: | Channels/chan_sip/General |
Versions: | Frequency of Occurrence | ||
Related Issues: | |||
Environment: | Attachments: | ( 0) SIP.txt | |
Description: | Using 1.6.0-beta8, I've setup a SIP peer using transport=tcp and promiscredir=yes. The peer replies with a 302 "Moved Temporarily", asterisk attempts to forward, but does so using UDP. I'm not sure how asterisk is to determine with protocol to use to send the invite to. Here is a snip of the 302 "Moved Temporarily": --- <--- SIP read from TCP://172.16.2.190:5060 ---> SIP/2.0 302 Moved Temporarily FROM: "Unknown Name"<sip:6137959112@172.16.2.185>;tag=as43494201 TO: <sip:6136274820@172.16.2.190>;tag=e64e5385f4 CSEQ: 102 INVITE CALL-ID: 3f2d24a02c67b01212d53b847642f08b@172.16.2.185 VIA: SIP/2.0/TCP 172.16.2.185:5060;branch=z9hG4bK500d5fb5;rport CONTACT: <sip:6136274820@172.16.2.190:5070;transport=Tcp;maddr=172.16.2.190;x-mss-call-id=3f2d24a02c67b01212d53b847642f08b%40172.16.2.185> CONTENT-LENGTH: 0 SERVER: RTCC/3.0.0.0 --- See attached SIP.txt for trace. ****** ADDITIONAL INFORMATION ****** sip.conf --- [IVR1] host=172.16.2.190 type=peer transport=tcp promiscredir=yes | ||
Comments: | By: Joshua C. Colp (jcolp) 2008-04-29 11:33:28 This is a duplicate of issue 11843. Please follow progress there. |