Adding a 9 prefix to call log calls

[Pepp77]

Hi Guys

We have a site running an IP500 on version 5.0(8).

They use a 9 to get an outside line, however this causes a problem when they try to return missed calls from their 1600 series call log, as it doesnt put the 9 in and the call fails.

We have added a 9 to the prefix box on the ISDN line, and I have been advised by my colleague that he has also edited the settings file for the handsets to add this 9 in, but nothing seems to be working.

Any ideas would be much appreciated.

 

[Bas1234]

Check the 46xxsettings and remove the ## before SET PHNOL
Restart the phone

___________________________________________
It works! Now if only I could remember what I did...

Dain Bramaged
___________________________________________

 

[Pepp77]

Yep we have that in place - but it doesnt do anything.

I place a DDI call to a handset, it then tries to call the number back from the call log and the call comes back as INCOMPATIBLE.

 

[kwing112000]

what does the number look like before it dials? in my case i needed a prefix of 9+1 to dial back out. can you dial 9+10digits.

Kevin Wing
ACS- Implement IP Office
ACA- Implement IP Office
Carousel Industries

 

[Pepp77]

The number is shown in the call logs as a standard national number ie 02071234567.

Dialling with a 9 works fine manually, its only the actual adding of it that isnt working.

 

[IPGuru]

as you are in the uk why not just drop the requirement to dial 9? it it tottaly unnecessary.

universal plan B:
When all else fails cheat.

 

[Pepp77]

Guru - that is what we want to do but the customer wont allow it.

Also it may get around the issue but it doesn't solve it.

 

[amriddle01]

In that case add the ? . Dial shortcode so the redial works without the 9 and leave the 9N Dial N shortcode in for the users and they will be none the wiser Still masking the fault but nobody will know


ACS - IP Office Implement

"What the Crocodile Hat....was that?

 

[Pepp77]

I really do want to - but this customer is very picky and doesnt want a ? access code on the system. They will expect that as this should work it will work.

 

[Pepp77]

I have logged a case with Avaya now.

 

[amriddle01]

They will tell you to upgrade

ACS - IP Office Implement

"What the Crocodile Hat....was that?

 

[amriddle01]

Only kidding, I know you can't, it's always their first response, does this site only have IP sets? Can you test on a Dig set to see if it's the same?

ACS - IP Office Implement

"What the Crocodile Hat....was that?

 

[Pepp77]

Riddle - They asked me to add the 9 to the front of the national and international prefix boxes on the line tab. Which works - although obviously it also displays the 9 as part of the incoming number - not ideal.

Site only have 1600 series handsets but I have tested the setting here as well using my system (I have 5410s and 1616s) and it does exactly the same, ie doesnt work unless added to the national/international prefix boxes.

Response from my BP is:-

This is the way the IP Office system works and most others, if you want the call log to include a 9. I have also just spoken to Avaya engineering to clarify this is working as designed. I can raise this as a feature request if you wish?

I therefore decided to reply with:-

Chris

That seems odd then – especially as they have the section in the settings file for access code that says:-

ENHANCED LOCAL DIALING RULES ###############
##
## These settings affect certain dialing behaviors, such as
## dialing numbers from the incoming Call Log or from web
## pages


## Outside line access code
## The number you press to make an outside call.
SET PHNOL 9

What does this actually do then, as reading it it makes it seem like this is designed for exactly what we are trying to achieve.

It would be useful to be able to assign a prefix to a call log without it affecting the incoming call display, so if you could log it as a feature request that would be appreciated.

Pete

 

[Bas1234]

## Outside line access code
## The number you press to make an outside call.
SET PHNOL 9

There are spaces in fron of the SET remove them

## Outside line access code
## The number you press to make an outside call.
SET PHNOL 9

___________________________________________
It works! Now if only I could remember what I did...

Dain Bramaged
___________________________________________

 

[Pepp77]

Bas I will double check that tomorrow - although Avaya say that settings file will only work for 46/56 series phones and wont affect 54xx and 16xx handsets.

 

[Bas1234]

It will also work for 16xx
For the 54xx

add a 9 on the line;

Prefix: Default = Blank.
The prefix is used in the following ways:

• For incoming calls
The ISDN messaging tags indicates the call type (National, International or Unknown). If the call type is unknown, then the number in the Prefix field is added to the ICLID.

• For outgoing calls
For IP Office 3.2 and lower, when a outgoing call is presented to the line with a leading digit to dial that matches the Prefix, that digit is stripped from the number. IP Office 4.0 and higher does not strip the prefix, therefore any prefixes not suitable for external line presentation should be stripped using short codes.

___________________________________________
It works! Now if only I could remember what I did...

Dain Bramaged
___________________________________________

 

[Pepp77]

Bas - I have double checked the SET PHNOL 9 and ensured there are no spaces at the start of the file, and still get the same issue - the 9 is not added to call log numbers.

Looks like the only way to do this is to add a ? to the system shortcodes or have a 9 displayed on the incoming number by adding a 9 to the national/international prefix boxes.

Im wondering if it stopped working in version 5 and did work before that.

 

[jgrove03]

It has never worked and if you find a fix for it let me know.

 

[IPGuru]

You may also need to set PHNDPLENGTH
I have had this working with 56XX handsets I am not 100% sure about the 16XX

 

[TheSmash]

Long story short, the SET PHNOL setting is ignored by by the 16xx handsets. We have confirmed that with multiple systems and now with Avaya. FR?? Why should we have to request a feature that already existed??

I'm amazed it has taken us this long to notice. Maybe because of the ? SC which we have on a lot of systems.

Don't you just love Avaya sometimes....

Don't ask me, I didn't design it.