----- "Dan Austin" <[EMAIL PROTECTED]> wrote: > I don't have wireshark, so I am open to suggestions. > My sniffer is reporting it as 'extra bytes'. At least > one of structures in the current code is using : > > uint32_t space; > > To generate 4 bytes of padding, so I extended the concept. > I have a patch that I am cleaning up right now, and I > can/will open a bug with it attached. > > My 7940 is still functional after these changes, so the > older phones do not care if the packet is padded, but the > new ones choke if it is not. Based on that observation, I > would tend to think that this approach is valid not only > for trunk, but also branches/1.4 since the code tries to > support the new devices. > > An alternate approach is to duplicate all of the structures > and have versions for old and new phones and make the general > code aware of the difference so we send old style packets > to legacy models and the new style for the current models (yuck). > > Dan
Wireshark doesn't know about anything after the second char[24] -- Jason Parker Digium _______________________________________________ --Bandwidth and Colocation provided by Easynews.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
