The SIP service table lists each Customer Voice Portal SIP
service configured on this server. The CVP SIP service is a
software module which always resides in the CVP Call Server.
The CVP SIP service is a SIP Back-to-Back User Agent (B2BUA).
On the front end, it supports two SIP call legs, one incoming
and one outgoing. This service does not terminate RTP flows:
it only deals with SIP messages. On the back end, the SIP
service implements the (GED-125) Service Control Interface
(SCI) to the Cisco Intelligent Contact Management (ICM)
application for call control functions only (no VRU scripts).
The purpose of a B2BUA is to act as an active intermediary
for a call, communicating with both the source and the
destination legs of the call, and providing 3rd party call
control capabilities on behalf of a routing engine (such as
the ICM contact router). Because it must track the call
throughout its life, it becomes a key source of call-level
reporting data and a natural place for moderating call
switching resources.
Generally speaking, a SIP B2BUA is two User Agents (UAs).
The device receives incoming calls in one UA and immediately
creates an outgoing call via its other UA. Thereafter, all
SIP messages from either one are forwarded to the other.
What makes it useful is the fact that it puts ICM in between
the two legs. On incoming calls, it asks the ICM where the
outgoing call should be addressed. Once the call has been
delivered, ICM has the opportunity to end the outgoing leg
and reconnect it to a subsequent destination. In practice,
there will typically be a delivery to the subsequent agents
(call center agents - a human resources tasked with answering
inbound calls and providing specific services) or back to
the VRU leg.
The SIP service table has a sparse dependent relationship
with the (generic) ccvpService table. The service index acts
as the primary index, relating the entry to the corresponding
entry in the ccvpService table.
The SNMP agent constructs this table at startup. Since
services can only be added or deleted when the CVP
application is stopped, service information entries cannot be
added to or deleted from the table either by the agent or the
management station while the application is running. The
agent will update service information table objects as their
values change when the application is running. All objects
in this table are read-only to the management station.
Parsed from file CISCO-CVP-MIB.mib
Module: CISCO-CVP-MIB
The SIP service table lists each Customer Voice Portal SIP
service configured on this server. The CVP SIP service is a
software module which always resides in the CVP Call Server.
The CVP SIP service is a SIP Back-to-Back User Agent (B2BUA).
On the front end, it supports two SIP call legs, one incoming
and one outgoing. This service does not terminate RTP flows;
it only deals with SIP messages. On the back end, the SIP
service implements the (GED-125) Service Control Interface
(SCI) to the Cisco Intelligent Contact Management (ICM)
application for call control functions only (no VRU scripts).
The purpose of a B2BUA is to act as an active intermediary
for a call, communicating with both the source and the
destination legs of the call, and providing 3rd party call
control capabilities on behalf of a routing engine (such as
the ICM contact router). Because it must track the call
throughout its life, it becomes a key source of call-level
reporting data and a natural place for moderating call
switching resources.
Generally speaking, a SIP B2BUA is two User Agents (UAs).
The device receives incoming calls in one UA and immediately
creates an outgoing call via its other UA. Thereafter, all
SIP messages from either one are forwarded to the other.
What makes it useful is the fact that it puts ICM in between
the two legs. On incoming calls, it asks the ICM where the
outgoing call should be addressed. Once the call has been
delivered, ICM has the opportunity to end the outgoing leg
and reconnect it to a subsequent destination. In practice,
there will typically be a delivery to the subsequent agents
(call center agents - a human resources tasked with answering
inbound calls and providing specific services) or back to
the VRU leg.
The SIP service table has a sparse dependent relationship
with the (generic) ccvpService table. The service index acts
as the primary index, relating the entry to the corresponding
entry in the ccvpService table.
The SNMP agent constructs this table at startup. Since
services can only be added or deleted when the CVP
application is stopped, service information entries cannot be
added to or deleted from the table either by the agent or the
management station while the application is running. The
agent will update service information table objects as their
values change when the application is running. All objects
in this table are read-only to the management station.
The SIP service table lists each Customer Voice Portal SIP
service configured on this server. The CVP SIP service is a
software module which always resides in the CVP Call Server.
The CVP SIP service is a SIP Back-to-Back User Agent (B2BUA).
On the front end, it supports two SIP call legs, one incoming
and one outgoing. This service does not terminate RTP flows;
it only deals with SIP messages. On the back end, the SIP
service implements the (GED-125) Service Control Interface
(SCI) to the Cisco Intelligent Contact Management (ICM)
application for call control functions only (no VRU scripts).
The purpose of a B2BUA is to act as an active intermediary
for a call, communicating with both the source and the
destination legs of the call, and providing 3rd party call
control capabilities on behalf of a routing engine (such as
the ICM contact router). Because it must track the call
throughout its life, it becomes a key source of call-level
reporting data and a natural place for moderating call
switching resources.
Generally speaking, a SIP B2BUA is two User Agents (UAs).
The device receives incoming calls in one UA and immediately
creates an outgoing call via its other UA. Thereafter, all
SIP messages from either one are forwarded to the other.
What makes it useful is the fact that it puts ICM in between
the two legs. On incoming calls, it asks the ICM where the
outgoing call should be addressed. Once the call has been
delivered, ICM has the opportunity to end the outgoing leg
and reconnect it to a subsequent destination. In practice,
there will typically be a delivery to the subsequent agents
(call center agents - a human resources tasked with answering
inbound calls and providing specific services) or back to
the VRU leg.
The SIP service table has a sparse dependent relationship
with the (generic) ccvpService table. The service index acts
as the primary index, relating the entry to the corresponding
entry in the ccvpService table.
The SNMP agent constructs this table at startup. Since
services can only be added or deleted when the CVP
application is stopped, service information entries cannot be
added to or deleted from the table either by the agent or the
management station while the application is running. The
agent will update service information table objects as their
values change when the application is running. All objects
in this table are read-only to the management station.
Parsed from file CISCO-CVP-MIB.my.txt
Company: None
Module: CISCO-CVP-MIB
The SIP service table lists each Customer Voice Portal SIP
service configured on this server. The CVP SIP service is a
software module which always resides in the CVP Call Server.
The CVP SIP service is a SIP Back-to-Back User Agent (B2BUA).
On the front end, it supports two SIP call legs, one incoming
and one outgoing. This service does not terminate RTP flows;
it only deals with SIP messages. On the back end, the SIP
service implements the (GED-125) Service Control Interface
(SCI) to the Cisco Intelligent Contact Management (ICM)
application for call control functions only (no VRU scripts).
The purpose of a B2BUA is to act as an active intermediary
for a call, communicating with both the source and the
destination legs of the call, and providing 3rd party call
control capabilities on behalf of a routing engine (such as
the ICM contact router). Because it must track the call
throughout its life, it becomes a key source of call-level
reporting data and a natural place for moderating call
switching resources.
Generally speaking, a SIP B2BUA is two User Agents (UAs).
The device receives incoming calls in one UA and immediately
creates an outgoing call via its other UA. Thereafter, all
SIP messages from either one are forwarded to the other.
What makes it useful is the fact that it puts ICM in between
the two legs. On incoming calls, it asks the ICM where the
outgoing call should be addressed. Once the call has been
delivered, ICM has the opportunity to end the outgoing leg
and reconnect it to a subsequent destination. In practice,
there will typically be a delivery to the subsequent agents
(call center agents - a human resources tasked with answering
inbound calls and providing specific services) or back to
the VRU leg.
The SIP service table has a sparse dependent relationship
with the (generic) ccvpService table. The service index acts
as the primary index, relating the entry to the corresponding
entry in the ccvpService table.
The SNMP agent constructs this table at startup. Since
services can only be added or deleted when the CVP
application is stopped, service information entries cannot be
added to or deleted from the table either by the agent or the
management station while the application is running. The
agent will update service information table objects as their
values change when the application is running. All objects
in this table are read-only to the management station.
ccvpSipTable OBJECT-TYPE SYNTAX SEQUENCE OF CcvpSipEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The SIP service table lists each Customer Voice Portal SIP service configured on this server. The CVP SIP service is a software module which always resides in the CVP Call Server. The CVP SIP service is a SIP Back-to-Back User Agent (B2BUA). On the front end, it supports two SIP call legs, one incoming and one outgoing. This service does not terminate RTP flows: it only deals with SIP messages. On the back end, the SIP service implements the (GED-125) Service Control Interface (SCI) to the Cisco Intelligent Contact Management (ICM) application for call control functions only (no VRU scripts). The purpose of a B2BUA is to act as an active intermediary for a call, communicating with both the source and the destination legs of the call, and providing 3rd party call control capabilities on behalf of a routing engine (such as the ICM contact router). Because it must track the call throughout its life, it becomes a key source of call-level reporting data and a natural place for moderating call switching resources. Generally speaking, a SIP B2BUA is two User Agents (UAs). The device receives incoming calls in one UA and immediately creates an outgoing call via its other UA. Thereafter, all SIP messages from either one are forwarded to the other. What makes it useful is the fact that it puts ICM in between the two legs. On incoming calls, it asks the ICM where the outgoing call should be addressed. Once the call has been delivered, ICM has the opportunity to end the outgoing leg and reconnect it to a subsequent destination. In practice, there will typically be a delivery to the subsequent agents (call center agents - a human resources tasked with answering inbound calls and providing specific services) or back to the VRU leg. The SIP service table has a sparse dependent relationship with the (generic) ccvpService table. The service index acts as the primary index, relating the entry to the corresponding entry in the ccvpService table. The SNMP agent constructs this table at startup. Since services can only be added or deleted when the CVP application is stopped, service information entries cannot be added to or deleted from the table either by the agent or the management station while the application is running. The agent will update service information table objects as their values change when the application is running. All objects in this table are read-only to the management station." ::= { ccvpServiceInfo 1 }
ccvpSipTable OBJECT-TYPE SYNTAX SEQUENCE OF CcvpSipEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "The SIP service table lists each Customer Voice Portal SIP service configured on this server. The CVP SIP service is a software module which always resides in the CVP Call Server. The CVP SIP service is a SIP Back-to-Back User Agent (B2BUA). On the front end, it supports two SIP call legs, one incoming and one outgoing. This service does not terminate RTP flows; it only deals with SIP messages. On the back end, the SIP service implements the (GED-125) Service Control Interface (SCI) to the Cisco Intelligent Contact Management (ICM) application for call control functions only (no VRU scripts). The purpose of a B2BUA is to act as an active intermediary for a call, communicating with both the source and the destination legs of the call, and providing 3rd party call control capabilities on behalf of a routing engine (such as the ICM contact router). Because it must track the call throughout its life, it becomes a key source of call-level reporting data and a natural place for moderating call switching resources. Generally speaking, a SIP B2BUA is two User Agents (UAs). The device receives incoming calls in one UA and immediately creates an outgoing call via its other UA. Thereafter, all SIP messages from either one are forwarded to the other. What makes it useful is the fact that it puts ICM in between the two legs. On incoming calls, it asks the ICM where the outgoing call should be addressed. Once the call has been delivered, ICM has the opportunity to end the outgoing leg and reconnect it to a subsequent destination. In practice, there will typically be a delivery to the subsequent agents (call center agents - a human resources tasked with answering inbound calls and providing specific services) or back to the VRU leg. The SIP service table has a sparse dependent relationship with the (generic) ccvpService table. The service index acts as the primary index, relating the entry to the corresponding entry in the ccvpService table. The SNMP agent constructs this table at startup. Since services can only be added or deleted when the CVP application is stopped, service information entries cannot be added to or deleted from the table either by the agent or the management station while the application is running. The agent will update service information table objects as their values change when the application is running. All objects in this table are read-only to the management station." ::= { ccvpServiceInfo 1 }
Vendor: Cisco
Module: CISCO-CVP-MIB
[Automatically extracted from oidview.com]
ccvpSipTable OBJECT-TYPE SYNTAX SEQUENCE OF CcvpSipEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The SIP service table lists each Customer Voice Portal SIP service configured on this server. The CVP SIP service is a software module which always resides in the CVP Call Server. The CVP SIP service is a SIP Back-to-Back User Agent (B2BUA). On the front end, it supports two SIP call legs, one incoming and one outgoing. This service does not terminate RTP flows; it only deals with SIP messages. On the back end, the SIP service implements the (GED-125) Service Control Interface (SCI) to the Cisco Intelligent Contact Management (ICM) application for call control functions only (no VRU scripts). The purpose of a B2BUA is to act as an active intermediary for a call, communicating with both the source and the destination legs of the call, and providing 3rd party call control capabilities on behalf of a routing engine (such as the ICM contact router). Because it must track the call throughout its life, it becomes a key source of call-level reporting data and a natural place for moderating call switching resources. Generally speaking, a SIP B2BUA is two User Agents (UAs). The device receives incoming calls in one UA and immediately creates an outgoing call via its other UA. Thereafter, all SIP messages from either one are forwarded to the other. What makes it useful is the fact that it puts ICM in between the two legs. On incoming calls, it asks the ICM where the outgoing call should be addressed. Once the call has been delivered, ICM has the opportunity to end the outgoing leg and reconnect it to a subsequent destination. In practice, there will typically be a delivery to the subsequent agents (call center agents - a human resources tasked with answering inbound calls and providing specific services) or back to the VRU leg. The SIP service table has a sparse dependent relationship with the (generic) ccvpService table. The service index acts as the primary index, relating the entry to the corresponding entry in the ccvpService table. The SNMP agent constructs this table at startup. Since services can only be added or deleted when the CVP application is stopped, service information entries cannot be added to or deleted from the table either by the agent or the management station while the application is running. The agent will update service information table objects as their values change when the application is running. All objects in this table are read-only to the management station." ::= { ccvpServiceInfo 1 }
ccvpSipTable OBJECT-TYPE SYNTAX SEQUENCE OF CcvpSipEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The SIP service table lists each Customer Voice Portal SIP service configured on this server. The CVP SIP service is a software module which always resides in the CVP Call Server. The CVP SIP service is a SIP Back-to-Back User Agent (B2BUA). On the front end, it supports two SIP call legs, one incoming and one outgoing. This service does not terminate RTP flows; it only deals with SIP messages. On the back end, the SIP service implements the (GED-125) Service Control Interface (SCI) to the Cisco Intelligent Contact Management (ICM) application for call control functions only (no VRU scripts). The purpose of a B2BUA is to act as an active intermediary for a call, communicating with both the source and the destination legs of the call, and providing 3rd party call control capabilities on behalf of a routing engine (such as the ICM contact router). Because it must track the call throughout its life, it becomes a key source of call-level reporting data and a natural place for moderating call switching resources. Generally speaking, a SIP B2BUA is two User Agents (UAs). The device receives incoming calls in one UA and immediately creates an outgoing call via its other UA. Thereafter, all SIP messages from either one are forwarded to the other. What makes it useful is the fact that it puts ICM in between the two legs. On incoming calls, it asks the ICM where the outgoing call should be addressed. Once the call has been delivered, ICM has the opportunity to end the outgoing leg and reconnect it to a subsequent destination. In practice, there will typically be a delivery to the subsequent agents (call center agents - a human resources tasked with answering inbound calls and providing specific services) or back to the VRU leg. The SIP service table has a sparse dependent relationship with the (generic) ccvpService table. The service index acts as the primary index, relating the entry to the corresponding entry in the ccvpService table. The SNMP agent constructs this table at startup. Since services can only be added or deleted when the CVP application is stopped, service information entries cannot be added to or deleted from the table either by the agent or the management station while the application is running. The agent will update service information table objects as their values change when the application is running. All objects in this table are read-only to the management station." ::= { ccvpServiceInfo 1 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.590.1.6.1.1 | ccvpSipEntry | 25 | 25 | Each entry represents a Customer Voice Portal (CVP) SIP service configured on the server. The SIP service acts as an active inte… |
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.590.1.6.2 | ccvpH323Table | 1 | 20 | The H.323 Service table lists each Customer Voice Portal (CVP) H.323 service configured on this server. This service is a softwa… |
| 1.3.6.1.4.1.9.9.590.1.6.3 | ccvpIvrTable | 1 | 25 | The IVR Service table lists each Customer Voice Portal Interactive Voice Response service configured on this server. Each entry i… |
| 1.3.6.1.4.1.9.9.590.1.6.4 | ccvpIcmTable | 1 | 25 | The ICM Service table lists each Customer Voice Portal ICM service configured on this server. Each entry in the table defines a … |
| 1.3.6.1.4.1.9.9.590.1.6.5 | ccvpReptTable | 1 | 9 | The Reporting service table lists each Customer Voice Portal reporting service configured on this server. The CVP Reporting Serv… |
| 1.3.6.1.4.1.9.9.590.1.6.6 | ccvpVxmlTable | 1 | 15 | The Voice XML Service table lists each Customer Voice Portal Voice XML service installed and configured on this server. The CVP V… |