Guest

Preview Tool

Cisco Bug: CSCuj07424 - AnalogueLineMgmnt:AnalogLineModFeature fails for shared lines on MGCP

Last Modified

Jan 12, 2014

Products (1)

  • Cisco Hosted Collaboration Solution (HCS)

Known Affected Releases

8.1(2)ER1

Description (partial)

Symptom:
Details:
GIVEN that a MGCP analog gateway port has been registered as a shared line,
WHEN attempting to modify the analog line, transaction fails as below.

It appears the gateway is being updated with device specific settings from the
original device the line was registered on...

Prerequisites:
1. Registered line at a location (either assigned to phone or user EM profile)
2. MGCP analog gateway with ports allocated to the same location and the analog
port registered using the same extension as in step 1
3.

Steps to Reproduce:
1. Attempt to modify the analog line
2.
3.
4.
5.
6.
Actual Results:  


XML    
100845 Request Failed     AnalogLineModFeature
    =>  Entered at: 2013/08/13 17:05:35 SAST  (172.29.232.98)

      updateGatewayEndpoint [AALN/S0/1@16487-MGCP] AXL:updateGatewayEndpoint:
[108] Busy Trigger cannot be greater than 1 because the specified device type
does not support Call Waiting
    => Started at: 2013/08/13 17:05:35 SAST
          => End at: 2013/08/13 17:05:39 SAST

Status of sub transactions

100846  Driver_AnalogLineModFeature     XML     Y      Database Values for
Analog Line with FINT Number [0400110059204] Updated      
100847  Driver_IPPBX     XML     F      updateGatewayEndpoint
[AALN/S0/1@16487-MGCP] AXL:updateGatewayEndpoint: [108] Busy Trigger cannot be
greater than 1 because the specified device type does not support Call Waiting  
100849  Driver_AnalogLineModFeature     XML     F      DBERR - query[INSERT
INTO fintfeature
(data_value,provideraccess,divisionname,providername,resellername,locationname,fintnumber,companyname,servicetype)
VALUES (?,?,?,?,?,?,?,?,?)] ERROR: duplicate key value violates unique
constraint "fintfeature_location_key1"
DETAIL: Key (providername, resellername, companyname, divisionname,
locationname, fintnumber, servicetype)=(HUCS_Provider, Reseller_1, Customer_1,
Division_1, 1-Location, 0400110059204, VoiceMail) already exists.
- DBERR


Workaround Available: Unsure

Conditions:
Details:
GIVEN that a MGCP analog gateway port has been registered as a shared line,
WHEN attempting to modify the analog line, transaction fails as below.

It appears the gateway is being updated with device specific settings from the
original device the line was registered on...

Prerequisites:
1. Registered line at a location (either assigned to phone or user EM profile)
2. MGCP analog gateway with ports allocated to the same location and the analog
port registered using the same extension as in step 1
3.

Steps to Reproduce:
1. Attempt to modify the analog line
2.
3.
4.
5.
6.
Actual Results:  


XML    
100845 Request Failed     AnalogLineModFeature
    =>  Entered at: 2013/08/13 17:05:35 SAST  (172.29.232.98)

      updateGatewayEndpoint [AALN/S0/1@16487-MGCP] AXL:updateGatewayEndpoint:
[108] Busy Trigger cannot be greater than 1 because the specified device type
does not support Call Waiting
    => Started at: 2013/08/13 17:05:35 SAST
          => End at: 2013/08/13 17:05:39 SAST

Status of sub transactions

100846  Driver_AnalogLineModFeature     XML     Y      Database Values for
Analog Line with FINT Number [0400110059204] Updated      
100847  Driver_IPPBX     XML     F      updateGatewayEndpoint
[AALN/S0/1@16487-MGCP] AXL:updateGatewayEndpoint: [108] Busy Trigger cannot be
greater than 1 because the specified device type does not support Call Waiting  
100849  Driver_AnalogLineModFeature     XML     F      DBERR - query[INSERT
INTO fintfeature
(data_value,provideraccess,divisionname,providername,resellername,locationname,fintnumber,companyname,servicetype)
VALUES (?,?,?,?,?,?,?,?,?)] ERROR: duplicate key value violates unique
constraint "fintfeature_location_key1"
DETAIL: Key (providername, resellername, companyname, divisionname,
locationname, fintnumber, servicetype)=(HUCS_Provider, Reseller_1, Customer_1,
Division_1, 1-Location, 0400110059204, VoiceMail) already exists.
- DBERR


Workaround Available: Unsure
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.