✳flâneur — a map of the web's best reading

LTE | Nick vs Networking

nickvsnetworking.com · 368 words · saved by 1 readers

In our last post we looked at Actions and ActionPlans, and one of the really funky things we can do is setting ActionPlans to trigger on a time schedule or setting ActionTriggers to trigger on an event. We’re going to build on the examples we had on the last post, so we’ll assume your code is up to the point where we’ve added a Signup Bonus to an account, using an ActionPlan we assigned when creating the account. In this post, we’re going to create an action that charges $6, called “Action_Monthly_Charge“, and tie it to an ActionPlan called “ActionPlan_Monthly_Charge“, but to demo how this works rather than charging this Monthly, we’re going to charge it every minute. Then with our balances ticking down, we’ll set up an ActionTrigger to trigger when the balance drops below $95, and alert us. The Action for the Monthly charge will look much like the other actions we’ve defined, except the Identifier is *debit so we know we’re deducting from the balance, and we’ll log to the CDRs table t

I was recently asked by a potential customer if we supported Gx over Gy. I’d never heard of this before, so I gave my standard “If it’s in the spec we should support it, but I’ll check” answer, and got them to send me a PCAP, which I’ve got. This is weird. So for starers, Protocoldex has nothing for this application ID (16777225), even though it has all the LTE diameter specs. My starting point was TS 29.230 TS Diameter applications; 3GPP specific codes and identifiers which acknowledged the existence of “Gx over Gy” with IANA code 16777225 and p

Explore this link on the map →

related reading