I think his patch was setting the span itself as the private data to the callback rather than the private_data which was currently being set.



On Thu, Jan 29, 2009 at 8:10 AM, Helmut Kuper <helmut.kuper@ewetel.de> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Stefan,

I'm not sure what you want to tell me with the diff. Maybe I should hook
into the CallBack log function to get the span_id?

After your hint I looked into FS's concole log and found that even the
Q931 callback log function displays span_id 0

I think this line:

zap_log("Span", "Q.931", span->span_id, (int)level, "%s", msg);


produces this line:

2009-01-29 11:16:20 [DEBUG] Span:0 Q.931() Receiving message from Layer4
(size: 212, type: 69)

in FS console. There span_id is zero despite the fact that span_id in
openzap.conf.xml is "1"

openzap seems to set the span_id during zap_span_create(). The first
span gets the span_id 1.

Unfortuantely neither FS console nor my code displays the span id as
expected.

I would like to have it, because I want to put it into pcap file to give
a hint in wireshark from which span the traffic is.


regards
Helmut
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)

iEYEARECAAYFAkmBuNcACgkQ4tZeNddg3dw5ugCgl2E1E/wiaGrebuh8G0WM9+gr
iMoAoI0DmmkIC2B/CwxNiZQKYB7EmcDP
=jDTx
-----END PGP SIGNATURE-----



--
Anthony Minessale II

FreeSWITCH http://www.freeswitch.org/
ClueCon http://www.cluecon.com/

AIM: anthm
MSN:anthony_minessale@hotmail.com
GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com
IRC: irc.freenode.net #freeswitch

FreeSWITCH Developer Conference
sip:888@conference.freeswitch.org
iax:guest@conference.freeswitch.org/888
googletalk:conf+888@conference.freeswitch.org
pstn:213-799-1400