96xx call log 91 vs 9

[Sinkiller]

We have 9620 and 9630 sets that are running 3.0 firmware. The problem we have relates to calling from the call log. We have 6 digit extensions. We have 10 digit dialing. When dialing a number that is called to a set from the call log "91" is inserted. This messes up 10 digit local calling. I haven't seen anything in the text file that allows me to define the local area code. This brings up another question. We have 3 sites with 3 different area codes. If the local vs ld issues can be fixed what would be the best way to handle multiple sites.

I can delete the 1 via ars/routing however I'm hoping there is a better way.

Note: the phones are h323.

The brain is a wonderful organ; it starts working the moment you get up in the morning, and does not stop until you get to the office.

 

[phoneguy55]

If you need to keep both 10 and 11 digit dialing then you should remove the 1 in the route pattern.

 

[testLED]

you need to check the PHNLD and PHNCC settings in the 46xxsettings.txt.file.

 

[Sinkiller]

PHNLD = 1
PHNCC = 1

This site is located in Canada.


The brain is a wonderful organ; it starts working the moment you get up in the morning, and does not stop until you get to the office.

 

[testLED]

remove the 1 from the PHNLD reboot phone and test. I take it you dial 9 for a line.

 

[Sinkiller]

Local calls require the full 10 digits to be dialed. I don't see anything that would tell the system that my area code is 905 and therefore local. I'm guessing that ARS may be my only option. Hoping that someone out there has ran into the same thing and figured out a trick or two.

The brain is a wonderful organ; it starts working the moment you get up in the morning, and does not stop until you get to the office.

 

[testLED]

No but I have many time ran into the system inserting the digit that appears in the 46xxsettings file when calling back from the call log. It may be that there are ARS settings or even route pattern insertion but to me it sounds like the settings file. Does this happen when dialing the number manually.

 

[Sinkiller]

Dialing numbers manually works fine. When a user receives a call, lets say a local, or LD number we see the 10 digit number in the call log, when I place a call via the call log the system inserts 91. I was thinking that I may not be able to fix this via the settings file. I may have to add an ARS entry that looks for 1+ (the local area code) and then strip the 1 then send the call on its way.



The brain is a wonderful organ; it starts working the moment you get up in the morning, and does not stop until you get to the office.

 

[testLED]

settings file my friend....

If your PHNCC setting is 1 I'm guessing your in the US remove the 1 from PHNLD and what have you set in the PHNLDLEGNTH ?

 

[phoneguy55]

leave the 46settings.txt file alone. You want to be able to call numbers that are LD back via 9 + 11 digits. For you local ones, just add route patterns to dial what should be 7 or 10 digits but have 11 digit enties and strip the digits you don't need.

 

[testLED]

Maybe my post is not clear do not remove the PHNLDLEGNTH setting. If your ARS setting are set correctly you will not need to worry about your long distance dialed digits. The system when dialing back from call log could be striping a leading digit so it uses the 1 to make that up. I would remove this digit. If it is removed and your ARS tables are set up this will control your dialed digit length anyway.

However I agree that there is more than one way to skin a cat...

 

[tbg247]

Can we get a CM trace (list trace station) of what happens when you dial out from the call log?