cause=28 invalid number format 1

[jallen2020]

I'm using an IPO 412v2 at 4.2.20

Why do I get this error? I'm sending the correct number of digits, do i need to outpulse aome sort of code before the ten digits?

 

[Westi]

does that happen with every call?
PRI I presume is the trunk type

Joe W.

FHandw., ACS

If you can't be good, be good at it!

 

[CarGoSki]

Find and read tech tip 212

add NI2_CALLED_PARTY_TYPE=UNKNOWN to nouser

 

[jallen2020]

Guys, thanks for your help, turns out it was a bug in the new software. Something to be aware of for 4.2.20. You will have to apply a patch to fix it.

 

[CarGoSki]

Yes the bug should be corrected by adding what I posted without applying a patch. Unless you know some specifics.

 

[kholladay]

IT IS NOT A BUG! LOL. The number being dialed IS INDEED in the "National Number" plan so the IP Office listing it as "National Number" in the setup not incorrect. Some providers, although few, don't like this and only accept numbers listed as Unknown.

Kyle Holladay
ACA-I, ACA Call Center, ACS-I, ACS-M, TIA-CTP, MCP/MCTS Exchange 2007
ACE Implement: IP Office

"Thinking is the hardest work there is, which is the probable reason why so few engage in it." - Henry Ford

 

[DMS10Tech]

Thanks for this info... ...I am fairly new to ISDN and the IP Office 500 and have been trying to get calls to go out of my PRI to a Nortel DMS-10 (only does NI2), but could not until adding the NI2_CALLED_PARTY_TYPE=UNKNOWN to the Source Numbers in NoUser. I am running 5.0.8

Also, direct line appearances for PRI don't work either, but that is not really an issue in my case.

 

[jallen2020]

Ok, I get it. Sorry, it is definitely not a bug. Makes sense now, but any thoughts or reasons as to why they want to see it as unknown? Laziness?