NetComm NF13ACV funky dialplan

Forums › VoIP › NetComm NF13ACV funky dialplan

ballistyx

44 posts

Geek
+1 received by user: 1

#228582 12-Jan-2018 21:03

I thought I was getting a good deal when I bought my new router with built-in voip port, but it took a conversation with netcomm's helpdesk to get my voip (2talk) to register.

Silly me, I was under the assumption that dialplans were a standard syntax, and the one I'd been using on my PAP2T would be fine. Nope - it wouldn't even register the account. It turns out that Netcomm (or this router in particular - I've seen several different syntax for their hardware's DP) doesn't support . (dot) as a wildcard for number of digits, and doesn't support a leading * as they claim that star codes are natively supported and configured by the router, so my voicemail is inaccessible as I can't dial *55.

The nice guy at netcomm did send me a basic DP that at least got the account registered, but I can't dial 027xxxxxxx or most other mobile numbers - my call record shows only 6427, so it completely ignores all following digits. Funnily enough, I did get through to 022xxxxxxx, yet 022 doesn't even exist in the DP!

Has anyone got this model with an NZ DP that works reliably?

I'll post back if I come across a combination that does it for me!

Ah, the idyllic rural life . . .

no cellphone reception
no UHF TV reception
no ADSL

I'm surprised I still have my sanity!

chevrolux

4962 posts

Uber Geek
+1 received by user: 2638
Inactive user

#1937886 12-Jan-2018 21:32

So firstly, I really struggle to see how a dial plan would stop the line registering. Unless there is some sort of bug.

And secondly, I can't imagine the sip stack (broadcom something) in these is different to that of the nf4v. Which definitely can match *xx for a feature code like *55. And also uses . for one or more character matches.

The funny one is wait is a T unlike the standard "S1, s2 etc"

Post your current dial plan and let's see what it looks like.

ballistyx

44 posts

Geek
+1 received by user: 1

#1937892 12-Jan-2018 22:06

Here goes:
I had this on my PAP2T;

([2-9]xxxxxx|0[34679][2-9]xxxxxx|0210xxxxxxx|021[12]xxxxxx|021[3-9]xxxxx|02[0279]xxxxxxx|0240xxxxxx|0240xxxxxx|024[1-9]xxxxxxx|0282[4-5]xxxxxx|050xxxxxxx|070xxxxxxx|080xxxxxxx|00xxxxxxx.|01[08]|017xx|12[356]|[19]11|*55|023xxxxxxxx|01[1234569]x.|02[56]x.|028[013456789]x.|0282[0123467890]|0282[01236789]|05[1-9]x.|08[1-9]x.|0[34679][0-1]x.|1[03456789]x.|11[023456789]x.|12[0124789]x.|*[012346789]x.|*5[012346789]x.)

and the netcomm guy (sort of) translated that to;

111|00*x|02[014789]x*|0[3679]xxxxxxx|0508x*|0800x*x|[2458]xxxxxx

which at least registered, but as you can see, doesn't really account for all NZ calls.

I couldn't understand why it would prevent it registering, either, but that's how it happened. As soon as I rebooted with the second DP, it hooked up immediately. Obviously, the leading parenthesis could create a hiccup, and as I say, it wouldn't recognise a leading * or any period. Apparently, if it can't deal with the DP, it just won't register. Silly machine.
I've written one that might do the job, but I've never done it before, just using other people's plans;

Again, it doesn't cover everything, but I never use operator numbers, and I've ignored the 02* ones I never plan on using. I can't test that until the rest of my network users have gone to bed as I don't want to cut them off if they're in the middle of something!

Yeah, things that might work on the NF4V don't seem to be compatible with the NF13, which is why I am lamenting the lack of standardised DP syntax :)

Ah, the idyllic rural life . . .

no cellphone reception
no UHF TV reception
no ADSL

I'm surprised I still have my sanity!

ballistyx

44 posts

Geek
+1 received by user: 1

#1938813 14-Jan-2018 22:39

So far, so good.

seems to be getting through to the numbers I am dialling.
I messed up a bit in my original post, getting the . & * mixed up re wildcards, but even so, my PAP2T plan was the reason it wouldn't connect, according to Netcomm.

It's a really basic DP, but it does leave out what I consider irrelevant rules such as 070xxxxxxx and operator codes. I still haven't set up an international rule, but I'll cross that bridge if I ever need to dial out of the country :)

Ah, the idyllic rural life . . .

no cellphone reception
no UHF TV reception
no ADSL

I'm surprised I still have my sanity!

sbiddle

30853 posts

Uber Geek
+1 received by user: 9996

Retired Mod

Trusted

Biddle Corp

Lifetime subscriber

#1938840 15-Jan-2018 07:54

chevrolux:

And secondly, I can't imagine the sip stack (broadcom something) in these is different to that of the nf4v. Which definitely can match *xx for a feature code like *55. And also uses . for one or more character matches.

This is a totally different chipset to other Netcomm routers. I got a few of these from Netcomm for testing and while they're a good unit performance wise they're totally different to the NF4V and NF18ACV.

Netcomm only bought a small quanity of these into the country and won't be bringing in any more.