It is common to work, my guess would be your geo location settings maybe.
https://docs.genesys.com/Documentation/GVP/8.1.0/Solution/Geo-LocationConfiguration
Hello cava,
I just added the option to the LRG, it was already on agent extension, trunk. I can see the call “incoming with VAL geo location” but it still cannot find the right service. I also re-read the whole GVP user guide, SIP deployment guide et GMS deployment guide. So I created another IVR Profile within GA with random integer for some mandatory data which you can leave blank :
IVR Profile “IVR_App_VXML”
[gvp.general] service-type=voicexml[gvp.policy]
cti-allowed=false
msml-allowed=true
outbound-call-allowed=true
transfer-allowed=true
usage-limits=20
use-same-gateway=always[gvp.service-parameters]
voicexml.gvp.appmodule=fixed,VXML-NG[gvp.service-prerequisite]
initial-page-url=file:///D:/GCTI/mcp/music/PRO_MUSIC_2018.wav
Tenant “Environment” options
[gvp.dn-group-assignments] DIDGroup=104[gvp.dn-groups]
DIDGroup=1000-2000[gvp.general]
default-application=IVR_App_VXML
service-type=voicexml
sip.sessiontimer=1800[gvp.policy]
usage-limits=100[iWD]
runtime-id=SYSTEM
version=9.0.0.2
RM logs
2023-02-24T14:24:23.177 DBUG 00000000-00000000 428 08500000 VGSIPProxyCore.cxx:284 VGSIPProxyCore::NotifyTransactionRequest processing method 1 2023-02-24T14:24:23.177 DBUG 00000000-00000000 428 09400901 CCPSIPProxyCoreProcessor.cxx:196 Request-URI parsed: msml 10.0.243.198 5160 2023-02-24T14:24:23.177 Trc 20119 INFO 00000000-00000000 428 09400506 New call : sip:msml@10.0.243.198:5160;tenant-dbid=1;media-service=treatment 2023-02-24T14:24:23.177 Trc 20002 NOTE 00000000-00000000 428 0940040C New call: Session-ID: | Call-ID:DF761B9F-5769-4B6F-85B3-3A8D9E17E220-218@10.0.243.198 | Request-URI:sip:msml@10.0.243.198:5160;tenant-dbid=1;media-service=treatment 2023-02-24T14:24:23.177 Trc 20002 NOTE 00000000-00000000 428 0940040D CallSessionImpl(719DBEAD-590C-4F57-3BA5-48D403663D2A) CSPtr<00000000019E7320> DMPtr<00000000094E7880> 2023-02-24T14:24:23.177 Trc 20002 NOTE 00000000-00000000 428 0940040C New call session: Session-ID:719DBEAD-590C-4F57-3BA5-48D403663D2A | Call-ID:DF761B9F-5769-4B6F-85B3-3A8D9E17E220-218@10.0.243.198 2023-02-24T14:24:23.177 DBUG 00000000-00000000 428 09400901 CCPSIPProxyCoreProcessor.cxx:1951 Cluster Information: primary=1 secondary=0 2023-02-24T14:24:23.177 DBUG 00000000-00000000 428 09400901 PolicyModule.cxx:223 719DBEAD-590C-4F57-3BA5-48D403663D2A New Call Session Request-URI : sip:msml@10.0.243.198:5160;tenant-dbid=1;media-service=treatment 2023-02-24T14:24:23.177 DBUG 00000000-00000000 428 09400901 PolicyModule.cxx:290 719DBEAD-590C-4F57-3BA5-48D403663D2A Handling call using call tenant Environment 2023-02-24T14:24:23.177 DBUG 00000000-00000000 428 09400901 PolicyModule.cxx:1725 getGVPTenantId returned GVPTenantID: IncomingApp: [b]2023-02-24T14:24:23.177 DBUG 00000000-00000000 428 09400901 PolicyModule.cxx:948 Incoming geo-location: 'VAL' [/b]2023-02-24T14:24:23.177 DBUG 00000000-00000000 428 09400901 PolicyModule.cxx:983 Incoming App from header is: bIsDbid: 0 2023-02-24T14:24:23.177 DBUG 00000000-00000000 428 09400901 PolicyModule.cxx:1760 getGVPTenantProfileForMSMLService returned TenantDBID: 1 ServiceProfileName: treatment 2023-02-24T14:24:23.177 DBUG 00000000-00000000 428 09400901 PolicyDataStore.cxx:601 Returning Default Application IVR_App_VXML 2023-02-24T14:24:23.177 Trc 20002 NOTE 00000000-00000000 428 0940040D IVR Profile is selected under the Tenant for the call 2023-02-24T14:24:23.177 DBUG 00000000-00000000 428 09400901 PolicyDataStore.cxx:601 Returning Default Application IVR_App_VXML 2023-02-24T14:24:23.177 Trc 20002 NOTE 00000000-00000000 428 0940040D Recording IVR profile is selected for the Tenant for the call 2023-02-24T14:24:23.177 Trc 20002 NOTE 00000000-00000000 428 0940040D CallImpl CSPtr<00000000019E7320> CPtr<00000000019F3C30> DMPtr<00000000094E7880> 2023-02-24T14:24:23.177 Trc 20002 NOTE 00000000-00000000 428 0940040C Session-ID:719DBEAD-590C-4F57-3BA5-48D403663D2A | Call-ID:DF761B9F-5769-4B6F-85B3-3A8D9E17E220-218@10.0.243.198 | SERVICE TYPE: treatment 2023-02-24T14:24:23.177 DBUG 00000000-00000000 428 09400901 GVPRMLocationService.cxx:117 Calling RequestResource: treatment UseSameGateway: always TenantDBID: 1 2023-02-24T14:24:23.177 Trc 20002 NOTE 00000000-00000000 428 09400000 Applicable LRG: 1.GVP_MCPGroup_LRG.MCPGroup 2023-02-24T14:24:23.177 Std 20029 EROR 00000000-00000000 428 09400217 719DBEAD-590C-4F57-3BA5-48D403663D2A Cannot allocate a resource type matching service type [Service Type: treatment] 2023-02-24T14:24:23.177 Std 20126 EROR 00000000-00000000 428 0940023F ResourceModule RequestResource failed: -10 Call Session: 719DBEAD-590C-4F57-3BA5-48D403663D2A 2023-02-24T14:24:23.177 DBUG 00000000-00000000 428 09400901 CallSessionImpl.h:2195 Pushing Call into Disconnected call list<> 2023-02-24T14:24:23.177 DBUG 00000000-00000000 428 09400901 CallImpl.h:1148 The call is cleared CPtr<00000000019F3C30> DMPtr<00000000094E7880> 2023-02-24T14:24:23.177 Trc 20002 NOTE 00000000-00000000 428 0940040D Cleared call session 719DBEAD-590C-4F57-3BA5-48D403663D2A CSPtr<00000000019E7320> DMPtr<00000000094E7880> 2023-02-24T14:24:23.177 DBUG 00000000-00000000 428 08500000 VGSIPTransportMgr.cxx:3837 VGSIPTransportMgr::ResolveDNS for 10.0.243.198:5060 2023-02-24T14:24:23.177 DBUG 00000000-00000000 428 08500000 VGSIPTransportMgr.cxx:3954 VGSIPTransportMgr::ResolveDNS nResult 2; CallID 2023-02-24T14:24:23.177 Trc 20152 INFO 00000000-00000000 428 09400509 RM - SIP Message sent to [10.0.243.198:5060] (520): SIP/2.0 603 Decline Via: SIP/2.0/UDP 10.0.243.198:5060;branch=z9hG4bKE7AACDB1-D049-49C4-8AD7-98204E80FE55-44 From: "Anonymous" ;tag=DA20F679-12AA-4F70-B31C-6776F9701D3A-226 To: ;tag=36CEAD06-67F3-44C6-5D92-06C2BD60AE96 CSeq: 1 INVITE Call-ID: DF761B9F-5769-4B6F-85B3-3A8D9E17E220-218@10.0.243.198 [b]Contact: sip:GVP@10.0.243.198:5160 [/b]Content-Length: 0 Warning: 399 10.0.243.198 "No matching resources for this service type [Service Type: treatment]"
Is it normal it contacts “GVP” VOIP Service DN ?
The documents are not explicit, but should I add a “[gvp.policy].treatment-allowed=true” in my IVR Profile or the tenant ?
Thank you.
Did you configure appropriate LRG with certain services like msml,treatment,vxml,etc.? Is the assigned MCP set as primary/active within the LRG?
EDIT :
Hello everyone,
Here is all steps in my Resource Group using GA wizard :
Resource Manager Selection : my “rm” application
Group Name and Type : “MCPGroup”, type=MCP, Services=VoiceXML, Conference, Announcement, Media, MSML, Treatment
Tenant Assignement : “Environment”, I have only this tenant
Group Properties : Monitoring Method=SIP OPTIONS, Load Balancing=Round Robin, Geo-Location=“VAL”, Max Conf Size=10, Max Conf Count=, SQ Notifification Threshold (%)=
Resource Assignment : my “mcp” application, port 5070, Max Port=20, Redundancy=Active
But when displayed in the GA, I can see Assigned=no. I don’t know if it should be yes, and in CME, I can see my MCP application moved to the GVP_MCPGroup_LRG/MCPGroup/ folder. Here is the associated folder options :
[gvp.lrg]
error.notification.threshold=
geo-location=VAL
load-balance-scheme=round-robin
monitor-method=option
port-usage-type=outbound
resource-confmaxcount=
resource-confmaxsize=10
service-types=voicexml;conference;announcement;media;msml;treatment
Is this normal to have “outbound” port usage type ?
Also I noticed that if I set Redundancy=Active, I got a blank/silence when I call my RP and the RM log says :
Environment/10.0.243.198:5070/out-of-service
but if I set it to Passive (because I have only one RM, one MCP, one SIP Server), I got a default standard ringing tone when I call my RP, and RM logs says :
Environment/10.0.243.198:5070/in-service
Thank you all.
Hello everyone,
we manage, with a Genesys PS and Avaya expert, to find the solution for the music in queue. There were several problem, I sum up here my case :
- Avaya detects that the SIP call sent from Avaya VDN to Genesys RP remained in “Ringing” status, because no treatment was played on MCP
- in Genesys, put the MCP access right to Full Control for SYSTEM user (it was probably automatically removed when the application was placed to the LRG folder)
- add explicitly the tenant to the RM object, in Tenant section
- in a single tenant environment, with no HA on application objects, the LRG must be set with “Active” Redundancy even if “Passive” is default setting
- in MPC options, for Windows Server reason, we had to set the msml/play.basepath=file://D:\xxx\xxx with backslashes
Will look now for the music on hold issue.
Quite weird hehe never had to do those things.
But thanks for sharing and great that you found a solution