Issues using STUN with Sprint 3G service (Wrong Port is being used)
Brought to you by:
krunalhire
Menu
▾
▴
#441 Issues using STUN with Sprint 3G service (Wrong Port is being used)
Obsolete
nobody
None
Medium
Defect
2011-03-27
2010-12-02
Anonymous
No
Originally created by: matthewp...@gmail.com
What steps will reproduce the problem?
1. Use Sprint Network (3G) with Samsung Intercept running Android 2.1
2. Set up account to connect to external SIP server using STUN with UDP set to connect on port 5060.
3. Incorrect port is sent to SIP server.
What is the expected output? What do you see instead?
I can see REGISTER packets being sent across to my SIP server via a wireshark trace. However the port that we receive the REGISTER request on is different from the port in the VIA/Contact in the Sip Header.
The traffic comes in on the following IP / Port
66.87.22.***:63021
The SIP packet has the following IP / Port in the VIA/Contact:
66.87.22.***:33678
Because the VIA/Contact are set to port 33678, the OK packet that is sent by our sip server is sent to 33678, and is therefore not getting sent to my difference, so the registration fails.
I would expect the port to be the same, allowing me to register.
What version of the product are you using? On what operating system?
Samsung Intercept using Sprint Network (Virgin Mobile pre-paid) running Android 2.1.
Please provide any additional information below.
It appears that Sprint (Virgin Mobile) uses some type of NAT. When STUN is not enabled, the IP address in the packet (Contact/Via) is different than the IP address from which we receive the packet. Therefore I enabled STUN. I don't see any improvement with ICE (wrong IP address), STUN, or both.
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: r3gis...@gmail.com
Port you see in the VIA/Contact header is the port detected by the STUN resolution (among other resolutions : ICE and register response). It is possible that your carrier use another port when registration is sent and when stun resolution is done. If so csipsimple use the port retrieved by stun resolution and send the packet to your server with this port. If meanwhile sprint routers changes the port... it will fail.
A good idea could be to have your own STUN server on your network and use it to resolve IP and ports of clients. You may also be able to monitor what is the reply of the STUN server and see if everything is ok, but I think so (pjsip is a reliable sip library and I use it a standard way on this stuff).
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: r3gis...@gmail.com
(No comment was entered for this change.)
Status: Obsolete