" /> 2nd call in IVR - Genesys CTI User Forum

Author Topic: 2nd call in IVR  (Read 4025 times)

Offline naviat

  • Jr. Member
  • **
  • Posts: 54
  • Karma: 0
2nd call in IVR
« on: November 19, 2012, 11:02:54 AM »
Advertisement
Our system has 2 RM run in HA mode and 2 MCP. We are testing the scenario when a customer calls to IVR system.

- The 1st call, everything works fine and customer gets auto-response from system
- 2nd call, There is no music or response from IVR system

We dont know whats wrong. We have chosen MCP mode in Resource Group as Route Robin. Wonder if it is the reason? I also attach the log for you

MCP log
[quote]2012-11-19T15:16:26.452 Int 50052 0092010A-10004022 1439845248 incall_initiated 0:0
2012-11-19T15:16:26.455 Int 50130 0092010A-10004022 1465936768 appl_begin INIT_URL=http://10.84.8.26:8080/test/src-gen/Main.vxml|DEFAULTS=file:///opt/gcti/gvp_mcp/config/defaults-ng.vxml|ANI=sip:1211@10.84.8.19|DNIS=sip:9001@10.84.8.19:5060|PROTOCOLNAME=sip|PROTOCOLVERSION=2.0|CALLIDREF=00347C22-D902-10A9-9120-1108540AAA77-40@10.84.8.19|VXMLI_TYPE=NGI
2012-11-19T15:16:26.456 Int 50016 0092010A-10004022 1465936768 wf_lookup http://10.84.8.26:8080/test/src-gen/Main.vxml
2012-11-19T15:16:26.456 Int 50016 0092010A-10004022 1465936768 wf_lookup file:///opt/gcti/gvp_mcp/config/defaults-ng.vxml
2012-11-19T15:16:56.465 Int 50056 0092010A-10004022 1439845248 call_reference 00347C22-D902-10A9-9120-1108540AAA77-40@10.84.8.19|AD029C00-0CA4-65B7-94FC-269E26A2AD7B|Environment|test1
2012-11-19T15:16:56.465 Int 50002 0092010A-10004022 1439845248 incall_reject sip:9001@10.84.8.19:5060|sip:1211@10.84.8.19|20121119313016017|N/A|N/A|N/A|timeout
2012-11-19T15:16:56.466 Int 50036 0092010A-10004022 1468947328 appl_end [/quote]


RM log
[quote]Via: SIP/2.0/UDP 10.84.8.20:5066;branch=z9hG4bK0x23f94640a9e078
From: sip:Environment@10.84.8.22:5068;tag=AD029C00-0CA4-4E0F-F59A-05F3591F43AC
To: sip:Environment@10.84.8.19:5060;tag=00347C36-D902-10A9-9120-1108540AAA77-1
Max-Forwards: 70
CSeq: 210 NOTIFY
Call-ID: 00347C22-D902-10A9-9120-1108540AAA77-1@10.84.8.19
Contact: <sip:GVP@10.84.8.20:5066>
Content-Length: 21
Content-Type: application/x-genesys-gvp-tenant-ports
Subscription-State: active
Event: x-genesys-gvp-tenant-ports
X-Genesys-gvp-tenant-ports: Environment/1000/1000
Supported: timer, uui

Environment/1000/1000
2012-11-19 14:32:08.329 DBUG 00000000-00000000 1245256576 09400901 DataModule.cxx:871 Calling SendNotify for Subscription for tenant-ID Environment
2012-11-19 14:32:08.333 DBUG 00000000-00000000 1232210816 09400901 CCPSIPMessageInterceptor.h:588 RM - SIP Message received from [10.84.8.19:5060] (360): SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.84.8.20:5066;branch=z9hG4bK0x23f94640a9e078;received=10.84.8.20
From: sip:Environment@10.84.8.22:5068;tag=AD029C00-0CA4-4E0F-F59A-05F3591F43AC
To: sip:Environment@10.84.8.19:5060;tag=00347C36-D902-10A9-9120-1108540AAA77-1
CSeq: 210 NOTIFY
Call-ID: 00347C22-D902-10A9-9120-1108540AAA77-1@10.84.8.19
Content-Length: 0


