PBXes (http://www1.pbxes.com/forum/index.php)
- English (http://www1.pbxes.com/forum/board.php?boardid=16)
-- Terminal Equipment (http://www1.pbxes.com/forum/board.php?boardid=21)
--- (http://www1.pbxes.com/forum/threadid.php?threadid=629)

Unlocked Netgear TA612V

I have an ex-sipgate Netgear TA612V which is running the unlocked firmware supplied by sipgate. While it will still register ok with sipgate, I cannot get it to register with pbxes. Have configured the sip proxy as pbxes.org:5060.

Looking at my firewall rules, I see it do DHCP, be assigned an IP. It then talks to an ntp server, then opens two stun connections (still configured to use stun.sipgate.co.uk:10000). It never appears to get any further, and doesn't appear to even try to talk to pbxes.org.

Has anyone had any success with this device?

(I am able to connect from the same network segment to pbxes.org using a Grandstream Budgetone phone without problem).

Matt

Sniffing the packets is your best bet at this point.

After making a few changes to the netgear it now tries to register but gets back a 404.

The netgear gives user options of
telephone number and username

Looking at a tcpdump it looks like the from line reads:
From username<sip:telephonenumber@217.195.32.11:5060>

I therefore have set both to be mattelton-4201

What I then see is it trying to register from:
From:.mattelton-4201<sip:mattelton4201@217.195.32.11:5060>
Note that the - is removed from the sip: part.

Can someone confirm that this is the cause of the 404? I have tried putting the username in "s and adding a \ infront of the -, but in both cases the - is removed from the username.


............REGI
0x0020 5354 4552 2073 6970 3a32 3137 2e31 3935 STER.sip:217.195
0x0030 2e33 322e 3131 3a35 3036 3020 5349 502f .32.11:5060.SIP/
0x0040 322e 300d 0a46 726f 6d3a 206d 6174 7465 2.0..From:.matte
0x0050 6c74 6f6e 2d34 3230 313c 7369 703a 6d61 lton-4201<sip:ma
0x0060 7474 656c 746f 6e34 3230 3140 3231 372e ttelton4201@217.
0x0070 3139 352e 3332 2e31 313a 3530 3630 3e3b 195.32.11:5060>;

The missing dash (-) is definitely the problem, and the proof is the Grandstream which does not truncate it, registers and functions with your PBXes account.

Open an account with Netgear, and ask them to change that behavior of their ATA. The TA612V is a recent product, so they will most probably fix this bug.