Whirlpool

Has anybody had any luck getting MyNetFone to work with Voxalot?

I signed up with them today, it registers in voxalot but when I call the DID I get an engaged tone :(

I've registered them on my Vox account and can make calls thru MNF on Vox, but I have never been able to receive MNF calls. However, I can receive calls if someone rings my PT number registered on Vox. If anyone has the solution I'd be over the moon.

It's interesting that some of the cheap no monthly fee providers work better with Voxalot than some of the more expensive VSPs.

Unless a VSP works seamlessly with Voxalot, I will not consider them. I tried IPrimus Talkbroadband, for example. I couldn't get it to work in Voxalot, so I dropped them.

CableRider writes...

I've registered them on my Vox account and can make calls thru MNF on Vox, but I have never been able to receive MNF calls.

I also have MNF and PT accounts. PT works OK through Vox but I am also getting and engaged signal with MNF. What is it that you are doing that at least allows you to make calls?

Russedw writes...

What is it that you are doing that at least allows you to make calls?

MNF requires your account to be registered before you can make calls, so on the Provider Details page for MNF, simply set SIP Register to Yes and save it. You need to wait 5-15 minutes before the registration actually happens (i.e. Status on the Provider List page will change from Pending to Registered.

This topic has sprung up in another post. Martin @ SipBroker has done some investigating. Have a look at: forum-replies.cfm?t=655413#r8

Hi Brent,

Just wondering if any progress is being made on the issue of receiving calls via Voxalot. If your engineers started testing on Monday, they may have made some progress by now.

Thanks.

Ozimarco,

We are working on this very thing tomorow.

I will keep you posted.

Brent Spargo writes...

Ozimicro

I haven't been called that before but thanks for the feedback, anyway, Brent. I have had a number of whims from other MNF users and potential users who are just as keen to see this working as I am.

Add my name to the list.

Mine too

Me too

Just a small update.

We have some information to act on, and will hopefully be implementing a fix as to what we found from next week.

And no, I will not tell you what we have found, sorry!

Good news !

I have been ringing my did every night this week in case anything happened

Brent Spargo writes...

We have some information to act on

Hi Brent I just sent your techs a break down of the problem. Hopefully it is aligned with your proposed fix.

--
Martin

Brent Spargo writes...

I will not tell you what we have found, sorry!

I though Martin had found your problem and you just need to provide a fix. Right?

I am very intrested in getting Voxalot service running with MNF

I am quite, no, extremely daunted by the voxalot setup, I have gone through most of the setup , but when it comes to setting the priorities in the call forwarding. I am going to need some help!
/me looks at Cable Rider :)

But no point right now until MNF is able to confirm sometime this week, that they have the solution discussed in this thread.
I want to be able to receive calls to my DID.

Just wondering on the progress of this?

Hi Guys,

I should be able to provide an update any day now.

Thank's for sticking with us, we are geting closer, no doubt about it.

Thank you also to Martin for the information provided, received and noted.

Brent.

Brent Spargo writes...

we are geting closer, no doubt about it

It was working for me yesterday, down again today :(

BrisbaneR33 writes...

It was working for me yesterday, down again today :(

What was working? We know that MNF is working for outgoing calls via Voxalot. It's just the incoming call issue that they are trying to fix.

ozimarco writes...

We know that MNF is working for outgoing calls via Voxalot. It's just the incoming call issue that they are trying to fix.

Are you saying even outgoing calls do not work via voxalot?

I assume your question is directed to BrisbaneR33.

Doesn't look like its going to happen chasps.

so do I take it from reading these mynetfone and voxalot threads that people have outgoing calls working but not incoming to their DID?

cos I just get an engaged tone calling out as well. Will try again tonight.

should it work if I call eg. 181 (MNF customer service) via voxalot?

I only have MNF set up in voxalot at present, registered and all ok according to the voxalot webpage, and one dial plan "_X." to send everything to MNF.

The ATA is a netcom V100S set to voxalot and it reports as successfully registered.

"should it work if I call eg. 181 (MNF customer service) via voxalot?

I only have MNF set up in voxalot at present, registered and all ok according to the voxalot webpage, and one dial plan "_X." to send everything to MNF"

I used _1xx to cover the MNF customer service numbers and this works ok - and then another plan for other numbers - Bill

randomthought writes...

cos I just get an engaged tone calling out as well.

The ATA is a netcom V100S set to voxalot and it reports as successfully registered.

I too have the V100S (supplied by MNF) and only get engaged signals when ringing out. So whatever, we both need to do the same thing...but what?

randomthought writes...

The ATA is a netcom V100S set to voxalot and it reports as successfully registered.

I also have a v100, tried yest to register it to voxalot but failed ... how did u get urs to register

And what firmware are u using with ur V100 .. is it the generic or the MNF_05 firmware

I have MNF registered in Vox but to no avail. Yes, I have the MNF_05 firmware update installed yesterday hoping for a miracle!

I think we need to watch this space for some breakthrough soon??

randomthought writes...

so do I take it from reading these mynetfone and VoXaLot threads that people have outgoing calls working but not incoming to their DID?

That's correct. Outgoing calls are working fine. MNF engineers are trying to get our DIDs working in VoXaLot. Tomorrow will be the end of the second week of testing, so I can only assume that the problem is not trivial.

If they are having so much trouble fixing it, they may have to ask another VSP for a favour. I am sure that, if they asked nicely (Oztell, for example), someone would oblige. Oztell have stated that they are not really interested in people making calls via their own system, so they would have nothing to lose by giving this information to MNF. I know that they assisted Koala last year when they were having similar problems with Voxalot and Oztell's Webdialler.

Our engineers have been working with Voxalot's engineers and we have narrowed down what the incompatibility is.

We are now working through a plan to see if we can resolve it.

This could take some time as it is complex to unravel, but we are still working on it. I will continue to update you as and when we make progress.

Thanks for your patience.

Yay! Thanks for the update Brent. Good to see the issue is not being ignored.

i_am_new_here writes...

I also have a v100, tried yest to register it to voxalot but failed ... how did u get urs to register

don't know, I just followed the instructions in the voxalot tutorial (don't forget to set your "username" in 2 places though on the SIP page on the V100S - that's what got me the first time).

And what firmware are u using with ur V100 .. is it the generic or the MNF_05 firmware

the one from MNF - there's a new one out on their website, comes as part of the PCTool thing for the V100S, so I installed that.

It has made no difference to my other problems with MNF/V100S though. The ATA appears to "hang" after a random amount of time somewhere under 1 hr. This results in no dialtone. I can't ping it either. I left the PCTool going the other day and it too becomes unresponsive. DHCP or static IP makes no difference, the device just stops responding to anything. MNF support are completely useless, the best they can offer is an incompatibility with my ADSL modem. Even if true, why this should make the device stop responding to all TCP/IP traffic is beyond me (and them obviously).

ozimarco writes...

That's correct. Outgoing calls are working fine.

hmm not for me. Haven't had another go at it yet but will over the weekend. Also intend to try it with a billion 7404 all-in-one router.

Russedw writes...

I too have the V100S (supplied by MNF) and only get engaged signals when ringing out. So whatever, we both need to do the same thing...but what?

yes that's the question.....
My impressions so far of both the V100S and MNF are not too good but we'll see.

Sorry for the late reply guys, I've been flatout at work this week and haven't had a chance to get on Whirlpool...

ozimarco writes...

What was working?

Yes, incoming calls to my DID were working via Voxalot.

BrisbaneR33 writes...

Yes, incoming calls to my DID were working via Voxalot.

so is this the 'denouement' does MNF work for incoming calls to the DID via voxalot??

bump........sorry would really like to know if the MNF DID works for incoming via voxalot.

Brisbane R33 has your connection proved stable and is any one else able to replicate??

I would like to know as well.

We haven't had notification of this from the Brent type person.

Just tried calling my MNF did which is being managed by voxalot and it was a no go. Made one USA style ring and then went engaged

boysana writes...

is any one else able to replicate??

Nope, I'm still getting the engaged tone when I dial a MNF account (not DID but should work the same way) registered on VoX, with my VoX account registered on my ATA.

Brent has given no indication to date that it has been fixed. I am sure he'll announce it here as soon as it has. MNF's engineers have been at it for two and a half weeks now, so I can only presume that it is a very difficult issue.

Well I too changed to the Whirlpool Saver Plan and find that my given DID is a complete failure...
It does not work to my VoXaLot PBX account (so it's absolutely of no use to me), and moreover, ever since my calls must be now routed through a second class server as they just do not connect and yet MYNETFONE CHARGED 10 CENTS ME FOR THESE CALLS THAT GO NOWHERE it is so bad that I've replaced MNF in my call plan with WDP (WorldDialPoint) :-(
Until now I never experienced nowhere calls.

Hi VoxMan,

As has been discussed on this forum, MyNetFone DOES work for Outbound Calls & Voxalot.

We as a company are working on inbound calls through Voxalot (3rd party service provider)

Your DID is fully functional might I add, just not through Voxalot.

Brent Spargo writes...

Your DID is fully functional might I add, just not through Voxalot.

If I can't use a MNF line attached to my PBX then I call that MNF line a non-functional line...

What is a "VoXaLot PBX account"?

hey Brent Spargo just wanted to say the hassle will be worth it to get this working.

Myself and i am sure many other whirlpool/voxalot users would be utilizing your service if incoming calls were working.
We realise the whole third party provider issues but the reality is releasing a whirlpool deal kind of comes with a prerequisite to work with these....

Brent Spargo writes...

3rd party service provider 's

I am sure you have reflected on this at some point just trying to push it into the forefront of your consciousness......... this is what we really want.

I am willing (and i am sure more others) to participate in any testing required (though not sure how much use it will be).

Regards Boyd

Q. What is a "VoXaLot PBX account"?
A. The best thing for VoIPers since sliced bread...

visit au.voxalot.com and checkout the tutorials.

I have two SPA-2102 2 line ata's, I live in 3 houses.
When I leave one I turn off tha ata, when I reach another I turn on the ata.

I use the other ata in the other two houses without a telephone line (saves $360 per year) and connect via unwired.com ($240 per year internet).

If I receive a call when moving between homes, it is recorded by voxalot and emailed to me. Also if I miss a call/too busy to answer the same happens. Voxalot also signals my ATA next time I log in and my telephones (telstra GE two line) show me that I've missed a call and that a voicemail is waiting (dial tone is also changed by the SPA-2102)...

Voxalot allows me to test my SIP between two voxalot extensions,
and I haven't even covered "Call Tarrif Plans", "10000 speed dials",
"multiple free shared did's in many countries", and MORE

Oh yes if you tell voxalot you wan't to use G729x codec (especially if your on unwired 64/32) and you connect to some hi-fi nut who wants to use G711x then Voxalot trancodes it for you (found that one out when testing with pennytel technical staff).

Otherwise it is hearsay that voxalot just does the SIP and you RTP directly.

BTW: I am a user not a rep.
I can't believe this is a "BASIC SERVICE" and it's free.

Testing is not required as MNF know the problem is in the software they comissioned..
It would be easy grep the source code to find where the 091 prefix is added...

I'm beginning to think MNF just wan't the problem to go away by blaming third parties
although I would look at it with the perspective that voxalot is the second party and MNF is one of many third parties, just hanging off my voxalot dial-plan :-)

See forum-replies.cfm?t=655413#r8

Brent Spargo writes...

MyNetFone DOES work for Outbound Calls & Voxalot.

Ah...not for me! If there has been some breakthrough, it hasn't happening for my service.

VoxMan writes...

It would be easy grep the source code to find where the 091 prefix is added...

Please don't be too hard on me if I have it totally wrong....BUT...wouldn't the Voxalot crowd just strip away the "091" you speak of and Presto!!! all is fixed....

If it does for others it must be your set up with Voxalot. Is MNF registered in Vox.?

Billy Two Hats writes...

Is MNF registered in Vox.?

Yes

VoxMan writes...
It would be easy grep the source code to find where the 091 prefix is added...

roborobo02 writes...
Please don't be too hard on me if I have it totally wrong....BUT...wouldn't the Voxalot crowd just strip away the "091" you speak of and Presto!!! all is fixed....

Really?
For ONE ERRANT VSP which is NOT RFC-3261 SIP COMPLIENT
out of the world's 10,000+?

I feel that it really is about the time for MNF management to the right thing and make the heroic decision to use RFC SIP and not MNF SIP...

I ask you, Brent Spargo,
MyNetFone Representative(s),
The demand is there... Can't you heed our plea?

VoxMan writes...

The demand is there...

Exactly how big is this demand, was there a poll somewhere?

demand here

VoxMan writes...

The demand is there...

jok11n writes...

Exactly how big is this demand, was there a poll somewhere?

Oh... About... 33.236 metres.

VoxMan writes...

Oh... About... 33.236 metres.

I take it there's not a lot of demand then

jok11n writes...

I take it there's not a lot of demand then

well it is 27.286 m higher than the world record

so given that, it is high. I think if you added the oztell WEBPABX external account, the demand it would be higher.

see the pole here.
multimedia.olympic.org/p...n_report_416.pdf

G'day Brent Spargo,

When is it going to be working?

Hi Brent,

Today is the first day of the fourth week since you announced testing had started to get incoming calls, including calls to our DID, working in Voxalot. It seems to be taking the MNF engineers a heck of a long time to get this working.

What's the reason for this delay and is there an ETR? Bear in mind that for us Voxalot users the DID is totally useless until MNF comes out with a fix.

Thanks
Mark

Or if you don't want to support it than say so.............. or

ozimarco writes...

is there an ETR?

otherwise you are just building bad will

I would simply like to use my MNF account through Vox as I don't have action on either leg... Brent!?

If you are saying you can not ring out through MNF when using Voxalot, make sure your ata is registered to Voxalot and that in Voxalot MNF is registered. Then have a look and test your dial plan.

Billy Two Hats writes...

make sure your ata is registered to Voxalot and that in Voxalot MNF is registered.

Thanks for the advice, but yes both register OK.

I can register MNF to my ATA and everything is fine including my DID ring in, but not via Vox! I want to use Vox because my ATA doesn't have dial plans and I want to also access Pennytel.

G'day Brent.

It is now the end of another week without update on this issue. I realise this is a third party application and further down the pecking list, but this is functionality that many of us desire. Just because we don't all post regularly doesn't mean there aren't a lot of us waiting for this to become functional.

If you have the time, would you please provide an update here for all to see on where MyNetFone are with this at the moment.

Regards,

Mike.

PS. Other than this problem with VoXaLot, I am very pleased with the product and thank you for making the offer available to all at Whirlpool.

What Taltosss said!

I am keen on an update to this also, and preferably a resolution.

I am also waiting to MNF through Voxalot. Looking forward to a resolution.

Just another me too post.

Russedw writes...

I can register MNF to my ATA and everything is fine including my DID ring in, but not via Vox! I want to use Vox because my ATA doesn't have dial plans and I want to also access Pennytel.

I was already using Pennytel through Voxalot and, like you, have added MyNetFone (outgoing only, no DID). Initially I tried to pass numbers starting with the country code (e.g. 612xxxxxxxx for Sydney) to MyNetFone, as I do to Pennytel. This didn't work (I got a busy tone). I modified my Voxalot dial plan to send Australian numbers prefixed with just the area code (e.g. 02xxxxxxxx for Sydney) and prefixed with 0011 plus country code for international, and found that this worked fine.

Don't suppose your problem could be similar? Have you tried the Voxalot dial plan test? What does it propose to send to MyNetFone?

Today is the end of the fourth week since MNF started working on the issue of incoming calls to an MNF account not working in Voxalot. We haven't heard anything from Brent for a while now. As Voxalot is becoming increasingly popular, it is important for VSPs to make sure their systems are compatible.

Could we please have an update, Brent?

ozimarco writes...

As Voxalot is becoming increasingly popular, it is important for VSPs to make sure their systems are compatible.

I can't imagine that it is much of their user base that would be affected though, I would be surprised if this issue was getting any sort of priority from their technicians

jok11n writes...

I can't imagine that it is much of their user base that would be affected though

its more about their potential user base

boysana writes...

its more about their potential user base

Perhaps it will encourage some Voxalot users to get a MyNetFone account, maybe some extra business in that way but what's in it for MyNetFone to make the effort worthwhile?

Maybe I don't understand the benefits of Voxalot but it seems to me to be all about getting each service to work at the lowest possible rate, great for the consumer but maybe not so good for the supplier if they are only going to be used for their cheapest product they offer, I would think they need a mix of services to be sustainable.

If there are more benefits to Voxalot for the supplier of the services then please point them out as I have read through their FAQ's etc and can't see how they would benefit.

jok11n writes...

Maybe I don't understand the benefits of VoXaLot but it seems to me to be all about getting each service to work at the lowest possible rate

That's one of the benefits. Other benefits are ENUM lookup, 13/1300 geographical number equivalent lookup, the ability to receive calls via various providers, the ability of VoXaLot users to call each other, voice mail, Web Callback and other features in the pipeline like call forwarding, etc.

As more and more people realise just how good VoXaLot is, it will become more popular. VoXaLot users won't sign up with incompatible providers. In the short term, a closed system may make more money, but I guess that those providers will eventually lose out to the likes of Pennytel, who maintain an open system.

ozimarco writes...

As Voxalot is becoming increasingly popular, it is important for VSPs to make sure their systems are compatible.

Is this MNF issue about being compatible with VoXaLot, or is it (more broadly), an issue of MNF conforming to RFC 3261 (Session Initiation Protocol)?

(I'm not thoroughly familiar enough with RFC 3261 to know. It may even be a "grey area", or something left unspecified in the RFC).

It may not be reasonable to expect a VSP to be compatible with an arbitrary third party, however it would seem reasonable for the VSP to conform to the SIP standard, if that's what's causing the problem.

e164 writes...

It may not be reasonable to expect a VSP to be compatible with an arbitrary third party, however it would seem reasonable for the VSP to conform to the SIP standard, if that's what's causing the problem.

I don't know anything about the SIP standard or RFC 3261, but I think that you are right. A large number of VSPs simply work with Voxalot without them going out of their way to make their system work with Voxalot. They must be the ones that conform to the standard.

Voxalot's Martin would probably be best qualified to explain why some VSPs do not work with Voxalot.

ozimarco writes...

That's one of the benefits. Other benefits are ENUM lookup, 13/1300 geographical number equivalent lookup, the ability to receive calls via various providers, the ability of VoXaLot users to call each other, voice mail, Web Callback and other features in the pipeline like call forwarding, etc.

I notice things on their site that are free now but will be available to premium users after the trial period, I take it this means that they will start to charge for some of this functionality, they would also be in business to make money not friends

As more and more people realise just how good VoXaLot is, it will become more popular. VoXaLot users won't sign up with incompatible providers. In the short term, a closed system may make more money, but I guess that those providers will eventually lose out to the likes of Pennytel, who maintain an open system.

They would seem to be something a bit beyond the average user, a lot of people are still getting their heads around VoIP, never mind the extra functionality possible, a whirlpool user is perhaps not representative of 'average' VoIP users, I think we are still a while away from services such as these becoming the norm (outside of this community anyway)

Section 24.2 of the SIP RFC describes in essence what needs to be done:

"The REGISTER messages associate Bob's SIP or SIPS URI (sip:bob@biloxi.com) with the machine into which he is currently logged (conveyed as a SIP or SIPS URI in the Contact header field).
The registrar writes this association, also called a binding, to a database, called the location service, where it can be used by the proxy in the biloxi.com domain."

Using this example Bob's SIP URI is his MyNetFone URI and the SIP URI in the Contact header field is his VoXaLot URI.

MyNetFone just need to store and subsequently use the URI in the Contact header field.

--
Martin

MartinB writes...

MyNetFone just need to store and subsequently use the URI in the Contact header field.

The way you explain it, Martin, the solution seems very simple, yet MNF's engineers have been at it for four weeks now and still haven't managed to make it work. It makes me wonder...

ozimarco writes...

MNF's engineers have been at it for four weeks now and still haven't managed to make it work. It makes me wonder...

Have they actually confirmed that they want this to work? I know they said they would look at it but I don't remember seeing anything saying what their preference was.

I am having problems with outgoing calls as well. I have registered my modem with voxalot and here the dial plans I tried. For all these, I get an engaged tone (however they all work well with WDP and Pennytel). Looks the problem may be with my dial plans. Can someone please check if they are ok?

10 _0[2378]XXXXXXXX ${EXTEN} MyNetFone Yes [Edit] [Delete]
20 _NXXXXXXX ${EXTEN} MyNetFone Yes [Edit] [Delete]
30 _0011. ${EXTEN} MyNetFone Yes [Edit] [Delete]
40 _04. ${EXTEN} MyNetFone Yes [Edit] [Delete]

Or, do I need to change codecs in voxalot for MNF to work properly? At the moment, it is: g729;ilbc;gsm;ulaw;alaw Host: sip00.mynetfone.com.au
Thank you.

kmpere writes...

I am having problems with outgoing calls as well.

MNF requires registration for outgoing calls to work. Does MNF show as registered in Voxalot?

jok11n writes...

Have they actually confirmed that they want this to work?

Yes, Brent has stated that they want it to work and they are actively striving towards a solution.

ozimarco writes...

Yes, Brent has stated that they want it to work and they are actively striving towards a solution.

I suspect that they need to make sure none of there clients will not be affected by any changes to there already working system

So maybe they are doing a lot of testing

I hope that it is resolved soon but i still have my pstn number it would be nice that my family in Brisbane could ring me for a local call ( all though some are starting to use VOIP )

ozimarco writes...

MNF requires registration for outgoing calls to work. Does MNF show as registered in Voxalot?

Yes. This is what it shows (other provides work)

World Dial Point xxxxxx sip.worlddialpoint.net.au Yes - [Edit] [Delete]
Penny Tel 8888xxxx sip.pennytel.com Yes - [Edit] [Delete]
MyNetFone xxxxx1 sip00.mynetfone.com.au Yes - [Edit] [Delete]

kmpere writes...

I get an engaged tone (however they all work well with WDP and Pennytel).

This is interesting because I have been having intermittent problems like this (with OZtell) as well. The other half often complains about getting an engaged tone, but it does work other times. My perception is certainly that MNF's network is not at all friendly to other networks, with incoming calls from MNF DID's confirmed as not available through VoXaLot or OZtell. This intermittent engaged tone I am seeing on outbound calls is strange though, as I would expect it to either work or not, not a bit of both.

kmpere writes...

Yes. This is what it shows

If you click [Edit] and goto the MyNetFone details page, what is "SIP Register" set to (as this value is not displayed on the list page above)?

--
Martin

kmpere writes...

MyNetFone xxxxx1 sip00.mynetfone.com.au Yes - [Edit] [Delete]

If this is a copy and paste from your setup, it would appear that you haven't got MNF registered.

Compare with my copy and paste:

MyNetFone 09XXXXXX sip00.mynetfone.com.au Yes Registered [Edit] [Delete]

Take note of the 'registered' in between Yes and [Edit]. You will have to edit MNF under Providers and enable registration. Allow about ten minutes for it to take.

edit: beaten by Martin.

ozimarco writes...

Take note of the 'registered' in between Yes and [Edit].

Nicely observed and a detail I missed - and to think I helped write this system :)

--
Martin

I see that Brent was online 15 minutes ago and has replied to this thread before. I see he has also replied to another MyNetFone thread since I respectfully asked for an update.

Brent, please provide us with some info, even if it is simply that nothing will be done. Then at least we can put this behind us and move on.

He might of missed it, whim him a link to the thread, I'm sure he'll reply once it is pointed out to him.

Thank you, MartinB & Ozimarco for your quick response. Now 'Stutus' is 'Registered'. It works!! -:)

WDP and Pennytel work without registering, but MNF must be registered.
If you guys can clarify what is the difference between Sip Registered and Not that would be good. I could not find anything in the tutorials and forum on this.

Most VSPs do not need to be registered for outgoing calls, only for incoming. If you have a DID with a VSP or you would like to be able to receive calls from other users of that VSP, you should register that VSP in Voxalot.

Hi Brent,

On the 1st of Feb you wrote:

We are working on this very thing tomorow.
I will keep you posted.

The next day, you said:

We have some information to act on, and will hopefully be implementing a fix as to what we found from next week.

On the 9th of Feb, you gave us an update:

Our engineers have been working with Voxalot's engineers and we have narrowed down what the incompatibility is.

We are now working through a plan to see if we can resolve it.

This could take some time as it is complex to unravel, but we are still working on it. I will continue to update you as and when we make progress.

Thanks for your patience.

On the 14th of Feb, another encouraging statement:

We as a company are working on inbound calls through Voxalot (3rd party service provider)

That was twelve days ago. Would it be possible to give us an update, even if the answer is no, on how the engineers are progressing? Are they still actively working on this issue or have they put it on the back burner for now?

Thanks
Mark

G'day Brent.

Please Fix it... You've been told how...

G'day Martin,

I have two extensions with VoXaLot (for my 2 line SPA-2102)...

Line 1 is set to register with my providers.
Line 1 is NOT set to register with my providers.

Line 1 shows the providers as registered,
Line 2 shows the same providers as registered too...

Why is this so?

VoxMan writes...

Please Fix it... You've been told how...

Can I suggest you try being a little less brusque. Your tone is not going to encourage Brent et al to be overly accommodating to your cause!

I also have a DID with MNF that is not very useful to me unless it works through VoXaLot, but I believe that the issue has been raised and we should do little but offer to help and wait. Other comments probably won't help our cause.

MG.

Hi all,

I understand there are many demands from Whirlpool members to get MNF and Voxalot interoperability working for incoming calls.

MyNetFone are now aware of what the issues are - thanks to the assistance from Voxalot engineers.

We have developed a fix to address the specific issue, however in order to deploy the fix it needs to pass through our testing and change management process.

This is so that we do not affect the other tens of thousands of MNF customers who are working with the current system. We need to be careful before deploying any changes to the system, so as not to affect other existing customers who do not require the fix.

The earliest this particular fix will be deployed is around early April, and we will notify the Whirlpool community closer to the date.

The point is we are working on a fix, and will deliver it when we are ready to do so.

We appreciate the patience of the Whirlpool community around this issue.

Thanks for the update Brent

Will this 'fix' also allow OZtell Web Dialer to work?

gwood writes...

Will this 'fix' also allow OZtell Web Dialer to work

What is the real difference (if any) to Voxalot?

Thanks for the update, Brent. At least now we know what sort of a wait we're in for, so I can stop holding my breath.

I am glad you're still committed to get this working.

Brent Spargo writes...

The earliest this particular fix will be deployed is around early April, and we will notify the Whirlpool community closer to the date.

Brent,

I am still testing the waters before I take the plunge with VOIP and I will go with MNF now, as you will have VoXaLot inbound around early April

Brent Spargo writes...

What is the real difference (if any) to Voxalot?

Nothing really is my guess, it is just registering from a webserver in the OZtell office not from an individuals ATA or soft phone.

In my post before it should actually be 'OZtell's external internet phone account' (so we can get our DID's working from other providers).

Let me know when you have it going and I can test it with my OZtell account.

Thank you Brent for the update.

Brent Spargo writes...

What is the real difference (if any) to Voxalot?

The "real" difference can only be determined by OZtell and VoXaLot. In principal they are similar in this function, but how they go about providing it is likely to be different in one way or another (ie, different engineers will approach the same task differently). Hopefully, the VoXaLot "fix" will work with both, but I guess we'll have to cross that bridge when we get there.

In the meantime, I also need to get to the bottom of why 50% of my outgoing MNF calls receive engaged tone, it's making it very hard to use the account with no incoming and only half outgoing...

Brent Spargo writes...

The point is we are working on a fix, and will deliver it when we are ready to do so.

We appreciate the patience of the Whirlpool community around this issue.

Thanks for the update Brent, and thanks for continuing to pursue this fix, in spite of some of the rude buggers around here :-)

I'm keeping my fingers crossed that the "fix" will also work for Oztell's Webdialer, as per a few others here... but we'll just have to see come April.

StephenH

Markovich writes...

In the meantime, I also need to get to the bottom of why 50% of my outgoing MNF calls receive engaged tone

I suggest you give our support department a call, and see if we can investigate this issue for you.

Brent Spargo writes...

I suggest you give our support department a call, and see if we can investigate this issue for you.

Yes, I will do that. The problem is certainly a strange one.

Brent Spargo writes...

I suggest you give our support department a call, and see if we can investigate this issue for you.

Not sure how successful that would be as each time I have rung regarding outbound calls, I get told that MNF don't know or support issues with VOX.

Sorry just to clarify:

We will provide as much support as possible, presuming the customers endpoint is registering directly with us.

We are not currently providing support for voxalot, however customers can configure it themselves.

My assistance to markovitch above was for him to give us a call about his MyNetFone service.

Sorry for the confusion.

Will mynetphone accept sip redirects?

What I am considering is registering the mynetphone account on the ata and redirecting all voxalot calls to the mynetphone sip address.

Will this work?

The call rates are good (I just loose my pennytel mobile call rates) so all outgoing calls can go through mnp.

XcalibA writes...

Will mynetphone accept sip redirects?

G'day XcalibA.

From a previous thread it appears they won't but there is a temporary work around until there is a fix at MNF's end. It is available here from Ruberman forum-replies.cfm?t=655413&p=2#r24

I have Optus cable and my ip address doesn't change much. I have registered my SPA3000 with MNF and use a gateway to send all my calls to VoXaLot where my dialplans are stored. I travel a lot and do this so I can access dial plans in case my wife has any problems while I'm away.

I have all my providers registered in VoXaLot and then use the Call Forwarding function there to forward all inbound calls back to my ip address. Sip forwarding won't work with MNF.

I still have a DID with Astratel and this method has been working fine for me for 3 weeks. (Until VoXaLot changed the call forwarding page structure and my info disappeared !!!).

My setup is like this on the call forward menu at VoXaLot:

sip:09xxxxxx@58.xxx.xx.xxx

I have no experience with ADSL and have no idea how long your IP address will remain static, but hope this helps you or someone else.

Anyone having issues making calls through voxalot with mynetfone? Currently getting constant engaged tone.

Hey,

I have just set up voxalot and MNF tonight and when making calls the other people can't hear me.

I have made calls within Oz and also international calls but same thing,... I can make the calls and they answer and I can hear them very clear but other end nothing!