Gigaset C610A IP - showing registration failed

I used the username and password provided in the BYOD tab.

Here are the configuration values I used

Authentication name: BYOD Username
Authentication password: BYOD Password
Username: BYOD Username
Displayname: BYOD Username

Domain voipwelcome.com
Proxy server address: sip.voipwelcome.com
Proxy server port: 5060
Registration server: I have tried blank and sip.voipwelcome.com
Registration server port: 5060
Registration refresh time: 180 seconds
Stun: Disabled

The C610A is setup as the DMZ.

I have the Voipo provided adapter connected and active.

I installed Sipdroid and it works fine with the BYOD Username, password and server.

I would appreciate any advice on how to get my C610A working.

Thanks

Re: Gigaset C610A IP - showing registration failed

I based my initial attempt to get it working on this thread http://forums.voipo.com/showthread.p...ss-phone-setup

Re: Gigaset C610A IP - showing registration failed

make your STUN: zeus.voipwelcome.com

should fix it.

Re: Gigaset C610A IP - showing registration failed

Quote:

Originally Posted by OregonVoIP

make your STUN: zeus.voipwelcome.com

should fix it.

Unfortunately enabling STUN did not fix it.

These are the configuration settings

http://pics.2ward.com/family/c610atele.jpg

Re: Gigaset C610A IP - showing registration failed

Every time I have added a new device with voipo, I have always needed the original ATA to register at least once. This must be a security feature that whenever it sees a new device ID that it requires that the voipo ATA to register to allow BYOD access.

Re: Gigaset C610A IP - showing registration failed

Quote:

Originally Posted by biomesh

Every time I have added a new device with voipo, I have always needed the original ATA to register at least once. This must be a security feature that whenever it sees a new device ID that it requires that the voipo ATA to register to allow BYOD access.

The original ATA is active. I could not get BYOD credentials until it had registered.

Thanks

Re: Gigaset C610A IP - showing registration failed

Have you verified that all of the TCP/IP settings are correct? If the DNS server isn't correct, then it won't be able to resolve the server names.

Re: Gigaset C610A IP - showing registration failed

Quote:

Originally Posted by biomesh

Have you verified that all of the TCP/IP settings are correct? If the DNS server isn't correct, then it won't be able to resolve the server names.

Good suggestion. The DHCP provided DNS is working for everything else on my network. And the phone was able to call home and uprade itself. To double check I replaced the URLs with IP addressed. Unfortunately it still shows registration failed.

Thanks for the suggestion.

Re: Gigaset C610A IP - showing registration failed

if you are behind any type of firewall you need to disable all NAT.. just an FYI

Re: Gigaset C610A IP - showing registration failed

After a call with tech support it has been working for a few weeks (Thanks Voipo).

The solution was to only enter data in the Authentication Name, Authentication Password, Username, Domain (sip.voipwelcome.com), Proxy server port (5061) and Registration server port(5061), Registration refresh time (180) fields.

I am using two VoiPo lines with the phones. The calls are incedibly clear. I am really enjoying the phones and service.

Re: Gigaset C610A IP - showing registration failed

Unfortunately none of the suggested settings did the trick with my Gigaset A510 IP. And the "Registration Failed" message isn't really helpful either. I have a snom 370 at the office that works just fine with the BYOD settings, so it has to be specific with this phone.

Any help is appreciated.

Re: Gigaset C610A IP - showing registration failed

Mine stopped working for about a month. I believe my ISP was doing some IPv6 stuff at that time. I am curious if your 510 works at your office, assuming your office has a different internet connection.

Re: Gigaset C610A IP - showing registration failed

