rendered paste bodyDownload Gizmo
*
*
*
Members Sign In
Gizmo Project
* Help
* Forums
* Extras
* Learn More
* Home
Home > Ticket List > Ticket Status: OJE-89975
Ticket Details: OJE-89975
TCP SIP messages being received with headers for UDP SIP
Status: Closed
Created On: 08 Aug 2007 01:53 PM
Author Contents
Jason Garland
Posted on: 08 Aug 2007 01:53 PM
I register to proxy01.sipphone.com via TCP and when I receive an INVITE it comes in via TCP (as it should) but the contents of the SIP message have UDP type headers:
Via: SIP/2.0/UDP
instead of
Via: SIP/2.0/TCP
I should also mention that "RemoteIP: 63.80.235.205" is also not valid and should be added as a tag to the Via line like this: received=63.80.235.205
Here is the INVITE:
18:21:35.605021 IP (tos 0x0, ttl 50, id 32621, offset 0, flags [DF], proto: TCP (6), length: 860) 198.65.166.156.7070 > 207.210.228.172.57262: P, cksum 0x
b588 (correct), 3190098434:3190099242(808) ack 1641935845 win 3066
E...m@.2....A...........%
.a..............
/...#..INVITE sip:17476771749@207.210.228.172:5060 SIP/2.0
Record-Route:
Max-Forwards: 16
To:
Via: SIP/2.0/UDP 198.65.166.131;branch=z9hG4bK13b3.ece705e1.3
Via: SIP/2.0/UDP 63.80.235.205:5061;rport=5061;branch=z9hG4bK665474089
From: ;tag=438662723
Call-ID: 1894304412@63.80.235.205
CSeq: 65448 INVITE
User-Agent: YATE/1.2.0
Contact:
Allow: ACK, INVITE, BYE, CANCEL, REGISTER, REFER, OPTIONS, INFO
Content-Type: application/sdp
Content-Length: 185
RemoteIP: 63.80.235.205
v=0
o=yate 1186525177 1186525177 IN IP4 63.80.235.205
s=SIP Call
c=IN IP4 63.80.235.205
t=0 0
m=audio 19968 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
Jason Garland
Posted on: 08 Aug 2007 02:41 PM
I am attaching a packet capture.
Adrian Torres
Posted on: 15 Aug 2007 01:29 PM
We do not support SIP over TCP directly on our SIP proxy so we use a special gateway for UDP blocking firewalls. There are other specific details regarding this scenario I am not authorized to disclose. Also RemoteIP: is a non standard header used for our "Map It" feature and is irrelevant. I would recommend using UDP instead but if this is an issue please let me know.
Thank you for your patience.
Sincerely,
SIPphone Customer Care
Jason Garland
Posted on: 15 Aug 2007 02:16 PM
I didn't choose TCP. Your DNS SRV records told me to use TCP. For my work around I had to publish NEW DNS records on my local DNS server for your domains to resolve the problem. If you don't want me using TCP then don't publish a _sip._tcp.proxy01.sipphone.com SRV record.
Your current record looks like this:
; <<>> DiG 9.3.2 <<>> -t SRV _sip._tcp.proxy01.sipphone.com
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 33718
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; QUESTION SECTION:
;_sip._tcp.proxy01.sipphone.com. IN SRV
;; ANSWER SECTION:
_sip._tcp.proxy01.sipphone.com. 1792 IN SRV 10 10 7070 uap.sipphone.com.
;; ADDITIONAL SECTION:
uap.sipphone.com. 21592 IN A 198.65.166.156
;; Query time: 2 msec
;; SERVER: 172.16.1.29#53(172.16.1.29)
;; WHEN: Wed Aug 15 18:00:40 2007
;; MSG SIZE rcvd: 100
This record indicates that you want me to connect to uap.sipphone.com via TCP on port 7070
If your preference is for me not to use TCP then you need to add a SRV record for UDP IE:
_sip._udp.proxy01.sipphone.com IN SRV 10 10 5060 uap.sipphone.com.
and a NAPTR record indicating your preference of UDP over TCP:
proxy01.sipphone.com. IN NAPTR 0 0 "s" "SIP+D2U" "" _sip._udp.proxy01.sipphone.com.
proxy01.sipphone.com. IN NAPTR 1 0 "s" "SIP+D2T" "" _sip._tcp.proxy01.sipphone.com.
I would suggest something like the following records for your DNS:
;; These would have helped me a bit.
_sip._udp.proxy01 IN SRV 10 10 5060 proxy01.sipphone.com.
_sip._tcp.proxy01 IN SRV 10 10 7070 uap.sipphone.com.
;; this lets anyone figure out who the SIP proxy servers are for your domain...
_sip._udp IN SRV 10 10 5060 proxy01.sipphone.com.
_sip._tcp IN SRV 10 10 7070 uap.sipphone.com.
;; Lets throw some stun servers in...
_stun._udp IN SRV 10 0 3478 stunserver.org.
_stun._udp IN SRV 20 0 3478 stun.xten.com.
;; These would tell me SIP UA that you prefer UDP over TCP
proxy01.sipphone.com. IN NAPTR 0 0 "s" "SIP+D2U" "" _sip._udp.proxy01.sipphone.com.
proxy01.sipphone.com. IN NAPTR 1 0 "s" "SIP+D2T" "" _sip._tcp.proxy01.sipphone.com.
;; These would tell me SIP UA that you prefer UDP over TCP
;; and let me know that these are the SRV records I should look for when I want to talk to sipphone.com via SIP
sipphone.com. IN NAPTR 0 0 "s" "SIP+D2U" "" _sip._udp.proxy01.sipphone.com.
sipphone.com. IN NAPTR 1 0 "s" "SIP+D2T" "" _sip._tcp.proxy01.sipphone.com.
And the RemoteIP: header should be x-RemoteIP: if it is a non standard header. All non standard headers are supposed to start with x-
Rate this ticket: Helpful Not Helpful ()
Post Reply
Subject: TCP SIP messages being received with headers for UDP SIP
Message:
Rating: Was the staff reply helpful? Yes No Dont Rate
Attach a file
Description:
File:
* about us
* tell a friend
* fine print
* site-map
* ©2005 SIPphone