T Com (T-Mobile) TC 300 - Configuration Issues

[shmuel]

I recently received a new WiFi SIP phone form my Internet Service Provider Ya.com a division of T-Mobile International. It's called the T Com TC300 (T Com is T-Mobile International's operating name in Germany).

The phone is interesting because it allows the use of a GSM network through the use of a SIM card as well as a SIP account through it's integrated software.

Unfortunately I am having a lot of trouble getting this phone to connect with my Broadvoice account. The phone has the following SIP settings available: Username, Password, eMail-Address (sic.), Domain name, Local port, Proxy server, Proxy port, Register server, Register port, Register period, Outbound server, Outbound port, RTP audio port, RTP pkt. period, and Preferred codec. Currently I have these set as follows:

Username: 616XXXXXXX (my broadvoice number)
Password: ********** (my broadvoice password)
eMail-Address: I've tried this with simply my number, 616XXXXXXX@sip.broadvoice.com, and empty.
Domain name: I've tried this with both sip.broadvoice.com and simply broadvoice.com
Local port: 5060
Proxy server: I've tried this with both proxy.nyc.broadvoice.com and simply sip.broadvoice.com
Proxy port: 5060
Register server: sip.broadvoice.com
Register port: 5060
Register period: 3600
Outbound server: I've tried both proxy.nyc.broadvoice.com and proxy-nyc.broadvoice.com
Outbound port: 5060
RTP audio port: 30000
RTP pkt. period: 20
Preferred codec: G.711U

I can then check the menu labeled SIP Status. Most frequently I see the error "Authentication fail" (sic.) but if I set outbound server to proxy-nyc.broadvoice.com I get the error "Server no response".

This indicates to me that when I am getting "Authentication fail" the server is in fact responding. This is corroborated by my network traffic log. Here's an example of two packets I got back from Broadvoice.

Packet received at 1178901978.451460
UDP packet from 147.135.20.128:5060 to 10.0.0.60:5060 (295 bytes)
IP Header:
 Version: 4; Header Length: 20; TOS: 0; Packet Length: 323
 Identifier: 1367; Do Not Fragment; Fragment Offset: 0
 Time To Live: 251; Protocol: 17; Header Checksum: 50959
UDP Header:
 Packet Length: 303; Checksum: 35666
Data:
SIP/2.0 400 Bad Request
Call-ID: 220898881022313@sip.broadvoice.com
CSeq: 1 REGISTER
From: <sip:616XXXXXXX@sip.broadvoice.com>;tag=0-24565
To: <sip:616XXXXXXX@sip.broadvoice.com>
Via: SIP/2.0/UDP 10.0.0.60:5060;branch=z9hG4bK29072;received=87.218.220.75;rpo
rt=1024
Content-Length:    0

Packet received at 1178901995.101877
UDP packet from 147.135.20.128:5060 to 10.0.0.60:5060 (295 bytes)
IP Header:
 Version: 4; Header Length: 20; TOS: 0; Packet Length: 323
 Identifier: 1368; Do Not Fragment; Fragment Offset: 0
 Time To Live: 251; Protocol: 17; Header Checksum: 50958
UDP Header:
 Packet Length: 303; Checksum: 29522
Data:
SIP/2.0 400 Bad Request
Call-ID: 220898882637117@sip.broadvoice.com
CSeq: 2 REGISTER
From: <sip:616XXXXXXX@sip.broadvoice.com>;tag=0-42908
To: <sip:616XXXXXXX@sip.broadvoice.com>
Via: SIP/2.0/UDP 10.0.0.60:5060;branch=z9hG4bK54495;received=87.218.220.75;rpo
rt=1024
Content-Length:    0

Traceroute reveals that 147.135.20.128 is obviously Broadvoice and as you can see the packet is making it back through the NAT to my device which is at the local IP 10.0.0.60 (I currently have it in the DMZ to ensure roundtrip traffic as I test).

There must be more detailed log information at Broadvoice's end regarding the exact type of authentication error I am encountering as the SIP server is obviously responding with a 400 Bad request error but the staff are either ignorant of or unwilling to look at these log files for me.

I should also note that the phone also allows setting two so called "NAT settings": RPORT (enable/disable) and STUN which if enabled allows me to set: Server address, Port number, and Refresh period.

I currently have RPORT enabled but not STUN but as far as I can tell from watching the network traffic (and I could be wrong) this doesn't seem to be an issue with NAT traversal as the packets seem to be making it back to the phone. The problem seems to be with the fact that the server is responding with the above error.

Also, I have the built in WAP browser working fine over the WiFi connection which I suppose adds to the confirmation that my WiFi connection is working and that network traffic is happening.

Any one have any ideas what else I can try to get this phone up and running with my account?

Thanks,
Samuel

[chavonbravo]

Did you manage to get this working? If so, what settings did you end up using?

[woprr]

hi Shmuel,

You're wasting Your time.

With original Firmware this Phone is IETF SIP incompatible and mostly only usuable on T-Com/T-Mobile and in Your case Ya.com hotspots.

But You can use the Pirelli Firmware publicly availlable on sipgate.de -> "Hilfe-Center" -> Pirelli -> Software, there are 2 downloads.

The guys from ip-phone-forum.de have partly reverse engineered the firmware so You can add extra features like 5 SIP profiles.

But be aware You will loose any Warranty on upgrading to Pirelli Firmware and the upgrade process maybe complex and can give errors due to buggy usb drivers and maybe even kill Your phone.

y
woprr

[mrjmwalker]

You may want to check out this link: http://fonosip.com/english/tcom300.html