VOIP etc > Voice Over IP - VOIP > VOIP Tech Chat > [Other] HKBN 2b PAP2 config

[Other] HKBN 2b PAP2 config

Try the following thread:

»Re: [BroadVoice] Calls to Hong Kong are down

Additionally, there are threads about this subject on voxilla.com and www.voip-info.org.

Just search for "Hong Kong Broadband" or "HKBN".

See ya...

d.c.

reply to helloagain
Yes, it is possible to setup your PAP2/Sipura to use HKBN VOIP. Just follow the two links provided by im_chandave. Post back here if you have questions.
--
**Students are the CUSTOMERS of teachers** »RateMyProfessors.com

I followed the steps and now I can make outgoing calls with no problems. But incoming calls will be terminated once I p[cik up the phone. Any idea how to resolve that problem?

i guess everyone using pap2 or sipura 2000 facing the same problem

Since yesterday, I cannot login to the HKBN with my PAP2. Anyone having the same problem?

Thanks a lot. resetting my account solves the problem. Will you be able to get incoming calls on your asterisk box? I am not able to get incoming calls on the PAP2.

chandave, you are so mighty, thanks

Just trying to help as best as I can. Now if only I can get HKBN to credit me a couple of months for the extra Tech support I've been doing on their behalf...:D

See ya...

d.c.

HI. just wanted to post my findings using PAP2. I tried im_chandave's recommendations, reset from 2b and power cycle PAP2. Unfortunately, it did not work. But I think I can narrow it down. I tried to use 2b softphone and when i try to make a call, the password screen keeps appearing even after putting in my correct password. I called 2b tech support and the nice chinese girl asked me to turn off my firewalls. I'm on xp so i turned it off. I pinged 2b and was unable to connect. Turned out to be my router. I have Netgear VPN and i beleive it's blocking my connection to 2b.
I've already changed SIP NAT support parameters to YES and enabled STUN. But no good.

My SPA-1001, SPA-2000 and PAP2 are working fine with my D-Link DI-624 router. I don't have to make any port forwarding. It picked up my network automatically.
--
**Students are the CUSTOMERS of teachers** »RateMyProfessors.com

reply to cplus
Pinging s21.hkbntel.net will not work. They do not respond to ping packets.

If you turn on STUN and set "STUN Test Enable" = "yes", what type of NAT does your PAP2 say you are behind?

See ya...

d.c.

reply to helloagain
For those of you that want to test your HKBN configuration, I've setup an echotest on my HKBN phone number. You can call into it and it will start the echotest. With the echo test, you can check to see if you have two-way audio for your outgoing calls.

It also has the option for a callback to your HKBN phone number so you can test receiving calls.

IM me and I'll give you access.

See ya...

d.c.

reply to helloagain
I am also having troubles with 2b hkbn, I have gotten callpacket and stanaphone to work fine. I have changed all the stun paramaeters and the nat. The messages I have seen is 'Can't connect to login serve', also I setup a syslog server, so I can send over the logs if they are helpful. The only thing I have never seen is the Symmetric RTP parameter in my pap2. Do I need to flash my pap2 to a certain version, I am currently using 3.1.3? Also I have gotten the 2b softphone to work fine without any problems. Last question, I have not changed any port forwarding on my firewall/router, do I need to change anything to make pap2 work, while the software somehow resolves itself?

Thanks for any help

reply to helloagain
Just want to add my experience and comment and this.

PAP2 3.1.3: I cannot find the Symmetric RTP selection either. I don't know if there is a newer firmware out there or not, I haven't tried looking for one though.

But chandave said the NAT by STUN should have "bypassed" this requirement, but to some (could be all?) of us, it doesn't.

I have also noticed something more about this, that it has not been mentioned yet (should I also post on Voxilla so my information gets out more?).

My friends alerted me to this particular problem, so this is happening to more than 1 person. Here is the description of the problem:

When a called is received by PAP2, via 2b service, then if the call can be received successfully depending on where the call originates. If the call comes from another 2b number, then the call will go through, and everything will be fine. If the call comes from other lines, even the Citi-Telecom Canada's VoIP service (which is a subsidiary / sister company of HKBN), then the call will get dropped right after the call is received. Caller ID is passed, and I can see my friend's Caller ID no problem.

My friend and I have attempted to put it directly on the Internet (no NAT in between, true routable IP from our ISP), and it's the same. For me,I have changed use NAT to "NO", and it's the same.

Now this is more interesting: I also have a DTA-310 around, running BV8051S, so i put 2b on it, and it works. Not only that, it works without above problem, behind a Linksys BEFVP41 router (no special config here) (it has a diff. problem, pertaining to doing DHCP w/ a ParkerVision router, but nothing to do with this). I tried calling from an outside line (Xpresscall LD service), and it gets through fine. I couldn't find a Symmetric RTP entry on the unit, but of course, it could be a built in feature?

I'm just starting to get my Asterisk server going, but having some problems with configuration, so it's not working yet. I'll test it out more when I get it going.

Another unrelated problem from my friend, is that 2 of his accounts, cannot get registered with 2 diff. PAP2 units, while using 2b software client, it works fine. Yes, we did the reset on the PA web portal. I then put my account info on, and it registered immediately. We wonder if newer acquired accounts have some detection routine built in? (I haven't put the Nortel blah blah info on the PAP2 yet, b/c I don't quite see why they just don't block all non Nortel agents, if that's the issue.)

I also own a Sipura 3000, but it's at a diff. location, but I'll try to see if this one works out better.

So I hope my info helps chandave and others to figure out the problem.

fortissimo, for your friend's problem, according to chandave's recommendation they need to go to »pa.2b.com.hk/login.jsp and unregister the first client before register another.

Thanks for your reply, but if you did read my post, I already said that " Yes, we did the reset on the PA web portal.", and that it didn't work for me (and my friend told me he also did that too). I'm quite sure what you said about "unregistering the client" means the same as "reset button on the portal", right?

reply to helloagain
If you can't find the "Symmetric RTP" option then it might be that the firmware doesn't have it. On SPA-3000, the option is there but it looks like SPA-1001 and SPA-2002 (PAP2 equivalents) don't have it.

For those of you still having incoming audio problems, would you please try "Line 1 > SIP Settings > Restrict Source IP" = "yes". Some of the syslog files sent to me have private IP addresses for the "Contact:" header. Additionally, the SDP also had private IP addresses instead of the public IP address.

Would someone with incoming call problems be willing to PM me an HTML dump of their PAP2's configuration? I would like to compare the parameters between a PAP2 and the SPA-3000.

Additionally, for those of you with PAP2's and the audio problem, was the PAP2 an unlocked Vonage unit or a virgin PAP2-NA?

See ya...

d.c.