# session.id

## session.id

A unique ID for each session. The ID consists of a six character server identifier (defaults to “000000”), followed by a semicolon, followed by a three digit channel identifier, followed by a semicolon, followed by a timestamp of when the channel was ready to receive the next call.

### Example

```markup
<?xml version="1.0" encoding="latin-1"?>
<vxml version="2.0">
  <form>
    <block>
      <prompt>
        Your phone number is
        <say-as type="acronym">
          <value expr="session.telephone.ani"/>
        </say-as>.
        You called
        <say-as type="acronym">
          <value expr="session.telephone.dnis"/>
        </say-as>.
        Your session id is
        <say-as type="acronym">
          <value expr="session.id"/>
        </say-as>.
      </prompt>
    </block>
  </form>
</vxml>
```

### Explanation

From this example, the application returns the caller's phone number, the phone number that the caller called, and the session id. Let's say the caller called from 234-867-5309 and dialed into 866-123-4567. The application would first say, “Your phone number is 234-867-5309.”&#x20;

Next, the application would say, “You called 866-123-4567.” However, if the caller called into a local number such as 234-123-4567, the application would only return the last 4 digits of the DNIS. In this case, the application would say, “You called 4567.”&#x20;

Finally, for the session id, the application would return a unique id such as “000005;000;1190752725” where the number before the first semicolon is a six character server identifier, the number before the second semicolon is a three digit channel identifier, and the last number is a timestamp of when the channel was ready to receive the next call.

### Notes

None


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.plumvoice.com/dev/voicexml/application-and-session-variables/session.id.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.