cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1421
Views
0
Helpful
2
Replies

Missing Quota Restore message when changing packages with quotas

k.vlachoulis
Beginner
Beginner

Hi all,

We experiencing a problem with quotas when we change package to a subscriber. We are having the Unprovisioned package that doesn;t allow any other kind of traffic except the redirection of browsing traffic to a portal. Also we have configured quota consumption for that traffic. We don't have a SM and QM but a third party external PCRF server that perform these tasks. We have also configured the provisioned package that the subscriber has internet access but we count his quota with a different quota profile.

The problem that we have is when the subscriber has quota and the quota depleted we don;t get a Quota restore message for the quotas that the subscriber must have.

As an example the subscriber is in the unprovisioned package with the quota bucket 2 and he has 20 MB. When the subscriber is in provisioned package and he buys 50MB service and when the quota depleted message comes he changes to package unprovisioned. The problem that we have is that we don;t have a quota restore message in order to take the quota value of unprovisioned package and as a result the subscriber doesn;t have service even to this package.

My question is why we don;t have the quota restore message during this change.

2012-04-01 14:05:05 | INFO  | CPU #000 | EM Agent: login operation was called with parameters: ID: xxx, mappings: ip add , additive: false, policy: packageId=8

2012-04-01 14:05:05 | INFO  | CPU #000 | EM Agent: quotaUpdate operation was called with parameters: ID: xxx, quota: 1=20480:1

2012-04-01 14:05:11 | INFO  | CPU #000 | EM Agent: quotaStatusIndication operation was called with parameters: ID: xxx, quota: 9,2,1333278311,2=10861

2012-04-01 14:05:43 | INFO  | CPU #000 | EM Agent: quotaBelowThresholdIndication operation was called with parameters:  operation with parameters ID:xxx, quota: 8,-1,1333278343,1=0

2012-04-01 14:05:43 | INFO  | CPU #000 | EM Agent: quotaDepletedIndication operation was called with parameters: ID: xxx, quota: 8,-1,1333278343,1=0

2012-04-01 14:05:43 | INFO  | CPU #000 | EM Agent: quotaUpdate operation was called with parameters: ID: xxx, quota: 1=0:0

2012-04-01 14:05:43 | INFO  | CPU #000 | EM Agent: quotaUpdate operation was called with parameters: ID: xxx, quota: 1=0:1

2012-04-01 14:05:44 | INFO  | CPU #000 | EM Agent: login operation was called with parameters: ID:xxx7, mappings: ip add, additive: false, policy: packageId=9

2012-04-01 14:05:47 | INFO  | CPU #000 | EM Agent: quotaStatusIndication operation was called with parameters: ID: xxx, quota: 8,2,1333278347,1=0

2012-04-01 14:06:05 | INFO  | CPU #000 | EM Agent: quotaBelowThresholdIndication operation was called with parameters:  operation with parameters ID: xxx, quota: 9,-1,1333278353,2=0

Thanks

2 Replies 2

mmiletic
Cisco Employee
Cisco Employee

Hi Kanellos,

Have you already resolved this in one of TAC cases?

Thanks,

Minja

Hello Minja,

We didn;t manage to reproduce 100% the case during TAC investigation. Maybe it was the something related to API on the PCRF side.

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: