Other
API reference for diameter.message.commands.
Placeholder classes that extend Message, but do not provide any direct
python API for reading and setting AVPs.
AggregatedRUCIReport ¶
AggregatedRUCIReport(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
An Aggregated-RUCI-Report message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the AggregatedRUCIReport.append_avp method.
AlertServiceCentre ¶
AlertServiceCentre(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
An Alert-Service-Centre message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the AlertServiceCentre.append_avp method.
AuthenticationInformation ¶
AuthenticationInformation(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A 3GPP-Authentication-Information message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the AuthenticationInformation.append_avp method.
BackgroundDataTransfer ¶
BackgroundDataTransfer(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A Background-Data-Transfer message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the BackgroundDataTransfer.append_avp method.
BootstrapingInfo ¶
BootstrapingInfo(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A Bootstraping-Info message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the BootstrapingInfo.append_avp method.
CancelLocation ¶
CancelLocation(header: MessageHeader = None, avps: list[Avp] = None)
Bases: UndefinedMessage
A 3GPP-Cancel-Location message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the CancelLocation.append_avp method.
CancelVCSGLocation ¶
CancelVCSGLocation(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A Cancel-VCSG-Location message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the CancelVCSGLocation.append_avp method.
CapabilitiesUpdate ¶
CapabilitiesUpdate(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A Capabilities-Update message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the CapabilitiesUpdate.append_avp method.
ConfigurationInformation ¶
ConfigurationInformation(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A Configuration-Information message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the ConfigurationInformation.append_avp method.
ConnectionManagement ¶
ConnectionManagement(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A Connection-Management message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the ConnectionManagement.append_avp method.
DataPull ¶
DataPull(header: MessageHeader = None, avps: list[Avp] = None)
Bases: UndefinedMessage
A Data-Pull message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the DataPull.append_avp method.
DataUpdate ¶
DataUpdate(header: MessageHeader = None, avps: list[Avp] = None)
Bases: UndefinedMessage
A Data-Update message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the DataUpdate.append_avp method.
DeleteSubscriberData ¶
DeleteSubscriberData(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A 3GPP-Delete-Subscriber-Data message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the DeleteSubscriberData.append_avp method.
DeliveryReport ¶
DeliveryReport(header: MessageHeader = None, avps: list[Avp] = None)
Bases: UndefinedMessage
A 3GPP-Delivery-Report message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the DeliveryReport.append_avp method.
DeviceAction ¶
DeviceAction(header: MessageHeader = None, avps: list[Avp] = None)
Bases: UndefinedMessage
A 3GPP-Device-Action message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the DeviceAction.append_avp method.
DeviceNotification ¶
DeviceNotification(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A 3GPP-Device-Notification message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the DeviceNotification.append_avp method.
DeviceTrigger ¶
DeviceTrigger(header: MessageHeader = None, avps: list[Avp] = None)
Bases: UndefinedMessage
A 3GPP-Device-Trigger message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the DeviceTrigger.append_avp method.
DistributedCharging ¶
DistributedCharging(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A Distributed Charging message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the DistributedCharging.append_avp method.
EricssonBindingData ¶
EricssonBindingData(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
An Ericsson-Binding-Data message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the EricssonBindingData.append_avp method.
EricssonSL ¶
EricssonSL(header: MessageHeader = None, avps: list[Avp] = None)
Bases: UndefinedMessage
An Ericsson-SL message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the EricssonSL.append_avp method.
EricssonSN ¶
EricssonSN(header: MessageHeader = None, avps: list[Avp] = None)
Bases: UndefinedMessage
An Ericsson-SN message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the EricssonSN.append_avp method.
EricssonTraceReport ¶
EricssonTraceReport(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
An Ericsson-Trace-Report message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the EricssonTraceReport.append_avp method.
GCSAction ¶
GCSAction(header: MessageHeader = None, avps: list[Avp] = None)
Bases: UndefinedMessage
A GCS-Action message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the GCSAction.append_avp method.
GCSNotification ¶
GCSNotification(header: MessageHeader = None, avps: list[Avp] = None)
Bases: UndefinedMessage
A GCS-Notification message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the GCSNotification.append_avp method.
GetGateway ¶
GetGateway(header: MessageHeader = None, avps: list[Avp] = None)
Bases: UndefinedMessage
A Get-Gateway message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the GetGateway.append_avp method.
IKEv2SK ¶
IKEv2SK(header: MessageHeader = None, avps: list[Avp] = None)
Bases: UndefinedMessage
An IKEv2-SK message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the IKEv2SK.append_avp method.
InsertSubscriberData ¶
InsertSubscriberData(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A 3GPP-Insert-Subscriber-Data message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the InsertSubscriberData.append_avp method.
JuniperSessionDiscovery ¶
JuniperSessionDiscovery(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A Juniper-Session-Discovery message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the JuniperSessionDiscovery.append_avp method.
JuniperSyncEvent ¶
JuniperSyncEvent(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A Juniper-Sync-Event message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the JuniperSyncEvent.append_avp method.
LCSRoutingInfo ¶
LCSRoutingInfo(header: MessageHeader = None, avps: list[Avp] = None)
Bases: UndefinedMessage
A 3GPP-LCS-Routing-Info message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the LCSRoutingInfo.append_avp method.
LocationReport ¶
LocationReport(header: MessageHeader = None, avps: list[Avp] = None)
Bases: UndefinedMessage
A 3GPP-Location-Report message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the LocationReport.append_avp method.
MIp6 ¶
MIp6(header: MessageHeader = None, avps: list[Avp] = None)
Bases: UndefinedMessage
A MIP6 message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the MIp6.append_avp method.
MOData ¶
MOData(header: MessageHeader = None, avps: list[Avp] = None)
Bases: UndefinedMessage
An MO-Data message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the MOData.append_avp method.
MOForwardShortMessage ¶
MOForwardShortMessage(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
An MO-Forward-Short-Message message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the MOForwardShortMessage.append_avp method.
MTData ¶
MTData(header: MessageHeader = None, avps: list[Avp] = None)
Bases: UndefinedMessage
An MT-Data message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the MTData.append_avp method.
MTForwardShortMessage ¶
MTForwardShortMessage(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
An MT-Forward-Short-Message message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the MTForwardShortMessage.append_avp method.
MeIdentityCheck ¶
MeIdentityCheck(header: MessageHeader = None, avps: list[Avp] = None)
Bases: UndefinedMessage
A 3GPP-ME-Identity-Check message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the AaMobileNode.append_avp method.
MessageProcess ¶
MessageProcess(header: MessageHeader = None, avps: list[Avp] = None)
Bases: UndefinedMessage
A Message-Process message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the MessageProcess.append_avp method.
MobileApplication ¶
MobileApplication(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A Mobile-Application message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the MobileApplication.append_avp method.
ModifyUecontext ¶
ModifyUecontext(header: MessageHeader = None, avps: list[Avp] = None)
Bases: UndefinedMessage
A Modify-Uecontext message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the ModifyUecontext.append_avp method.
MsgInterface ¶
MsgInterface(header: MessageHeader = None, avps: list[Avp] = None)
Bases: UndefinedMessage
A Msg-Interface message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the MsgInterface.append_avp method.
NATControl ¶
NATControl(header: MessageHeader = None, avps: list[Avp] = None)
Bases: UndefinedMessage
A NAT-Control message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the NATControl.append_avp method.
NIDDInformation ¶
NIDDInformation(header: MessageHeader = None, avps: list[Avp] = None)
Bases: UndefinedMessage
An NIDD-Information message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the NIDDInformation.append_avp method.
NSNCancelLocationMS ¶
NSNCancelLocationMS(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
An NSN-Cancel-LocationMS message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the NSNCancelLocationMS.append_avp method.
NSNProfileUpdateMS ¶
NSNProfileUpdateMS(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
An NSN-Profile-UpdateMS message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the NSNProfileUpdateMS.append_avp method.
NSNPushNotificationMS ¶
NSNPushNotificationMS(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
An NSN-Push-NotificationMS message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the NSNPushNotificationMS.append_avp method.
NSNSubscribeNotificationsMS ¶
NSNSubscribeNotificationsMS(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
An NSN-Subscribe-NotificationsMS message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the NSNSubscribeNotificationsMS.append_avp method.
NSNUserDataMS ¶
NSNUserDataMS(header: MessageHeader = None, avps: list[Avp] = None)
Bases: UndefinedMessage
An NSN-User-DataMS message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the NSNUserDataMS.append_avp method.
NetworkStatus ¶
NetworkStatus(header: MessageHeader = None, avps: list[Avp] = None)
Bases: UndefinedMessage
A Network-Status message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the NetworkStatus.append_avp method.
NetworkStatusContinuousReport ¶
NetworkStatusContinuousReport(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A Network-Status-Continuous-Report message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the NetworkStatusContinuousReport.append_avp method.
NokiaCoreService ¶
NokiaCoreService(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A Nokia Core Service message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the NokiaCoreService.append_avp method.
NokiaExtendedCommand ¶
NokiaExtendedCommand(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A Nokia Extended Command message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the NokiaExtendedCommand.append_avp method.
NokiaFetchSession ¶
NokiaFetchSession(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A Nokia Fetch-Session message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the NokiaFetchSession.append_avp method.
NokiaSessionMassSync ¶
NokiaSessionMassSync(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A Nokia Session-Mass-Sync message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the NokiaSessionMassSync.append_avp method.
NokiaSessionSync ¶
NokiaSessionSync(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A Nokia Session-Sync message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the NokiaSessionSync.append_avp method.
NonAggregatedRUCIReport ¶
NonAggregatedRUCIReport(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A Non-Aggregated-RUCI-Report message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the NonAggregatedRUCIReport.append_avp method.
Notif ¶
Notif(header: MessageHeader = None, avps: list[Avp] = None)
Bases: UndefinedMessage
A Notif message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the Notif.append_avp method.
NotificationData ¶
NotificationData(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A Notification-Data message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the NotificationData.append_avp method.
Notify ¶
Notify(header: MessageHeader = None, avps: list[Avp] = None)
Bases: UndefinedMessage
A 3GPP-Notify message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the Notify.append_avp method.
ProSeAlert ¶
ProSeAlert(header: MessageHeader = None, avps: list[Avp] = None)
Bases: UndefinedMessage
A ProSe-Alert message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the ProSeAlert.append_avp method.
ProSeAuthorization ¶
ProSeAuthorization(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A ProSe-Authorization message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the ProSeAuthorization.append_avp method.
ProSeCancellation ¶
ProSeCancellation(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A ProSe-Cancellation message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the ProSeCancellation.append_avp method.
ProSeDiscovery ¶
ProSeDiscovery(header: MessageHeader = None, avps: list[Avp] = None)
Bases: UndefinedMessage
A ProSe-Discovery message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the ProSeDiscovery.append_avp method.
ProSeInitialLocationInformation ¶
ProSeInitialLocationInformation(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A ProSe-Initial-Location-Information message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the ProSeInitialLocationInformation.append_avp method.
ProSeLocationUpdate ¶
ProSeLocationUpdate(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A ProSe-Location-Update message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the ProSeLocationUpdate.append_avp method.
ProSeMatch ¶
ProSeMatch(header: MessageHeader = None, avps: list[Avp] = None)
Bases: UndefinedMessage
A ProSe-Match message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the ProSeMatch.append_avp method.
ProSeMatchReportInfo ¶
ProSeMatchReportInfo(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A ProSe-Match-Report-Info message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the ProSeMatchReportInfo.append_avp method.
ProSeNotify ¶
ProSeNotify(header: MessageHeader = None, avps: list[Avp] = None)
Bases: UndefinedMessage
A ProSe-Notify message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the ProSeNotify.append_avp method.
ProSeProximity ¶
ProSeProximity(header: MessageHeader = None, avps: list[Avp] = None)
Bases: UndefinedMessage
A ProSe-Proximity message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the ProSeProximity.append_avp method.
ProSeSubscriberInformation ¶
ProSeSubscriberInformation(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A ProSe-Subscriber-Information message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the ProSeSubscriberInformation.append_avp method.
ProXimityAction ¶
ProXimityAction(header: MessageHeader = None, avps: list[Avp] = None)
Bases: UndefinedMessage
A ProXimity-Action message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the ProXimityAction.append_avp method.
ProXimityApplication ¶
ProXimityApplication(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A ProXimity-Application message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the ProXimityApplication.append_avp method.
ProfileUpdate ¶
ProfileUpdate(header: MessageHeader = None, avps: list[Avp] = None)
Bases: UndefinedMessage
A Profile-Update message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the ProfileUpdate.append_avp method.
ProvideLocation ¶
ProvideLocation(header: MessageHeader = None, avps: list[Avp] = None)
Bases: UndefinedMessage
A 3GPP-Provide-Location message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the ProvideLocation.append_avp method.
PurgeUE ¶
PurgeUE(header: MessageHeader = None, avps: list[Avp] = None)
Bases: UndefinedMessage
A 3GPP-Purge-UE message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the PurgeUE.append_avp method.
PushNotification ¶
PushNotification(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A Push-Notification message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the PushNotification.append_avp method.
QoSAuthorization ¶
QoSAuthorization(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A QoS-Authorization message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the QoSAuthorization.append_avp method.
QoSInstall ¶
QoSInstall(header: MessageHeader = None, avps: list[Avp] = None)
Bases: UndefinedMessage
A QoS-Install message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the QoSInstall.append_avp method.
QueryProfile ¶
QueryProfile(header: MessageHeader = None, avps: list[Avp] = None)
Bases: UndefinedMessage
A Query Profile message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the QueryProfile.append_avp method.
ReportSMDeliveryStatus ¶
ReportSMDeliveryStatus(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A Report-SM-Delivery-Status message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the ReportSMDeliveryStatus.append_avp method.
ReportingInformation ¶
ReportingInformation(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A Reporting-Information message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the ReportingInformation.append_avp method.
Reset ¶
Reset(header: MessageHeader = None, avps: list[Avp] = None)
Bases: UndefinedMessage
A Reset message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the MTData.append_avp method.
RivadaXaDPCRegistration ¶
RivadaXaDPCRegistration(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A Rivada Xa DPC-Registration message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the RivadaXaDPCRegistration.append_avp method.
RivadaXaHeartBeat ¶
RivadaXaHeartBeat(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A Rivada Xa Heart-Beat message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the RivadaXaHeartBeat.append_avp method.
RivadaXaResourceAllocation ¶
RivadaXaResourceAllocation(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A Rivada Xa Resource-Allocation message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the RivadaXaResourceAllocation.append_avp method.
RivadaXaResourceRelease ¶
RivadaXaResourceRelease(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A Rivada Xa Resource-Release message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the RivadaXaResourceRelease.append_avp method.
RivadaXaResourceReleaseNotification ¶
RivadaXaResourceReleaseNotification(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A Rivada Xa Resource-Release-Notification message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the RivadaXaResourceReleaseNotification.append_avp method.
RivadaXdCellInfoModification ¶
RivadaXdCellInfoModification(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A Rivada Xd Cell-Info-Modification message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the RivadaXdCellInfoModification.append_avp method.
RivadaXdCellInfoModificationNotification ¶
RivadaXdCellInfoModificationNotification(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A Rivada Xd Cell-Info-Modification-Notification message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the RivadaXdCellInfoModificationNotification.append_avp method.
RivadaXdCellInfoNotification ¶
RivadaXdCellInfoNotification(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A Rivada Xd Cell-Info-Notification message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the RivadaXdCellInfoNotification.append_avp method.
RivadaXdCellInfoTransfer ¶
RivadaXdCellInfoTransfer(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A Rivada Xd Cell-Info-Transfer message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the RivadaXdCellInfoTransfer.append_avp method.
RivadaXdDSCRegistration ¶
RivadaXdDSCRegistration(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A Rivada Xd DSC-Registration message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the RivadaXdDSCRegistration.append_avp method.
RivadaXdHeartBeat ¶
RivadaXdHeartBeat(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A Rivada Xd Heart-Beat message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the RivadaXdHeartBeat.append_avp method.
RivadaXdResourceAllocation ¶
RivadaXdResourceAllocation(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A Rivada Xd Resource-Allocation message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the RivadaXdResourceAllocation.append_avp method.
RivadaXdResourceAllocationNotification ¶
RivadaXdResourceAllocationNotification(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A Rivada Xd Resource-Allocation-Notification message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the RivadaXdResourceAllocationNotification.append_avp method.
RivadaXdResourceHold ¶
RivadaXdResourceHold(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A Rivada Xd Resource-Hold message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the RivadaXdResourceHold.append_avp method.
RivadaXdResourceHoldNotification ¶
RivadaXdResourceHoldNotification(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A Rivada Xd Resource-Hold-Notification message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the RivadaXdResourceHoldNotification.append_avp method.
RivadaXdResourceModification ¶
RivadaXdResourceModification(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A Rivada Xd Resource-Modification message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the RivadaXdResourceModification.append_avp method.
RivadaXdResourceModificationNotification ¶
RivadaXdResourceModificationNotification(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A Rivada Xd Resource-Modification-Notification message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the RivadaXdResourceModificationNotification.append_avp method.
RivadaXdResourceRelease ¶
RivadaXdResourceRelease(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A Rivada Xd Resource-Release message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the RivadaXdResourceRelease.append_avp method.
RivadaXdResourceReleaseNotification ¶
RivadaXdResourceReleaseNotification(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A Rivada Xd Resource-Release-Notification message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the RivadaXdResourceReleaseNotification.append_avp method.
RivadaXdResourceResume ¶
RivadaXdResourceResume(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A Rivada Xd Resource-Resume message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the RivadaXdResourceResume.append_avp method.
RivadaXdResourceResumeNotification ¶
RivadaXdResourceResumeNotification(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A Rivada Xd Resource-Resume-Notification message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the RivadaXdResourceResumeNotification.append_avp method.
RivadaXdResourceUsageNotification ¶
RivadaXdResourceUsageNotification(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A Rivada Xd Resource-Usage-Notification message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the RivadaXdResourceUsageNotification.append_avp method.
RivadaXdResourceUsageUpdate ¶
RivadaXdResourceUsageUpdate(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A Rivada Xd Resource-Usage-Update message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the RivadaXdResourceUsageUpdate.append_avp method.
RivadaXhUserData ¶
RivadaXhUserData(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A Rivada Xh User-Data message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the RivadaXhUserData.append_avp method.
RivadaXmAddUEContext ¶
RivadaXmAddUEContext(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A Rivada Xm Add-UE-Context message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the RivadaXmAddUEContext.append_avp method.
RivadaXmDeleteUEContext ¶
RivadaXmDeleteUEContext(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A Rivada Xm Delete-UE-Context message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the RivadaXmDeleteUEContext.append_avp method.
RivadaXmDetachUE ¶
RivadaXmDetachUE(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A Rivada Xm Detach-UE message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the RivadaXmDetachUE.append_avp method.
RivadaXmHeartBeat ¶
RivadaXmHeartBeat(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A Rivada Xm Heart-Beat message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the RivadaXmHeartBeat.append_avp method.
RivadaXmPageUE ¶
RivadaXmPageUE(header: MessageHeader = None, avps: list[Avp] = None)
Bases: UndefinedMessage
A Rivada Xm Page-UE message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the RivadaXmPageUE.append_avp method.
RivadaXmResourceAllocation ¶
RivadaXmResourceAllocation(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A Rivada Xm Resource-Allocation message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the RivadaXmResourceAllocation.append_avp method.
RivadaXmResourceAllocationNotify ¶
RivadaXmResourceAllocationNotify(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A Rivada Xm Resource-Allocation-Notify message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the RivadaXmResourceAllocationNotify.append_avp method.
RivadaXmResourceHold ¶
RivadaXmResourceHold(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A Rivada Xm Resource-Hold message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the RivadaXmResourceHold.append_avp method.
RivadaXmResourceModify ¶
RivadaXmResourceModify(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A Rivada Xm Resource-Modify message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the RivadaXmResourceModify.append_avp method.
RivadaXmResourceRelease ¶
RivadaXmResourceRelease(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A Rivada Xm Resource-Release message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the RivadaXmResourceRelease.append_avp method.
RivadaXmResourceResume ¶
RivadaXmResourceResume(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A Rivada Xm Resource-Resume message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the RivadaXmResourceResume.append_avp method.
RivadaXmUpdateUEContext ¶
RivadaXmUpdateUEContext(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A Rivada Xm Update-UE-Context message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the RivadaXmUpdateUEContext.append_avp method.
SendRoutingInfoforSM ¶
SendRoutingInfoforSM(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A Send-Routing-Info-for-SM message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the SendRoutingInfoforSM.append_avp method.
SipLocationInfo ¶
SipLocationInfo(header: MessageHeader = None, avps: list[Avp] = None)
Bases: UndefinedMessage
A SIP-Location-Info message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the SipLocationInfo.append_avp method.
SipMultimediaAuth ¶
SipMultimediaAuth(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A SIP-Multimedia-Auth message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the SipMultimediaAuth.append_avp method.
SipPushProfile ¶
SipPushProfile(header: MessageHeader = None, avps: list[Avp] = None)
Bases: UndefinedMessage
A SIP-Push-Profile message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the SipPushProfile.append_avp method.
SipRegistrationTermination ¶
SipRegistrationTermination(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A SIP-Registration-Termination message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the SipRegistrationTermination.append_avp method.
SipServerAssignment ¶
SipServerAssignment(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A SIP-Server-Assignment message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the SipServerAssignment.append_avp method.
SipUserAuthorization ¶
SipUserAuthorization(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A SIP-User-Authorization message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the SipUserAuthorization.append_avp method.
SubscribeNotifications ¶
SubscribeNotifications(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A Subscribe-Notifications message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the SubscribeNotifications.append_avp method.
SubscriberInformation ¶
SubscriberInformation(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A 3GPP-Subscriber-Information message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the SubscriberInformation.append_avp method.
SubscriptionInformationApplication ¶
SubscriptionInformationApplication(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A Subscription Information Application message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the SubscriptionInformationApplication.append_avp method.
TDFSession ¶
TDFSession(header: MessageHeader = None, avps: list[Avp] = None)
Bases: UndefinedMessage
A TDF-Session message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the TDFSession.append_avp method.
TSSFNotification ¶
TSSFNotification(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A TSSF-Notification message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the TSSFNotification.append_avp method.
Tggp2SubscriberInformation ¶
Tggp2SubscriberInformation(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A 3GPP2 Subscriber-Information message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the 3GPP2SubscriberInformation.append_avp method.
TgppReset ¶
TgppReset(header: MessageHeader = None, avps: list[Avp] = None)
Bases: UndefinedMessage
A 3GPP-Reset message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the Reset.append_avp method.
TriggerEstablishment ¶
TriggerEstablishment(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A Trigger-Establishment message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the TriggerEstablishment.append_avp method.
UpdateLocation ¶
UpdateLocation(header: MessageHeader = None, avps: list[Avp] = None)
Bases: UndefinedMessage
A 3GPP-Update-Location message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the UpdateLocation.append_avp method.
UpdateProSeSubscriberData ¶
UpdateProSeSubscriberData(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
An Update-ProSe-Subscriber-Data message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the UpdateProSeSubscriberData.append_avp method.
UpdateVCSGLocation ¶
UpdateVCSGLocation(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A 3GPP-Update-VCSG-Location message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the UpdateVCSGLocation.append_avp method.
UserData ¶
UserData(header: MessageHeader = None, avps: list[Avp] = None)
Bases: UndefinedMessage
A User-Data message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the UserData.append_avp method.
VerizonSessionDataRecovery ¶
VerizonSessionDataRecovery(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A Verizon Session Data Recovery message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the VerizonSessionDataRecovery.append_avp method.
WIMAXHRPDSFF ¶
WIMAXHRPDSFF(header: MessageHeader = None, avps: list[Avp] = None)
Bases: UndefinedMessage
A WIMAX-HRPD-SFF message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the WIMAXHRPDSFF.append_avp method.
WiMAXAbortSession ¶
WiMAXAbortSession(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A WiMAX-Abort-Session message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the WiMAXAbortSession.append_avp method.
WiMAXChangeofAuthorization ¶
WiMAXChangeofAuthorization(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A WiMAX-Change-of-Authorization message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the WiMAXChangeofAuthorization.append_avp method.
WiMAXDHCP ¶
WiMAXDHCP(header: MessageHeader = None, avps: list[Avp] = None)
Bases: UndefinedMessage
A WiMAX-DHCP message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the WiMAXDHCP.append_avp method.
WiMAXDiameterEAP ¶
WiMAXDiameterEAP(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A WiMAX-Diameter-EAP message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the WiMAXDiameterEAP.append_avp method.
WiMAXHomeAgentIPv4 ¶
WiMAXHomeAgentIPv4(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A WiMAX-Home-Agent-IPv4 message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the WiMAXHomeAgentIPv4.append_avp method.
WiMAXHomeAgentIPv6 ¶
WiMAXHomeAgentIPv6(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A WiMAX-Home-Agent-IPv6 message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the WiMAXHomeAgentIPv6.append_avp method.
WiMAXLAA ¶
WiMAXLAA(header: MessageHeader = None, avps: list[Avp] = None)
Bases: UndefinedMessage
A WiMAX-LAA message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the WiMAXLAA.append_avp method.
WiMAXLocationAccounting ¶
WiMAXLocationAccounting(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A WiMAX-Location-Accounting message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the WiMAXLocationAccounting.append_avp method.
WiMAXLocationMeasurementQuery ¶
WiMAXLocationMeasurementQuery(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A WiMAX-Location-Measurement-Query message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the WiMAXLocationMeasurementQuery.append_avp method.
WiMAXReauthentication ¶
WiMAXReauthentication(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A WiMAX-Reauthentication message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the WiMAXReauthentication.append_avp method.
WiMAXSessionTermination ¶
WiMAXSessionTermination(
header: MessageHeader = None, avps: list[Avp] = None
)
Bases: UndefinedMessage
A WiMAX-Session-Termination message.
This message implementation provides no python subclasses for requests and answers; AVPs must be created manually and added using the WiMAXSessionTermination.append_avp method.
register ¶
register(cmd_class: Type[DefinedMessage])
Register a custom command.
Adds a class that extends DefinedMessage to the internal registry of commands. Registered custom commands will be automatically recognised when parsing network-received bytes. If the command also implements a request and answer subclass, those are automatically returned as well.
msg_bytes = "01000028c00003e70000000000000000000000000000010740000014686f73742e7265616c6d3b31"
# returns an instance of UndefinedMessage
msg = Message.from_bytes(msg_bytes)
print(dump(msg))
# Prints:
# Unknown <Version: 0x01, Length: 40, Flags: 0xc0 (request, proxyable), Hop-by-Hop Identifier: 0x0, End-to-End Identifier: 0x0>
# Session-Id <Code: 0x107, Flags: 0x40 (-M-), Length: 20, Val: host.realm;1>
from diameter.message import DefinedMessage
from diameter.message.commands import register
class SpecialMessage(DefinedMessage):
code: int = 999
name: str = "Special-Message"
def __post_init__(self):
self.header.command_code = self.code
super().__post_init__()
register(SpecialMessage)
# now returns an instance of SpecialMessage
msg = Message.from_bytes(msg_bytes)
print(dump(msg))
# Prints:
# Special-Message <Version: 0x01, Length: 40, Flags: 0xc0 (request, proxyable), Hop-by-Hop Identifier: 0x0, End-to-End Identifier: 0x0>
# Session-Id <Code: 0x107, Flags: 0x40 (-M-), Length: 20, Val: host.realm;1>
Warning
If a command implementation with the same command code already exists, that implementation will be overwritten.