Maintenance and Services

So we are testing the new J Series phones, I currently am testing a J179 SIP on a CM 6.3/SMGR 7.1 (Will be moving this to an Avaya Aura 8 Lab system we are building). The current load of J phone is 4.0.3.1.4

So in my testing I have noticed two things and I was wondering if anyone had also ran into these issues and what they might have done to resolve them.

Item 1. The button layout - In my test environment I have assigned the J179 as a 9611SIP in CM, given it 3 call appearances, 3 bridge appearances of another phone, and a Send All Calls. The screen is in HALF Display mode, and what is happening I have provided in the picture below:



As you see in this photo, the call appearances and bridge appearances are 2 on the left, and 1 on the right - that is not how we have it provisioned in CM (Main call appearance is 1,2,3, and the Bridge is 5,6,7), and the SAC is button 4 in CM.

So is this normal behavior for this phone? Could it be the CM 6.3/SMGR 7.1 on this load of phone? I wondering once I move this to Aura 8 if this issue will fix itself.


Item 2. So in testing this J179, I noticed that trying to dial out of the call log is a bit of a bear.

In our current environment we use H.323, 96xx phones, and have choose to go with Enbloc Dialing (Using the Call Type table in CM) opposed to the ENHANCED LOCAL DIALING RULES found in the 46xxsettings. The reason for this was simple, for some reason we could NEVER get the Enhanced Local Dialing Rules to work in the local area dial plan and our own internal dial plan as it was. It had a very hard time figuring what was a internal extension, what was local, and what was long distance. Enbloc Dialing was just way better for us.

So now I am finding that the J179 is using the Enhanced Local Dialing Rules and I am a bit puzzled on how to set this up with our current environment. We have a mixed dial plan of 10 digit and 5 digit (with a few 3 digit FAC codes thrown in for good measure). We also live in a area that our area codes can either be local of long distance, depending on where the number is going.

So with those two issues, anyone ever figure out how to make this work? Is there a better way with these J series phones? I am a bit stumped, and it's a bit frustrating to think we have to introduce phones with reduced capability.

------------------------------
James Davis
Voice and Data Senior Engineer
University of Nebraska Medical Center
Omaha NE
------------------------------

Original Message------

So we are testing the new J Series phones, I currently am testing a J179 SIP on a CM 6.3/SMGR 7.1 (Will be moving this to an Avaya Aura 8 Lab system we are building). The current load of J phone is 4.0.3.1.4

So in my testing I have noticed two things and I was wondering if anyone had also ran into these issues and what they might have done to resolve them.

Item 1. The button layout - In my test environment I have assigned the J179 as a 9611SIP in CM, given it 3 call appearances, 3 bridge appearances of another phone, and a Send All Calls. The screen is in HALF Display mode, and what is happening I have provided in the picture below:

As you see in this photo, the call appearances and bridge appearances are 2 on the left, and 1 on the right - that is not how we have it provisioned in CM (Main call appearance is 1,2,3, and the Bridge is 5,6,7), and the SAC is button 4 in CM.

So is this normal behavior for this phone? Could it be the CM 6.3/SMGR 7.1 on this load of phone? I wondering once I move this to Aura 8 if this issue will fix itself.


Item 2. So in testing this J179, I noticed that trying to dial out of the call log is a bit of a bear.

In our current environment we use H.323, 96xx phones, and have choose to go with Enbloc Dialing (Using the Call Type table in CM) opposed to the ENHANCED LOCAL DIALING RULES found in the 46xxsettings. The reason for this was simple, for some reason we could NEVER get the Enhanced Local Dialing Rules to work in the local area dial plan and our own internal dial plan as it was. It had a very hard time figuring what was a internal extension, what was local, and what was long distance. Enbloc Dialing was just way better for us.

So now I am finding that the J179 is using the Enhanced Local Dialing Rules and I am a bit puzzled on how to set this up with our current environment. We have a mixed dial plan of 10 digit and 5 digit (with a few 3 digit FAC codes thrown in for good measure). We also live in a area that our area codes can either be local of long distance, depending on where the number is going.

So with those two issues, anyone ever figure out how to make this work? Is there a better way with these J series phones? I am a bit stumped, and it's a bit frustrating to think we have to introduce phones with reduced capability.

------------------------------
James Davis
Voice and Data Senior Engineer
University of Nebraska Medical Center
Omaha NE
------------------------------

I found that same issue concerning the button line-ups when setting up our J-series phones.  What I found was that the numbering jumps back and forth between the left and right side.  The left side of the screen is 1,3,5,7 and the right is 2,4,6,8.  This is normal behavior.

------------------------------
Nicholas Blum
South Sound 911
Tacoma WA
253-2874888
------------------------------

Original Message:
Sent: 01-08-2020 10:03 AM
From: James Davis
Subject: J100 Series button line up and the Call Log

So we are testing the new J Series phones, I currently am testing a J179 SIP on a CM 6.3/SMGR 7.1 (Will be moving this to an Avaya Aura 8 Lab system we are building). The current load of J phone is 4.0.3.1.4

So in my testing I have noticed two things and I was wondering if anyone had also ran into these issues and what they might have done to resolve them.

Item 1. The button layout - In my test environment I have assigned the J179 as a 9611SIP in CM, given it 3 call appearances, 3 bridge appearances of another phone, and a Send All Calls. The screen is in HALF Display mode, and what is happening I have provided in the picture below:

As you see in this photo, the call appearances and bridge appearances are 2 on the left, and 1 on the right - that is not how we have it provisioned in CM (Main call appearance is 1,2,3, and the Bridge is 5,6,7), and the SAC is button 4 in CM.

So is this normal behavior for this phone? Could it be the CM 6.3/SMGR 7.1 on this load of phone? I wondering once I move this to Aura 8 if this issue will fix itself.


Item 2. So in testing this J179, I noticed that trying to dial out of the call log is a bit of a bear.

In our current environment we use H.323, 96xx phones, and have choose to go with Enbloc Dialing (Using the Call Type table in CM) opposed to the ENHANCED LOCAL DIALING RULES found in the 46xxsettings. The reason for this was simple, for some reason we could NEVER get the Enhanced Local Dialing Rules to work in the local area dial plan and our own internal dial plan as it was. It had a very hard time figuring what was a internal extension, what was local, and what was long distance. Enbloc Dialing was just way better for us.

So now I am finding that the J179 is using the Enhanced Local Dialing Rules and I am a bit puzzled on how to set this up with our current environment. We have a mixed dial plan of 10 digit and 5 digit (with a few 3 digit FAC codes thrown in for good measure). We also live in a area that our area codes can either be local of long distance, depending on where the number is going.

So with those two issues, anyone ever figure out how to make this work? Is there a better way with these J series phones? I am a bit stumped, and it's a bit frustrating to think we have to introduce phones with reduced capability.

------------------------------
James Davis
Voice and Data Senior Engineer
University of Nebraska Medical Center
Omaha NE
------------------------------