Spark HG659b VOIP Functionality

Forums › VoIP › Spark HG659b VOIP Functionality

1 | 2 | 3 | 4 | 5 | 6 | 7 | ... | 9

836 posts

Ultimate Geek

ID Verified

Lifetime subscriber

#1183842 27-Nov-2014 09:44

ashtonaut: Awesome, I really appreciate any other thoughts or tests you could help with. The fact that the log shows a failed connection attempt makes me wonder if it's something at 2talk's end that's causing the issue. I have an open ticket with them to (hopefully) investigate.

The only other things I can think to try are 1) Create a new 2talk account with a fresh 028 number and see if I can get that working, or 2) if someone can 'loan' me account details for another VOIP provider (not 2talk) then I could try them out - if they work it would rule out a device issue.

A hiccup. We do have an HG659B at work but it's boxed up and I can't swap out the current one which is an HG659. I thought the HG659B was already in use.

However, I can take the HG659B home and have a play to see if I can get it working if needed. Might not have results today, though due to other commitments.

Samsung

Shop now on Samsung phones, tablets, TVs and more (affiliate link).

ashtonaut

614 posts

Ultimate Geek

#1183901 27-Nov-2014 10:54

Understood, thanks again for helping out. I'll be very interested to hear if you can get up and running with the 'b' model. I hope you can, because it means my issue is unlikely to be hardware specific...

If the 'b' doesn't work but the 659 does, I may need to see if I can find a 659 to swap out.

huckster

836 posts

Ultimate Geek

ID Verified

Lifetime subscriber

#1185238 29-Nov-2014 08:45

ashtonaut: Awesome, I really appreciate any other thoughts or tests you could help with. The fact that the log shows a failed connection attempt makes me wonder if it's something at 2talk's end that's causing the issue. I have an open ticket with them to (hopefully) investigate.

The only other things I can think to try are 1) Create a new 2talk account with a fresh 028 number and see if I can get that working, or 2) if someone can 'loan' me account details for another VOIP provider (not 2talk) then I could try them out - if they work it would rule out a device issue.

Ok. HG659B plugged in. All the web pages are green.

Model: HG659b
Hardware Version: VER.B
Software:V100R001C227B018
2talk works.

