I dunno what stuff is used by the vsa product. There is nothing in the SIP standard which can be referred to as conference id. TID is transaction id (i.e., value of branch parameter). If you would like to have some unique value, use callid. Note that some devices are known to generate broken non-unique callids and you better also include from-tag and to-tag. The latter can't be gained from exec since it depends in SIP reply. Use acc module to record call start/stop events better.

-jiri

At 07:42 PM 7/30/2004, David Stanaway wrote:

Hi, I am trying to prototype a ser module by first using a perl script in exec_dset, and I would like to record the calls conference ID. I had thought that the TID was the conferenceid (As seen on cisco vsa accounting) but they do not match.

Here is an example:

I get an INVITE request from a Cisco ATA using ser as an outbound proxy.

The exec_dset script sees this in the environment: SIP_TID = 6d2796abca7d6e1d65249aa229bc2f53

The cisco 5350 I redirect to shows this in its cisco-vsa accounting: h323-conf-id = "h323-conf-id=8457403F E38341D8 872CFC52 183D0ADC"

What is happening here? Is the cisco gateway generating the conferencid for the SIP call? Should it be using the SIP TID?

-- David Stanaway david@dialmex.net

---

Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers

-- Jiri Kuthan http://iptel.org/~jiri/