make NotificationOriginator using MibInstrumentationController when expanding

Notification OBJECTS into Managed Objects Instances

2 files changed, 7 insertions, 1 deletions

diff --git a/CHANGES b/CHANGES
index d83fbe9..f55229d 100644
--- a/CHANGES
+++ b/CHANGES
@@ -89,6 +89,8 @@ Revision 4.2.6rc0
   change has been explicitly permitted by the original modules authors.
 - Fix to asyncore-based transport not to use asyncore's cheap inheritance
   from socket object what caused warnings.
+- Fix at NotificationOriginator to make is using MibInstrumentationController
+  when expanding Notification OBJECTS into Managed Objects Instances.
 - Missing wrongLength and wrongEncoding SMI errors added.
 
 Revision 4.2.5
diff --git a/pysnmp/entity/rfc3413/ntforg.py b/pysnmp/entity/rfc3413/ntforg.py
index 98e92c8..c7e7a98 100644
--- a/pysnmp/entity/rfc3413/ntforg.py
+++ b/pysnmp/entity/rfc3413/ntforg.py
@@ -326,7 +326,11 @@ class NotificationOriginator:
                         mibNode = mibNode.getNode(mibNode.name + instanceIndex)
                     else:
                         mibNode = mibNode.getNextNode(mibNode.name)
-                    varBinds.append((mibNode.name, mibNode.syntax))
+                    varBinds.extend(
+                        contextMibInstrumCtl.readVars(
+                            [ (mibNode.name, None) ]  # XXX AC is missing
+                        )
+                    )
                     debug.logger & debug.flagApp and debug.logger('sendVarBinds: processed notification object %s, instance index %s, var-bind %s' % (notificationObject, instanceIndex is None and "<first>" or instanceIndex, mibNode))
             elif notificationName:  # numeric OID
                 varBinds.append(