Jump to content

jholland

Members
  • Posts

    16
  • Joined

  • Last visited

Posts posted by jholland

  1. The issue has to deal with an incoming call going directly to a hunt group and if someone that is assigned to the hunt group picks the call, no other extensions are able to see the BLF for that extension until the extension places the call on hold or tries to transfer/conference. In short the initial call state is not shown for a call picked up directly in a hunt group. Please advise......

  2. Having issues with BLF working on incoming calls ringing into a Hunt Group.

     

    We are unable to see an extension take a call directly from a Hunt Group. You are only able to see the call state once the extension puts the call on exclusive hold, transfer, conference or any other call state.

     

     

     

    Pbxnsip Ver: 3.3.1.3177 (Linux)

    Polycom Ver: 3.1.3.0439

  3. Having an issue on version 1.5.6 version and Polycom phones on 1.6.7 firmware version with the MWI intermittently not working. Examples are person is left a new voicemail and the light does not activate, or person doesn't have a new message and the light still blinks and can't be cleared without a hard reset. Has anyone experienced an issue with this and what would the fix be?

  4. Has anyone been able to get BLA to work with POLYCOM ver 2.0.3.0127 and PBXNSIP ver 2.0.3.1715? If so what are the settings being used in the XML files for the POLYCOM phones and what other oddities need to be added to the PBXNSIP?

  5. Having an issue with setting a service flag time sets up in 1715 version. We are trying to have the follwoing script in the service flag entry 08:45-11:45 13:00-16:30 18:30-7:45 for the day/night time set to work so that, the service flag is cleared during these times but for some reason on the last or third entry 18:30-7:45 the service flag never comes off of SET.

  6. I have also noticed that when a caller is placed on HOLD for more than 2.5 to 3 minutes that the PBXNSIP will hang up the call. I believe there is some kind of timeout within the software that drops calls that are not transmitting two way audio.

     

     

     

     

     

    I'm getting an RTP timeout after putting calls on mute for between 2.5 and 3 minutes on PBXnSIP version 2.0.3.1715. Would others please confirm if they're seeing this. After the timeout the call obviously drops. This was discovered by a user listening to a conference on mute.
  7. Where is the XML file that we can change the start date settings for new day light savings time change? It took place March 11, 2007 this year and not April 1st, 2007. This is screwing up my service flags and call records. :o

×
×
  • Create New...