:-(

Off to see if I can upgrade the firmware and see if that causes a problem.
Scratch that - this appears to be the latest firmware.

ashtonaut

614 posts

Ultimate Geek

#1185240 29-Nov-2014 08:57

OK, now I'm really stumped. Why on earth is mine not working?

Same hardware, same software, same VOIP provider. I'm on a Spark VDSL connection, what are you on?

Would you mind turning on debug logging on the device and then posting whatever relevant messages regarding VOIP that you can see?

Edit: And would you also mind posting a screenshot that confirms the line status?

huckster

836 posts

Ultimate Geek

ID Verified

Lifetime subscriber

#1185261 29-Nov-2014 09:31

ashtonaut: OK, now I'm really stumped. Why on earth is mine not working?

Same hardware, same software, same VOIP provider. I'm on a Spark VDSL connection, what are you on?

Would you mind turning on debug logging on the device and then posting whatever relevant messages regarding VOIP that you can see?

Edit: And would you also mind posting a screenshot that confirms the line status?

Am on fibre. I've put the HG659 back in place as the kids were getting restless.

This is when I'm on a call, otherwise it says idle.

Not much to see in the logs....

Manufacturer:Huawei Technologies Co., Ltd.
Product Style:HG659
Serial Number:XXXXXXXXXXX
Hardware Version:VER.B
Software Version:V100R001C227B011

2014-11-29 09:27:44 System Notice Message type: Query, Querier: 192.168.Y.YYY, Group: 0.0.0.0, version: 2.
2014-11-29 09:27:40 System Notice Message type: Query, Querier: 192.168.Y.YYY, Group: 224.0.1.178, version: 2.
2014-11-29 09:27:40 System Notice Message type: Query, Querier: 192.168.Y.YYY, Group: 0.0.0.0, version: 3.
2014-11-29 09:25:43 System Notice Message type: Query, Querier: 192.168.Y.YYY, Group: 0.0.0.0, version: 2.
2014-11-29 09:25:35 System Notice Message type: Query, Querier: 192.168.Y.YYY, Group: 224.0.1.178, version: 2.
2014-11-29 09:25:35 System Notice Message type: Query, Querier: 192.168.Y.YYY, Group: 0.0.0.0, version: 3.
2014-11-29 09:24:12 User Level Notice All logs are cleared by user(admin).
2014-11-29 09:28:45 System Notice Registering with VoIP number 028XXXXXXX to Register server sip.2talk.co.nz successfully.
2014-11-29 09:28:42 System Notice User admin Update Sip Line information.
2014-11-29 09:27:33 System Notice Un-Registering with VoIP number 028XXXXXXX to Register server sip.2talk.co.nz successfully.
2014-11-29 09:27:32 System Notice User admin Update Sip Line information.

[EDIT: Wrong picture]

ashtonaut

614 posts

Ultimate Geek

#1185279 29-Nov-2014 09:51

Thanks a lot for testing this out, I really appreciate it. I have no idea why my setup is not working and yours is. I'll go back to the drawing board, perhaps a factory reset is in order.

jourdant

44 posts

Geek

#1185308 29-Nov-2014 10:47

I'm having the same on my (voda) HG659 ver b. I've tried the voda and spark firmwares with no luck.

The interesting thing however, is I could successfully register to 2talk when using a different modem and using the ethernet port on the device for the WAN connection. This would be consistent with people using UFB and being able to register successfully.

Any ideas why VOIP doesn't work over the VDSL WAN connection? Actually, does anyone have it working over the VDSL WAN connection?

ashtonaut

614 posts

Ultimate Geek

#1185321 29-Nov-2014 11:09

Interesting. I have no idea how to test this further, as the other modem I have at home is not VDSL compatible.

Does anyone with (much) more networking knowledge than I do have an idea as to what might be different about the VDSL connection that stops it from working? Perhaps there is a setting on the device that needs tweaking if you are on a VDSL connection?

I'd be interested to see if anyone can get it working on ADSL, as this uses the same physical port as VDSL. Perhaps the firmware has a bug/'feature' that will only allow VOIP registration through the ethernet WAN?

Do you get the same "registration failed" log message when it doesn't work?

jourdant

44 posts

Geek

#1185346 29-Nov-2014 12:37

I get the same response (Reason: no answer from remote station received.)

If you go into the WAN settings for VDSL, I have the following:

The VOICE box is checked, that would suggest that interface can be used for registering SIP? That's what logic tells me anyway.

It would be great if we could get some input from Spark/Vodafone on this issue since it seems to be consistent across both providers.

ashtonaut

614 posts

Ultimate Geek

#1185520 29-Nov-2014 17:40

Here is the equivalent page from my setup:

I can't see anything here that seems like it would make any difference. Like you, I also have VOICE checked by default.

A factory reset made no difference to me, but I knew that was a long shot.

ashtonaut

614 posts

Ultimate Geek

#1186476 1-Dec-2014 16:46

I hate to admit defeat, but without some input from someone 'in the know' at Spark, I'm stumped.

It appears from others' experience that VOIP works when connected to the Internet via the WAN port, but for some reason it doesn't work when connected directly via the DSL port (definitely not with VDSL, unsure about ADSL).

I can't think of any reason why this would be a deliberate restriction, which would mean that it's either some kind of device software bug, or a non-obvious configuration setting specific to the DSL interface.

I've not heard back from 2talk, but given that the SIP connection appears to work on the WAN interface I'd be very surprised if it's anything at 2talk's end - it seems more likely to be a device issue.

If any sympathetic Spark employees could chip in it would be appreciated, even if it's just to confirm that this is indeed a device limitation/restriction/bug.

huckster

836 posts

Ultimate Geek

ID Verified

Lifetime subscriber

#1186637 1-Dec-2014 21:13

ashtonaut: I hate to admit defeat, but without some input from someone 'in the know' at Spark, I'm stumped.

It appears from others' experience that VOIP works when connected to the Internet via the WAN port, but for some reason it doesn't work when connected directly via the DSL port (definitely not with VDSL, unsure about ADSL).

I can't think of any reason why this would be a deliberate restriction, which would mean that it's either some kind of device software bug, or a non-obvious configuration setting specific to the DSL interface.

I've not heard back from 2talk, but given that the SIP connection appears to work on the WAN interface I'd be very surprised if it's anything at 2talk's end - it seems more likely to be a device issue.

If any sympathetic Spark employees could chip in it would be appreciated, even if it's just to confirm that this is indeed a device limitation/restriction/bug.

I can do a test on a VDSL connection tomorrow too. If I can't get it to work, then I might know a man who knows someone etc.

No promises, but I can ask.

ashtonaut

614 posts

Ultimate Geek

#1186651 1-Dec-2014 21:37

Thanks for trying. If yours doesn't work on VDSL but does on UFB then that's pretty conclusive.

huckster

836 posts

Ultimate Geek

ID Verified

Lifetime subscriber

#1187156 2-Dec-2014 15:16

ashtonaut: Thanks for trying. If yours doesn't work on VDSL but does on UFB then that's pretty conclusive.

Yep. VDSL is a no-go. Offline. Beep-beep dial tone and logs that say.....

2014-12-02 14:15:43 System Notice Registering with VoIP number 028xxxxxxxx to Register server sip.2talk.co.nz failed: Reason: no answer from remote station received.

I have passed this onto a man who may be able to talk to a man etc.

ashtonaut

614 posts

Ultimate Geek

#1187178 2-Dec-2014 15:32

Very interesting. In summary, if you have a HG659b and want to use VOIP:

UFB (or other Internet via WAN port): OK
VDSL via DSL port: No-go
ADSL via DSL port: Unsure

Perhaps the man your man may be able to talk to could shed some light on whether this situation is a bug or a feature?

Thanks again.

1 | 2 | 3 | 4 | 5 | 6 | 7 | ... | 9