OpenStage Phone Localization

[LoPath]

Has anyone been successful in getting the locality/canonical dial settings working right in the USA? I'd really like to get the phones setup right so I can just click from the call log and dial a number - like it's supposed to work! All of the examples I've seen have been for Germany.


LoPath
Maintain HiPath 4000 V5 & V6, OpenScape Xpert V4, Xpressions, Contact Center

 

[donb01]

I have been researching this exact same problem for years. I suspect the clue can be found in the DLS server, but I have not yet discovered the clue. I understand the concept, but not how to make it do what I want. If I ever solve that problem I will be a hero, because then I can import their outlook contacts into the OS Manager app and they will actually be able to dial them (like I was told I could before we bought the system)!!

Don Bruechert, Voice Comm Analyst II
CareTech Solutions @ Holy Family Memorial
Manitowoc, WI, USA

 

[sbcsu]

Is there a parameter called 'Minimum local number length'
If so then it needs to be filled in

 

[sbcsu]

CP 600. Wrong call log entry if Canonical dial Settings are filled. KBA00089093
Detailed Problem Description and Symptoms:

OpenScape DP CP 600. Wrong call log entry if "Canonical dial settings" are filled as in Openstage.
497111238917 calls 497111238914 we get the entry +497118914. We expect only 8914.
497111238917 gets a call from 497111398918 we get the entry +497118918. We also expect 8918.
An Openstage with the same settings show only the subscriber as we expect.
Problem Validation/Isolation Actions / Other Notes:
With DP CP you have to fill the Parameter "Minimum local number length"

Local country code 49
National prefix digit 0
Local national code 711
Minimum local number length 5
Local enterprise node 123
PSTN access code 0
International access code 00
Operator codes
Emergency numbers
Initial extension digits


Permanent Solution:
With DP CP you have to fill the Parameter "Minimum local number length

 

[LoPath]

The call log shows up just fine. The problem is dialling from the call log. Example: Incoming call displays as 4025551212. I need the phone to dial 94025551212 or 914025551212 if 402 is not a local area code. If tried understanding the phone instructions and the DLS instructions. Both are vague and give German examples.

LoPath
Maintain HiPath 4000 V5 & V6, OpenScape Xpert V4, Xpressions, Contact Center

 

[sbcsu]

If this is on a HiPath 4K do you get the correct number on the screen on an incoming call including the 9 for a line prefix ?

 

[donb01]

No, when the call comes in (on our PRI) the phone just displays the 10 digits, and that's how it goes in the call log. You have to find a way to prepend the 9 and 1 when you are dialing from the call log or phone book. I can see in the docs there SHOULD be a way to do that, but I can't figure it out, and some pretty gifted instructors don't know either. Once I know what to do I can make a DLS template and push it out at least to the executives. If I figure it out for the call log the same thing should work for the phone book.

Here would be my goal - "forget the local area code stuff. If you have 10 digits automatically put a 9 and a 1 at the beginning before you send the number to the PBX for dialing". There has to be a way to do it!


Don Bruechert, Voice Comm Analyst II
CareTech Solutions @ Holy Family Memorial
Manitowoc, WI, USA

 

[sbcsu]

If your exit code (9 or 0) normally is missing then
REG-KNPRE;

If no entries there then run in the following
Using 011 as International Access code and 9 for a line
Using 1 as Long Distance Code

ADD-KNPRE:0&&15,ISDN,INTERNAT,9,011;
ADD-KNPRE:0&&15,ISDN,NATIONAL,9,1;
ADD-KNPRE:0&&15,ISDN,SUBSCR,9,;

 

[donb01]

I do not have any entries for that information on my system.

This sounds dumb, but since I know nothing about this topic is there any risk that by adding the entries you have outlined above I will cause any failures of the normal ability to dial out from the system?? If I screw it up I have no idea how to revert it, other than assuming it would be some version of DEL-KNPRE ) I really want to just jump in and try this, but I'm in the middle of a voicemail server upgrade and I don't want to crash the PBX because I'm bored while I'm waiting!! )

Thany you for your attention!

Don Bruechert, Voice Comm Analyst II
CareTech Solutions @ Holy Family Memorial
Manitowoc, WI, USA

 

[sbcsu]

KN is short for KNOTEN, in HiPath that means Node. (In German it means the word Knot)
KNPRE is Node Prefixing.

All of the systems that I have setup have these entries added with no affects on outbound dialing except that when it is added then a missed call can be dialed back straight away.

There are other KN AMO's to consider for further modifications however they are less straightforward and are not needed for this feature.
KNDEF - Node Definitions
KNMAT - Node Matrix
KNFOR - Foreign Nodes
KNTOP - Node Topology


TO DELETE KNPRE:
DELETE-KNPREPLN=0&&15,NPI=ISDN,TON=INTERNAT;
DELETE-KNPREPLN=0&&15,NPI=ISDN,TON=NATIONAL;
DELETE-KNPREPLN=0&&15,NPI=ISDN,TON=SUBSCR;

 

[sbcsu]

Please Don let me quote you:
I'm usually not negative on here, but.... my sphincter clenches in anticipation of what comes next.....

 

