[asterisk-dev] manager event conversion strategy (was: oej: branch oej/managergames r174538 - /team/oej/managergames/)

Steve Murphy murf at digium.com
Mon Feb 16 12:46:06 CST 2009


On Tue, 2009-02-10 at 10:33 -0600, Russell Bryant wrote:
> On Feb 10, 2009, at 9:53 AM, Johansson Olle E wrote:
> >> Events already automatically have an entity ID added to them
> >> automatically by the event core.  This was needed for sharing events
> >> between servers.  The entitiy ID looks just like it does for DUNDi.
> >> It's a unique identifier, in the same form as a MAC address.  When
> >> Asterisk starts, we try to grab one from a network interface, or it
> >> can be configured in asterisk.conf.  Does this handle what you had in
> >> mind?
> > And we also have systemname, which is easier to handle by
> > humans... Yes, I saw what you did in the ais code.
> > I thought that entity ID was only used in AIS, not internally in
> > Asterisk.
> 
> 
> It's used internally, as well.  I went with the EID because it has  
> nice properties that fit what was needed:
> 
> 1) A unique ID can be determined automatically, which makes  
> configuration easier in most cases.
> 
> 2) Since this is a unique ID that has to go in _every_ event, and may  
> also result in a comparison that must be done on _every_ event, I  
> wanted to restrict it to something small.  It is a 6 byte payload.
> 
> We could come up with a way to display a friendlier string for each  
> EID for CLI display if we come across a need to display it on the  
> CLI.  I suppose it could be useful for debugging.

There were some "animated" discussions on uniqueID in CDR's previously,
and perhaps this might play into it somehow... I like the idea of a 
6-byte payload opposed to 36 byte uid's, etc. At least, as an option!

murf

-- 
Steve Murphy <murf at digium.com>
Digium
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3227 bytes
Desc: not available
Url : http://lists.digium.com/pipermail/asterisk-dev/attachments/20090216/290beeb2/attachment-0001.bin 


More information about the asterisk-dev mailing list