2012-11-19 14:32:08.411 DBUG 00000000-00000000 1240238976 08500000 VGSIPTransportMgr.cxx:3443 VGSIPTransportMgr::ResolveDNS for 10.84.8.24:5071
2012-11-19 14:32:08.412 DBUG 00000000-00000000 1240238976 09400901 GVPRMSIPMonitor.cxx:268 Calling Send Options to: sips:10.84.8.24:5071
2012-11-19 14:32:08.412 DBUG 00000000-00000000 1240238976 08500000 VGSIPTransportMgr.cxx:3443 VGSIPTransportMgr::ResolveDNS for 10.84.8.23:5070
2012-11-19 14:32:08.412 DBUG 00000000-00000000 1240238976 09400901 GVPRMSIPMonitor.cxx:268 Calling Send Options to: sip:10.84.8.23:5070
2012-11-19 14:32:08.412 DBUG 00000000-00000000 1240238976 08500000 VGSIPTransportMgr.cxx:3443 VGSIPTransportMgr::ResolveDNS for 10.84.8.24:5070
2012-11-19 14:32:08.412 DBUG 00000000-00000000 1240238976 09400901 GVPRMSIPMonitor.cxx:268 Calling Send Options to: sip:10.84.8.24:5070
2012-11-19 14:32:08.412 DBUG 00000000-00000000 1240238976 08500000 VGSIPTransportMgr.cxx:3443 VGSIPTransportMgr::ResolveDNS for 10.84.8.23:5071
2012-11-19 14:32:08.412 DBUG 00000000-00000000 1240238976 09400901 GVPRMSIPMonitor.cxx:268 Calling Send Options to: sips:10.84.8.23:5071
2012-11-19 14:32:08.414 DBUG 00000000-00000000 1232210816 09400901 GVPRMSIPMonitor.cxx:216 Changing resource to online: sips:10.84.8.23:5071
2012-11-19 14:32:08.414 DBUG 00000000-00000000 1232210816 09400901 GVPRMSIPMonitor.cxx:216 Changing resource to online: sip:10.84.8.23:5070[/quote]

Offline Kubig

  • Hero Member
  • *****
  • Posts: 2755
  • Karma: 44
Re: 2nd call in IVR
« Reply #1 on: November 19, 2012, 12:39:00 PM »
Could you please attach RM log which covered the issue? Current fragment of log covering only Notify SIP message,but not SIP signal. of call.

Offline naviat

  • Jr. Member
  • **
  • Posts: 54
  • Karma: 0
Re: 2nd call in IVR
« Reply #2 on: November 20, 2012, 02:20:02 AM »
Yes, sorry, here's my log RM when i dial from eyeBeam  ???

https://skydrive.live.com/redir?resid=11E5182275BCF890!225&authkey=!AK21bqkXaOgj23k

Thanks in advance

Offline René

  • Administrator
  • Hero Member
  • *****
  • Posts: 1832
  • Karma: 62
Re: 2nd call in IVR
« Reply #3 on: November 21, 2012, 09:26:36 AM »
Hi,

I did quick check of provided logs and found just one call that looks to be processed correctly. Did you upload correct log?

R.

Offline bublepaw

  • Sr. Member
  • ****
  • Posts: 283
  • Karma: 10
Re: 2nd call in IVR
« Reply #4 on: November 21, 2012, 08:52:57 PM »
One more comment on top of Rene's - in log I can see some retransimted messages which would point to network problems or network misconfiguration. Sometimes I see 127.0.0.1 and in some other messages real address. Without full set of logs from RM/SIPS/MCP including stratup logs it will be difficult to help