Whirlpool

Hi All,

After following the various guides around and after much head scratching and trying a few things I've got it registering and ½ working.

I can make outgoing calls...so I would have thought I'm going to get incoming calls.

These however are going to a recorded voicemail message immediately.

Have I possibly forgotten a vital step?

Thanks in advance

The PAP2 is an ATA right? Did you map the necessary ports to it?

Hi,

yes the PAP2T is an ATA.

Gave up but I thought I'd have another go.

Port mapped 5060-5061 and 16384-16482 to the pap2 on the router TPlink w8920G.
Tried putting the pap2 in the DMZ still no luck.

Both PAP2T and router have the latest firmware.

All settings are a specifie on the whirlpool guide here.

Still nothing incoming.

Outgoing continues to work..the whole thing comes up as registered.

spent about 1 hour last night on the phone with iinet and getting them to check my VOIP profile (which was rebuilt)

So very frustrated as it's likely just a small misconfiguration but just can't figure out which setting among the massive amount to change to get it to work.

Have a look here http://whirlpool.net.au/wiki/?tag=iiNetPhone_sipura2k

There is screenshots of the set up pages.

thebow writes...

I can make outgoing calls...so I would have thought I'm going to get incoming calls.

These however are going to a recorded voicemail message immediately.

Is it voicemail as in "The person you are calling is unavailable" or "The number you are calling is being upgraded to Naked DSL". If its the latter there may be a issue with the local number port processing. You'd need to call support for help in this case. Or email me and I'll have a look.

As stated previously this has already been done, set up as per the wiki pages specs.
I'll quadruple check again today just in case I've missed something.

To Daniel

I'm getting the "the person you are calling is unavailable...blah,blah,blah".
I'v had this problem for about 3 months so my line is well and truely active :-)

Well that should really be :-(

I spent about 1hr with a very helpful iinet rep on th phone wednesday night and he rebuilt my VOIP profile and tested this.

Any other suggestions????

At this stage it's looking like the tp link and lynksys to ebay and I'll buy a belkin wireless + voip. But the fact that I just can't get this sucker to work is frustrating!

By process of elimination it's got to be the router but lynksys is now in the DMZ, ports are open so I'm at a loss there.

I use the linksys PAP2T with naked dsl + voip and it works perfectly, so hang in there :P

When I get home I'll take some screenshots of my config pages to help you out if you want.

Have you disabled the firewall on the modem?

Ummm, I am hoping like I am not completely dumb but there are no firewall setting enabled by default on this( that I can see from the advanced setup menu) .

It's essentially open other than password and NAT....

thebow writes...

By process of elimination it's got to be the router but lynksys is now in the DMZ, ports are open so I'm at a loss there.
Few questions/ideas:
1. Did you try softphone operation yet? If not, then do it ASAP it will actually give you some ideas on the problem area.
2. Did you have regional settings updated for Australia?
3. Do you have a friend where you can take your PAP2 to test?
4. Did you try different modem/router? The fact you put your PAP2 in DMZ zone doesn't eliminate the router as a problem area. My Billion had problem with VOIP even though PAP2 was in DMZ as well. Only frmware update fixed the problem.
5. Did you try to use it after factory reset?

cheers

1) Getting request timeout error 408 with X-lite...so there is a problem but no freaking idea now.

2) Yep configured for regiional

3) Yep I can do that so I might go over today

4) don't have a different router unfortunately but hopefully option 3 can sort that out.

I am using the latest firmware both on router and PAP2T

5) I have not done a factory reset....

Another perhaps interesting observation.

Went to a friends place, plugged the lynksys in, it gets IP, registers and basically exhibits the same behaviour.

The router there is the iinet supplied, 4 port, wireless G router.

I did then open ports 5060,5061,16384,16482 with no change..still no incoming calls.

This is officially extremely crappy.

are you in wa?
try sa for state instead of wa
(sip.sa.iinet.net.au)
and make sure the register expire is 300

mind you it sounds like they have tested on other equipment, but i have heard of problems with wa iinet voip being fixed by these steps

Hi,

Nah..I'm in NSW.

I did try replacing nsw for vic when I was going through testing with the iinet tech though with the same non-results.

thebow writes...

I did try replacing nsw for vic when I was going through testing with the iinet tech though with the same non-results.

Have you requested that a staff member try replicate the problem on the test bench? If not I would suggest doing this as it would rule your config out as the issue.

Alright..

Got X-lite working, incoming/outgoing...

So now point of crapness has got to be the damn lynksys not router.

unsupported config so I'm very lucky I got someone interested anyway...

thebow writes...

I did try replacing nsw for vic when I was going through testing with the iinet tech though with the same non-results.

figured as much, but worth mentioning :o]

since it is now definitely it, a factory reset is worth a world of tinkering with settings, as it may have just decided something daft entirely on its own.
A firmware update (or swap) may be a good step too.. i'd do it first (and get both out of the way at once :o)