Voxalot / SIP Broker Support Forums - View Single Post - UTStarcom GF210 Will not register to Voxalot

boatman · 02-16-2009, 06:39 AM

Well, I have no idea what's preventing SIP registration. I don't know about Voxalot's proxies, but some proxies will stop responding to a user agent if SIP registration requests are sent too frequently. Including registration attempts and NAT keep alive packets, how many SIP packets per minute are being sent to Voxalot from your UTSTARCOM GF210 and any other user agents you may have which use the same Voxalot user ID?

Edit: While using the Terminal Capabilities function of Twinkle to look for problems, I noticed that your user agent returned rport 1024, when I was using 5060. The rport is found in the Via header of SIP responses, and is supposed to show the port number of the return address of a received SIP packet. I don't know what would cause an incorrect rport response, or if it could be related to the non-registration issue.

02-16-2009, 06:39 AM	#9
boatman Senior Member Join Date: Jul 2007 Location: Oregon, USA Posts: 365 Thanks: 17 Thanked 77 Times in 64 Posts	Well, I have no idea what's preventing SIP registration. I don't know about Voxalot's proxies, but some proxies will stop responding to a user agent if SIP registration requests are sent too frequently. Including registration attempts and NAT keep alive packets, how many SIP packets per minute are being sent to Voxalot from your UTSTARCOM GF210 and any other user agents you may have which use the same Voxalot user ID? Edit: While using the Terminal Capabilities function of Twinkle to look for problems, I noticed that your user agent returned rport 1024, when I was using 5060. The rport is found in the Via header of SIP responses, and is supposed to show the port number of the return address of a received SIP packet. I don't know what would cause an incorrect rport response, or if it could be related to the non-registration issue. Last edited by boatman; 02-17-2009 at 03:28 AM.