i2050 Keep DN Alive 1

[option11newby]

Hi all,

We have a BCM400 (3.6) and all the latest patches.
We have a problem with the i2050 softphones. They are set to keep DN alive. This is okay for 24 hours, but if the end user has not logged in after 24 hours, when you dial their extn it shows not in service.

Is this anything you guys have come across?

Thanks

 

[3Sixty]

When you say they get not in service what where you hoping to get voicemail or something.The keep alive I think is do with the system remembering the extension number and saves the user having to login everytime they start there IP phone.

 

[biv343]

Keepalive is supposed to make the i2050 appear as an active DN when the user isn't connected to the network with their 2050 client.

This is strange, as I've used 2050's with the keepalive feature on some systems as a "phantom" DN for oddball requests (using the free IP client keycode that comes with the systems).

 

[option11newby]

Thanks Mr Marshall. the documentation says that it should should/would keep the DN alive unless the BCM suffers from a restart. We have not had a restart, and the Sales people obviously think that their calls will go to voicemail when they are not logged on.

We have tried the same scenario with other members of staff. It will keep their DN alive for 24 hours then when you attempt to ring their extn you get the Not in Service message.

I thought I would try to se if any of the BCM guys had any idea before we open a ticket.

Biv343, this happens on most of the i2050 phones as they are valid DN's for the sales force.

Thanks

 

[3Sixty]

Yeah I have had that happen but I was unaware of the keep alive parameter facilitating the extension to be a live extension. That will resolve some problems I have with other site if this works.I was wondering do you have 10 IP phones and 10 licenses. I have had problems where some customers have had 10 sales staff but only 5 IP seats.

Marshall

 

[biv343]

Typically you need one IP license for each configured phone. You might be able to fool it with hot desking and having the sales staff "log into" a guest extension when they're in the office. I've never tried that though.

I'm wondering if the keepalive issue is a UTPS issue or a core issue - there are some new UTPS and core patches out that aren't included in CP2.

This might be a good one for ITAS. Let us know what the solution is if you go that route.

 

[option11newby]

We have 32 ip seats and currently utilising 75% of that. I have just downloaded the latest core patch and will put this into the system this weekend.

I will let you all know the outcome of this.

Thanks

 

[3Sixty]

There are some patches related to the UNISTIM. Have you installed that?

Marshall

 

[option11newby]

are these patches separate from CP2?

 

[3Sixty]

Yeah seperate from the cp2

 

[MagnaRGP]

There are 15 "post CP2" patches for release 3.6. to bring a machine to current.

I hear that they were going to release CP3 soon, but it has been removed from beta due to some issues.

 

[3Sixty]

There are 15 patches but some are specific to call center and CDR. The few I think you should be interested in should be the Unistim,MSC core patches and maybe the VM patch if you have problems.

 

[nsantin]

We had this same problem with our i2050's in ver 3.50.
It went away when we upgraded to 3.6.

Stupid question: Are you sure you are on 3.6?

 

[kcaneva]

Hello -
Have any of you experienced dropped voice packets with the Nortel Phase I phones? The BCM 3.6 is running with the latest patches - The Phase II phones on the same system are not experiencing this problem.
We've found that the Phase I phones do not like excessive ARP broadcasts and will either lockup or experience poor voice quality. The Phase II phones seem to be immune to this.
Granted, ARP broadcasts are normal, but we found that this network is broadcasting ARP in what appears to inordinatley excessive amount. We've proven without the shawdow of doubt that this excessive ARPing is causing the IP sets to flake out.
We'd appreciate your input if you've experienced same...

Thanks a lot.

 

[hogandog]

kcaneva,

I am experiencing similar issues with LAN-based packet-loss on V3.6. I have solved my problem by implementing a Knudsen ARP trap on the L2 device. If you are new to this technique, feel free to email me at hoganisadog@hotmail.com. I can direct you to the necessary resources to modify the phone's behavior.