[quote author=Fra link=topic=7345.msg31494#msg31494 date=1345473863]
[quote author=kevinwang link=topic=7345.msg31493#msg31493 date=1345468927]
[quote author=Fra link=topic=7345.msg31474#msg31474 date=1345194542]
Have you added the userdata-map-filter to the Voice Treatment Ports? Can you see any attached data passed to MCP now?
[quote author=kevinwang link=topic=7345.msg31471#msg31471 date=1345129581]
[quote author=Fra link=topic=7345.msg31442#msg31442 date=1344937383]
[quote author=kevinwang link=topic=7345.msg31425#msg31425 date=1344875887]
what do you mean by Resource Group cti-usage option
for MCP resource group? but there is no cti related option.
Are you saying cti options in IVR profile? I enabled cti-allowed, and cti,transferONCTI options.
[/quote]
I think the use-cti option is set on the Gateway Resource Group (in essence the SIP Server Resource Manager communicates to in IVR Server deployments).
Fra
[/quote]
Can I create two different Resource Gateways, one for integration through IVR Server, the other for integration through Sip Server?
If so, where to specify which resource gateway will be used one specific different mode?
Thanks.
[/quote]
I think you can't have both integrations in the same installation.
Also, I don't think that the Gateway Resource Group is needed for the integration through SIP Server.
Fra
[/quote]
[color=red][b][size=14pt]Configuring CTI Flagging for IVR Profiles[/size][/b][/color]
Complete the procedures in this section to configure the rules that Resource
Manager uses to determine whether it should forward calls to the CTI
Connector.
Depending on your deployment architecture and the applications that it
services, you can flag the gateway resource as follows:
• Always Off—For CTI through SIP Server only deployments, where CTI
Connector and IVR Server are not included in the architecture. Resource
Manager performs IVR Profile mapping based on the DNIS provided in
the incoming call.
• Always On—For deployments where CTI through IVR Server is always
required. For example, if your deployment only services IVR-centric
applications, where CTI through IVR Server is required for midcall CTI
functionality. Or in TDM-connected configurations, where the DNIS must
be retrieved from the IVR Server in all cases.
• Based on DN Lookup—For deployments with architecture configurations
that support both CTI through IVR Server and CTI through SIP Server call
flows, and that include both Standard VoiceXML and IVR-centric voice
applications. For this option, you must set the IVR Profile for a specific
application as either CTI or non-CTI. For non-CTI applications
(self-service only), Resource Manager bypasses CTI Connector and
instead maps the IVR Profile directly.
[/quote]
well, yes, my second question was which of these values you set the option to
My first one still stands: have you added the userdata-map-filter to the Voice Treatment Ports? Can you see any attached data passed to MCP now?
Fra
[/quote]
Thank you very much for your quick response.
I did some configuration change, now symptom changed, I will open a new post to discuss it.