[donb01]

Not sure if the quote applies to the voicemail upgrade or something else, but it's always appropriate!

I will try this Monday if I don't have a whole inbox full of stuff. The voicemail upgrade went what I could consider to be well - the actual upgrade (and the upgrades to the upgrade) only took about 70 minutes. The other 3.5 hours was waiting for the 248 windows updates to finish up! I kicked that off around Noon so they would all be installed by 930 when I planned to start with the first reboot, and then once I rebooted it took about 3 hours and 3 more reboots to finish. Then a half hour later it told me there were another 107 waiting... According to one of the IT guys, I guess I set the record for a server having 400+ windows updates that hadn't been applied yet! )

Don Bruechert, Voice Comm Analyst II
CareTech Solutions @ Holy Family Memorial
Manitowoc, WI, USA

 

[MerlinJ]

Don,
Did it work for you?

 

[donb01]

No, sorry. I messed around with it for a while, but entering those parameters didn't seem to change anything. Most of my studying has been in the DLS manuals because there is a whole section on Canaonical Dialing, but I haven't made any progress (

Don Bruechert, Voice Comm Analyst II
CareTech Solutions @ Holy Family Memorial
Manitowoc, WI, USA

 

[sbcsu]

Hi Don - Happy New Year !
You need to check with your carrier/provider.
It works everywhere else !

 

[donb01]

You can get your phone to automatically append a 9 and a 1 to the 10-digit number that is in the call log, or the phone directory and all you have to di is push "dial" on the number on the phone?? How is that carrier related? The dialing rules for our system require the 9 for an outside line, and the 1 if it is a 10-digit number, but the system does not send that out to the provider - it only sends the 10 digits. The system refuses to dial the 10-digit numbers that are in the call log or the directory because they are not properly formatted. Because my area code is "920" the system strips off the first 9, and then the number is no longer in the proper format to be dialed by the carrier.....

There is a bunch of stuff in the docs about using canonical dialing to get the system to prepend or append digits to the number in your call log before it tries dialing it, but I can't figure out how to make it do that....

I fiddle with it for a while and then have to go back to the stuff I'm supposed to be doing! )

Don Bruechert, Voice Comm Analyst II
CareTech Solutions @ Holy Family Memorial
Manitowoc, WI, USA

 

[sbcsu]

The carrier can send the call in to the system with different identifiers.
International, National & Subscriber (Local)
If they send them in correctly and you have the KNPRE filled in then it should work, it works for me.
Outbound is different again and you can change that separately but the KNPRE is for digit prefixing only.

 

[sbcsu]

Also you can do a trace on your incoming circuits to see what NPI (Network Plan Identifier) they are providing for various calls (if any)
That would assist you in setting up the KNPRE for to prefix the numbers on the screens.

 

[donb01]

I know I added all the KNPRE stuff after you posted it. None of that stuff was there when I looked and it is now, but nothing has changed. If I choose a number off the call log such as 920-123-4567, it uses the 9 to grab an outside line and then I assume it outdials the 20-123-4567 and that generates the CO message that I must first dial a 1 or a 0 when dialing this number. Even if it sent the whole 10-digit number there would still need to be a 1 at the beginning. It's just coincidental that my area code starts with a "9". If I have a 10-digit number like 708-262-1234 then if I tried to dial the number I would end up at extension 7082, because without the 9 at the beginning it would not know it was supposed to go outside, so it would just make an extension out of the first 4 digits if that extension existed.

I have been half inclined to try and create an LDPLN of NXX-XX-XXXX that had an ODR of OUTPULSE 9, OUTPULSE 1, ECHO ALL or something stupid like that just to see if I could get it to dial out from a bare 10-digit number. I suspect that would be too easy though P

Don Bruechert, Voice Comm Analyst II
CareTech Solutions @ Holy Family Memorial
Manitowoc, WI, USA

 

[donb01]

Using the call log as an example, I understand that gets populated with what the phone company sends to us, which visually I can see is a 10-digit ISDN/NATIONAL number, or if the call was internal it puts in a 4-digit extension which I CAN call back. If the caller was a local caller the number string always gets populated with the full 10-digit ISDN number, which is exactly how I would want it to behave, because eventually 10-digit dialing will be mandatory for all calls. But now let's think about the phone's own directory - if I go in to the Openstage Manager utility and use that to import my contacts list from outlook into the phone book it will fill with 10-digit numbers if that is how the user created them in Outlook. In that case the phone company has had no play in how the number got there. The phone still needs to be told "If you have a 10 digit number then add a 9 and a 1 at the beginning"; "If you have a 7-digit number then add a 9 at the beginning"; "If you have a 4-digit number then dial as entered". I have read in the book that is exactly what the canonical dialing rules are supposed to do, but the stupid book does not present any examples of how that string or set of rules is supposed to look, or how you are supposed to create the rules - it basically just says "OK, you can use the canonical dialing rules to add digits at the beginning or end of your number" - but doesn't give you a clue HOW to do it! (in the true German fashion....)


Don Bruechert, Voice Comm Analyst II
CareTech Solutions @ Holy Family Memorial
Manitowoc, WI, USA