The Bria softphone works just fine from the same network at home. Haven't tried the Gigaset at the office. Here's a log (created by proxying through a logger) of what is happening (phone # and my public IP replaced with nines):

Quote:

Apr 19 12:35:35.128 : Recv 518 bytes from 192.168.1.38:5060 : REGISTER sip:sip.voipwelcome.com SIP/2.0 Via: SIP/2.0/UDP 192.168.1.38:5060;branch=z9hG4bKb74f75122cdc710c15 132e592aea1d0;rport From: "9999999999" <sip:9999999999@sip.voipwelcome.com>;tag=131747048 9 To: "9999999999" <sip:9999999999@sip.voipwelcome.com> Call-ID: 3573377332@192_168_1_38 CSeq: 7 REGISTER Contact: <sip:9999999999@192.168.1.38:5060> Max-Forwards: 70 User-Agent: A510 IP/42.075.00.000.000 Expires: 900 Allow: INVITE, ACK, CANCEL, BYE, OPTIONS, INFO, REFER, SUBSCRIBE, NOTIFY Content-Length: 0
Apr 19 12:35:35.175 : Recv 565 bytes from 67.228.182.2:5060 : SIP/2.0 100 Trying Via: SIP/2.0/UDP 192.168.1.38:5060;branch=z9hG4bKb74f75122cdc710c15 132e592aea1d0;rport=51088;received=999.999.999.999 From: "9999999999" <sip:9999999999@sip.voipwelcome.com>;tag=131747048 9 To: "9999999999" <sip:9999999999@sip.voipwelcome.com> Call-ID: 3573377332@192_168_1_38 CSeq: 7 REGISTER Server: Kamailio (1.4.5-notls (x86_64/linux)) Content-Length: 0 Warning: 392 67.228.182.2:5060 "Noisy feedback tells: pid=485 req_src_ip=999.999.999.999 req_src_port=51088 in_uri=sip:sip.voipwelcome.com out_uri=sip:sip.voipwelcome.com via_cnt==1"
Apr 19 12:35:35.191 : Recv 737 bytes from 67.228.182.2:5060 : SIP/2.0 401 Unauthorized Via: SIP/2.0/UDP 192.168.1.38:5060;branch=z9hG4bKb74f75122cdc710c15 132e592aea1d0;rport=51088;received=999.999.999.999 From: "9999999999" <sip:9999999999@sip.voipwelcome.com>;tag=131747048 9 To: "9999999999" <sip:9999999999@sip.voipwelcome.com>;tag=50bb2a71d 8d027d80525a88d4628ce8d.8c85 Call-ID: 3573377332@192_168_1_38 CSeq: 7 REGISTER WWW-Authenticate: Digest realm="sip.voipwelcome.com", nonce="517172750000625dd1b33d85b90bdaf14150e52a050 ccd9f", qop="auth" Server: Kamailio (1.4.5-notls (x86_64/linux)) Content-Length: 0 Warning: 392 67.228.182.2:5060 "Noisy feedback tells: pid=485 req_src_ip=999.999.999.999 req_src_port=51088 in_uri=sip:sip.voipwelcome.com out_uri=sip:sip.voipwelcome.com via_cnt==1"
Apr 19 12:35:35.222 : Recv 793 bytes from 192.168.1.38:5060 : REGISTER sip:sip.voipwelcome.com SIP/2.0 Via: SIP/2.0/UDP 192.168.1.38:5060;branch=z9hG4bK3ed9f7c885000a7034 97fce68b3ddb9e;rport From: "9999999999" <sip:9999999999@sip.voipwelcome.com>;tag=131747048 9 To: "9999999999" <sip:9999999999@sip.voipwelcome.com> Call-ID: 3573377332@192_168_1_38 CSeq: 8 REGISTER Contact: <sip:9999999999@192.168.1.38:5060> Authorization: Digest username="9999999999", realm="sip.voipwelcome.com", qop=auth, uri="sip:sip.voipwelcome.com", nonce="517172750000625dd1b33d85b90bdaf14150e52a050 ccd9f", nc=00000001, cnonce="19467c8d8b7648732e927718d862db07", response="bc3b13dd8760e23ee044eb27338c2790" Max-Forwards: 70 User-Agent: A510 IP/42.075.00.000.000 Expires: 900 Allow: INVITE, ACK, CANCEL, BYE, OPTIONS, INFO, REFER, SUBSCRIBE, NOTIFY Content-Length: 0
Apr 19 12:35:35.269 : Recv 566 bytes from 67.228.182.2:5060 : SIP/2.0 100 Trying Via: SIP/2.0/UDP 192.168.1.38:5060;branch=z9hG4bK3ed9f7c885000a7034 97fce68b3ddb9e;rport=51088;received=999.999.999.99 9 From: "9999999999" <sip:9999999999@sip.voipwelcome.com>;tag=131747048 9 To: "9999999999" <sip:9999999999@sip.voipwelcome.com> Call-ID: 3573377332@192_168_1_38 CSeq: 8 REGISTER Server: Kamailio (1.4.5-notls (x86_64/linux)) Content-Length: 0 Warning: 392 67.228.182.2:5060 "Noisy feedback tells: pid=483 req_src_ip=999.999.999.999 req_src_port=51088 in_uri=sip:sip.voipwelcome.com out_uri=sip:sip.voipwelcome.com via_cnt==1"
Apr 19 12:35:35.269 : Recv 738 bytes from 67.228.182.2:5060 : SIP/2.0 401 Unauthorized Via: SIP/2.0/UDP 192.168.1.38:5060;branch=z9hG4bK3ed9f7c885000a7034 97fce68b3ddb9e;rport=51088;received=999.999.999.99 9 From: "9999999999" <sip:9999999999@sip.voipwelcome.com>;tag=131747048 9 To: "9999999999" <sip:9999999999@sip.voipwelcome.com>;tag=50bb2a71d 8d027d80525a88d4628ce8d.380c Call-ID: 3573377332@192_168_1_38 CSeq: 8 REGISTER WWW-Authenticate: Digest realm="sip.voipwelcome.com", nonce="5171727500006260b360d59b935f6ea312663e63a46 4f721", qop="auth" Server: Kamailio (1.4.5-notls (x86_64/linux)) Content-Length: 0 Warning: 392 67.228.182.2:5060 "Noisy feedback tells: pid=483 req_src_ip=999.999.999.999 req_src_port=51088 in_uri=sip:sip.voipwelcome.com out_uri=sip:sip.voipwelcome.com via_cnt==1"
Apr 19 12:35:35.300 : Recv 792 bytes from 192.168.1.38:5060 : REGISTER sip:sip.voipwelcome.com SIP/2.0 Via: SIP/2.0/UDP 192.168.1.38:5060;branch=z9hG4bKe2228c61970337152a 49618d15dccedf;rport From: "9999999999" <sip:9999999999@sip.voipwelcome.com>;tag=131747048 9 To: "9999999999" <sip:9999999999@sip.voipwelcome.com> Call-ID: 3573377332@192_168_1_38 CSeq: 9 REGISTER Contact: <sip:9999999999@192.168.1.38:5060> Authorization: Digest username="9999999999", realm="sip.voipwelcome.com", qop=auth, uri="sip:sip.voipwelcome.com", nonce="5171727500006260b360d59b935f6ea312663e63a46 4f721", nc=00000001, cnonce="558b4afe086965f622874b18a67fcb4", response="de051414006a68ba403592baa6b96c7d" Max-Forwards: 70 User-Agent: A510 IP/42.075.00.000.000 Expires: 900 Allow: INVITE, ACK, CANCEL, BYE, OPTIONS, INFO, REFER, SUBSCRIBE, NOTIFY Content-Length: 0
Apr 19 12:35:35.347 : Recv 566 bytes from 67.228.182.2:5060 : SIP/2.0 100 Trying Via: SIP/2.0/UDP 192.168.1.38:5060;branch=z9hG4bKe2228c61970337152a 49618d15dccedf;rport=51088;received=999.999.999.99 9 From: "9999999999" <sip:9999999999@sip.voipwelcome.com>;tag=131747048 9 To: "9999999999" <sip:9999999999@sip.voipwelcome.com> Call-ID: 3573377332@192_168_1_38 CSeq: 9 REGISTER Server: Kamailio (1.4.5-notls (x86_64/linux)) Content-Length: 0 Warning: 392 67.228.182.2:5060 "Noisy feedback tells: pid=485 req_src_ip=999.999.999.999 req_src_port=51088 in_uri=sip:sip.voipwelcome.com out_uri=sip:sip.voipwelcome.com via_cnt==1"
Apr 19 12:35:35.347 : Recv 738 bytes from 67.228.182.2:5060 : SIP/2.0 401 Unauthorized Via: SIP/2.0/UDP 192.168.1.38:5060;branch=z9hG4bKe2228c61970337152a 49618d15dccedf;rport=51088;received=999.999.999.99 9 From: "9999999999" <sip:9999999999@sip.voipwelcome.com>;tag=131747048 9 To: "9999999999" <sip:9999999999@sip.voipwelcome.com>;tag=50bb2a71d 8d027d80525a88d4628ce8d.e55c Call-ID: 3573377332@192_168_1_38 CSeq: 9 REGISTER WWW-Authenticate: Digest realm="sip.voipwelcome.com", nonce="51717275000062624e30ad3b4a407b097a5b9b96e07 5d65f", qop="auth" Server: Kamailio (1.4.5-notls (x86_64/linux)) Content-Length: 0 Warning: 392 67.228.182.2:5060 "Noisy feedback tells: pid=485 req_src_ip=999.999.999.999 req_src_port=51088 in_uri=sip:sip.voipwelcome.com out_uri=sip:sip.voipwelcome.com via_cnt==1"

Maybe someone can get more from this. A similar log of a successful registration from Bria looks pretty much the same, except for the result.

Thanks