If you do not want to use session ID, you can write your method to create something equivalent. You can have port counter in database which the system reads and increments each time a call comes in. (from 1 to 60). Depending on no of calls you get, you can reset that counter back to 0 or 1 when it reaches 60. This will ensure that each call will have a unique ID with respect to the backend.
Hemal

From: Cisco Developer Community Forums [mailto:cdicuser@developer.cisco.com]
Sent: Wednesday, November 07, 2012 9:13 AM
To: cdicuser@developer.cisco.com
Subject: New Message from Keith Adams in Customer Voice Portal (CVP) - General Discussion - All Versions: CVP Telephony Port Number or Equivalent.

Keith Adams has created a new message in the forum "General Discussion - All Versions": -------------------------------------------------------------- Hi all, I’m in the process of moving an application from a TDM IVR to CVP. The application uses the IVR port number of the call as an ID to interface with a back end system. As the IVR uses the port ID this ensures that only one call with that ID can exist in the back end system at any one time. The port number can be used again once it has been released. As part of the migration I need to replicate this number which was between 1 and 60. Does anyone know if CVP has a method similar to a port ID or the license number etc? The session ID is unfortunately too long. Thanks Keith
--
To respond to this post, please click the following link: http://developer.cisco.com/web/cvp/forums/-/message_boards/view_message/8392559 or simply reply to this email.

My assumption was not that. Anyways, if that is the requirement than that too can be done. All you need to do is to look for which no got freed up from the database and have a method that checks for all such conditions and assigned the next one. The requirement needs to be defined further.
It’s java and any logic can be coded.
Hemal

From: Cisco Developer Community Forums [mailto:cdicuser@developer.cisco.com]
Sent: Wednesday, November 07, 2012 10:22 AM
To: cdicuser@developer.cisco.com
Subject: New Message from Janine Graves in Customer Voice Portal (CVP) - General Discussion - All Versions: Re: New Message from Hemal Mehta in Customer Voice Portal (CVP) - General D

Janine Graves has created a new message in the forum "General Discussion - All Versions": -------------------------------------------------------------- Hemal,

It's not quite that simple. Because if you have 20 callers, but then
caller number 3 hangs up. Now you have 19 callers, but you need to
assign the next caller with the number '3', not '20'.
So you need a pool of numbers 1-60. And each time a new call comes in,
you take a number out of this pool. And when the call is done (in the
end of call java), you have to put the number back into the pool.

You could use a DB for this or create persistent global data (using
java). But the details would be up to you.

Janine
--
To respond to this post, please click the following link: http://developer.cisco.com/web/cvp/forums/-/message_boards/view_message/8395361 or simply reply to this email.

Keith,
Yes, multiple applications can read the values of global data at the
same time using custom java.
How large can this number be? Can't you use the ANI? You wouldn't have
more than one call from a phone number at a given time, would you?

Why not use the RouterCallKey from ICM? That shouldn’t be very large, as it is reset every day to 1 and increments with each call.

I did consider taking a
mod 60 on the router call key but the uniqueness within the back end system was
still an issue.  I like the suggestions
of a database with record locking or thread synchronisation.
Thank you for
these.
I'm leaning towards the database at the moment as it potentially helps with another ID that needs to be replicated.

Keith

Sure, I would be interested to know how to get this ds0-num using Custom VXML in Call Studio.

In VoiceXML you can access a SIP header using the session variable session.com.cisco.proto_headers[''], for example, session.com.cisco.proto_headers['Remote-Party-ID'].  Sample VoiceXML output from a custom element is attached; you can see a selection of headers being retrieved.

To get the B-channel ID itself you have to retrieve the Via header and parse the DS0 number from the x-ds0num header field.   I've attached a custom element that will retrieve the headers configured in the element settings and create data for each of the fields.  In the B-channel example, using this custom element, the relevant information would be written to ElementName.Via.x-ds0num.  The actual value you're interested in still needs to be parsed-out but this gets you pretty close.   For a BRI the DS0 field looks like this: x-ds0num="Basic Rate Interface 0/1/0 1S0" so you just need to extract the value from the xS0 part.  It's very similar for a PRI.

In comprehensive model, the Via header on the VRU leg won't include the x-ds0num field as CVP doesn't propagate it but there's a couple of things you can do very easily provided you configure the CVP Call Server to pass the Via x-ds0num field up to ICM.   In the ICM script you can either parse out the B-channel number from the xS0 field into a call variable or just write it to a custom SIP header before invoking the SendToVRU if you don't want to use up variable space.

Attachments: