Author Topic: composer error in gvp 8.1.6  (Read 7548 times)

Offline mumtazalam2k

  • Jr. Member
  • **
  • Posts: 55
  • Karma: 0
composer error in gvp 8.1.6
« on: January 13, 2014, 09:04:20 PM »
i m trying to run a test sample application using composer 8.1 with gvp 8.1.6.
i am able to create a sample vxml project and successfully generate code.
however when i run the callflow, it gives error message "Could not start the debug target,Failed to initialize SIP".

any reasons why this error is due to?

FYI, I can place a direct call from my sip phone to the GVP sample application both directly on sip server port and rm port.

Offline Kubig

  • Hero Member
  • *****
  • Posts: 2576
  • Karma: 42
Re: composer error in gvp 8.1.6
« Reply #1 on: January 13, 2014, 09:29:59 PM »
And what is your SIP phone configuration for Composer debug? Have you debug enabled on MCP?
Genesys certified professional consultant (GVP, SIP, GIR and Troubleshooting)

anoredis

  • Guest
Re: composer error in gvp 8.1.6
« Reply #2 on: January 13, 2014, 09:37:10 PM »
I once had the same issue. I cannot remember how I solved it though. I think I inserted 'localhost' instead of the IP address and somehow resolved. You may find more information in the Composer Help at the section "Debugging a Callflow"

Offline mumtazalam2k

  • Jr. Member
  • **
  • Posts: 55
  • Karma: 0
Re: composer error in gvp 8.1.6
« Reply #3 on: January 13, 2014, 09:59:24 PM »
Yes I do have debug enabled on mcp.
Are you saying mention localhost instead of the IP Address of the SIP Phone in Debug config on composer?
Can you check your configuration and see if anythig uselful info that I may be missing.

Offline Kubig

  • Hero Member
  • *****
  • Posts: 2576
  • Karma: 42
Re: composer error in gvp 8.1.6
« Reply #4 on: January 13, 2014, 10:25:39 PM »
You have to configure your ext SIP phone (IP address, port and number). As was mentioned, all is described in documentation, help and some hints are on Genesys web/wiki.
Genesys certified professional consultant (GVP, SIP, GIR and Troubleshooting)

Offline mumtazalam2k

  • Jr. Member
  • **
  • Posts: 55
  • Karma: 0
Re: composer error in gvp 8.1.6
« Reply #5 on: January 14, 2014, 03:50:56 PM »
I have configured the ext sip phone along with the IP Address, Port and Number.
However the logs do not show any hits either on MCP/RM/SIP Server nor on the composer logs.

Attaching some of the debug logs, see if I am really missing anything.
I am using the default debug configuration and I can see that the Application URL is not complete in the logs.


org.eclipse.core.runtime.CoreException: Could not start the debug target
at com.genesyslab.composer.debug.launch.AbstractComposerLaunchDelegate.abort(Unknown Source)
at com.genesyslab.rtdclient.core.launch.RTDLaunchDelegate.launch(Unknown Source)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:853)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:703)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:696)
at com.genesyslab.composer.debug.launch.AbstractComposerLaunchShortcut$1.run(Unknown Source)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: com.genesyslab.sip.tpcc.SipTPCCException: Failed to initialize SIP
at com.genesyslab.sip.tpcc.TPCController.handleError(Unknown Source)
at com.genesyslab.sip.tpcc.TPCController.initiateCall(Unknown Source)
at com.genesyslab.rtdclient.core.launch.RTDCallLauncher.launchCall(Unknown Source)
... 6 more
Caused by: javax.sip.SipException: class java.net.ConnectException Connection refused: connect null Problem connecting /10.8.76.235 5090 /10.8.76.235 for message INVITE sip:null@10.8.76.235:5090 SIP/2.0
Call-ID: fe1762df453d88a3f3775b836e721329@10.8.76.235
CSeq: 1 INVITE
From: "Debugger" <sip:debugger@10.8.76.235:50600>;tag=7vW5jsel6X1W
To: <sip:null@10.8.76.235:5090>
Via: SIP/2.0/TCP 10.8.76.235:50600;branch=z9hG4bK-353230-5b2601e126767df6d0cdf5bc848fbce5
Max-Forwards: 70
Contact: "Debugger" <sip:debugger@10.8.76.235:50600>
Call-Info: <sip:debugger@10.8.76.235>;appearance-index=1;answer-after=0
Content-Length: 0


at gov.nist.javax.sip.stack.SIPClientTransaction.sendRequest(SIPClientTransaction.java:1066)
at com.genesyslab.sip.tpcc.TPCController.inviteA(Unknown Source)
... 8 more
Caused by: java.net.SocketException: class java.net.ConnectException Connection refused: connect null Problem connecting /10.8.76.235 5090 /10.8.76.235 for message INVITE sip:null@10.8.76.235:5090 SIP/2.0
Call-ID: fe1762df453d88a3f3775b836e721329@10.8.76.235
CSeq: 1 INVITE
From: "Debugger" <sip:debugger@10.8.76.235:50600>;tag=7vW5jsel6X1W
To: <sip:null@10.8.76.235:5090>
Via: SIP/2.0/TCP 10.8.76.235:50600;branch=z9hG4bK-353230-5b2601e126767df6d0cdf5bc848fbce5
Max-Forwards: 70
Contact: "Debugger" <sip:debugger@10.8.76.235:50600>
Call-Info: <sip:debugger@10.8.76.235>;appearance-index=1;answer-after=0
Content-Length: 0


at gov.nist.javax.sip.stack.IOHandler.sendBytes(IOHandler.java:319)
at gov.nist.javax.sip.stack.TCPMessageChannel.sendMessage(TCPMessageChannel.java:524)
at gov.nist.javax.sip.stack.MessageChannel.sendMessage(MessageChannel.java:281)
at gov.nist.javax.sip.stack.SIPTransaction.sendMessage(SIPTransaction.java:884)
at gov.nist.javax.sip.stack.SIPClientTransaction.sendMessage(SIPClientTransaction.java:490)
at gov.nist.javax.sip.stack.SIPClientTransaction.sendRequest(SIPClientTransaction.java:1058)
... 9 more

anoredis

  • Guest
Re: composer error in gvp 8.1.6
« Reply #6 on: January 14, 2014, 04:25:30 PM »
Define the target DN and Sip Server IP address and port in Sip phone settings and then the MCP IP address and port in Application settings of the Debugger configuration. I believe this should get it working. - Let us know if this solved your problem
« Last Edit: January 14, 2014, 05:22:12 PM by anoredis »

Offline mumtazalam2k

  • Jr. Member
  • **
  • Posts: 55
  • Karma: 0
Re: composer error in gvp 8.1.6
« Reply #7 on: January 14, 2014, 06:38:12 PM »
Well now when running the composer application, it does not show up any errors.
However I cannot run/debug the application yet.

I have a question:-
In Composer | Debugging section, what values should the client port be set to?
I have set it as 5060-5061.



In fact in my MCP logs, I can see entries shown below.

2011-01-14T14:45:43.906 Int 50052 006F00D3-10002EEB 3432 incall_initiated 0:0
2011-01-14T14:45:58.906 Int 50130 006F00D3-10002EEB 9268 appl_begin INIT_URL=http://10.8.76.235:9002/JavaComposerProject2/src-gen/Main.vxml|DEFAULTS=file://C:\Genesys\GVP\MCP1/config/defaults-ng.vxml|ANI=sip:null@10.8.76.235:50601|DNIS=sip:dialog@10.8.51.218:5070;voicexml=http://10.8.76.235:9002/JavaComposerProject2%2Fsrc-gen%2FMain.vxml;gvp.debug=true|PROTOCOLNAME=sip|PROTOCOLVERSION=2.0|CALLIDREF=8ddee5827c791c861ed9a628c45c238f@10.8.76.235|VXMLI_TYPE=NGI
2011-01-14T14:45:58.906 Int 50016 006F00D3-10002EEB 9268 wf_lookup http://10.8.76.235:9002/JavaComposerProject2/src-gen/Main.vxml
2011-01-14T14:45:58.906 Int 50016 006F00D3-10002EEB 9268 wf_lookup file://C:/Genesys/GVP/MCP1/config/defaults-ng.vxml
2011-01-14T14:46:07.406 Int 50056 006F00D3-10002EEB 3432 call_reference 8ddee5827c791c861ed9a628c45c238f@10.8.76.235|F0E491BC-1A62-45B3-04BC-41C31EDD3067|N/A|N/A
2011-01-14T14:46:07.406 Int 50002 006F00D3-10002EEB 3432 incall_reject sip:dialog@10.8.51.218:5070;voicexml=http://10.8.76.235:9002/JavaComposerProject2%2Fsrc-gen%2FMain.vxml;gvp.debug=true|sip:null@10.8.76.235:50601|20110114996567000|N/A|N/A|N/A|error
2011-01-14T14:46:07.406 Int 50036 006F00D3-10002EEB 3520 appl_end
2011-01-14T14:47:12.656 Int 50052 006F00D3-10002EEC 3432 incall_initiated 0:0

Offline mumtazalam2k

  • Jr. Member
  • **
  • Posts: 55
  • Karma: 0
Re: composer error in gvp 8.1.6
« Reply #8 on: January 14, 2014, 09:56:07 PM »
Probably I feel now my issues is probably due to this URL form for my call flow.
http://10.8.76.235:9002/JavaComposerProject3%2Fsrc-gen%2FMain.vxml

If i replace it manually on my GVP server with the below the vxml call flow can be fetched.
http://10.8.76.235:9002/JavaComposerProject3/src-gen/Main.vxml

Not sure, if I can specifically overwrite it in the run confign in composer.

anoredis

  • Guest
Re: composer error in gvp 8.1.6
« Reply #9 on: January 14, 2014, 11:22:23 PM »
Why don't you do something simpler? Target the callflow instead of specifying URIs. This works fine for me.

Offline naviat

  • Jr. Member
  • **
  • Posts: 54
  • Karma: 0
Re: composer error in gvp 8.1.6
« Reply #10 on: March 29, 2016, 01:20:51 PM »
Well now when running the composer application, it does not show up any errors.
However I cannot run/debug the application yet.

I have a question:-
In Composer | Debugging section, what values should the client port be set to?
I have set it as 5060-5061.



In fact in my MCP logs, I can see entries shown below.

2011-01-14T14:45:43.906 Int 50052 006F00D3-10002EEB 3432 incall_initiated 0:0
2011-01-14T14:45:58.906 Int 50130 006F00D3-10002EEB 9268 appl_begin INIT_URL=http://10.8.76.235:9002/JavaComposerProject2/src-gen/Main.vxml|DEFAULTS=file://C:\Genesys\GVP\MCP1/config/defaults-ng.vxml|ANI=sip:null@10.8.76.235:50601|DNIS=sip:dialog@10.8.51.218:5070;voicexml=http://10.8.76.235:9002/JavaComposerProject2%2Fsrc-gen%2FMain.vxml;gvp.debug=true|PROTOCOLNAME=sip|PROTOCOLVERSION=2.0|CALLIDREF=8ddee5827c791c861ed9a628c45c238f@10.8.76.235|VXMLI_TYPE=NGI
2011-01-14T14:45:58.906 Int 50016 006F00D3-10002EEB 9268 wf_lookup http://10.8.76.235:9002/JavaComposerProject2/src-gen/Main.vxml
2011-01-14T14:45:58.906 Int 50016 006F00D3-10002EEB 9268 wf_lookup file://C:/Genesys/GVP/MCP1/config/defaults-ng.vxml
2011-01-14T14:46:07.406 Int 50056 006F00D3-10002EEB 3432 call_reference 8ddee5827c791c861ed9a628c45c238f@10.8.76.235|F0E491BC-1A62-45B3-04BC-41C31EDD3067|N/A|N/A
2011-01-14T14:46:07.406 Int 50002 006F00D3-10002EEB 3432 incall_reject sip:dialog@10.8.51.218:5070;voicexml=http://10.8.76.235:9002/JavaComposerProject2%2Fsrc-gen%2FMain.vxml;gvp.debug=true|sip:null@10.8.76.235:50601|20110114996567000|N/A|N/A|N/A|error
2011-01-14T14:46:07.406 Int 50036 006F00D3-10002EEB 3520 appl_end
2011-01-14T14:47:12.656 Int 50052 006F00D3-10002EEC 3432 incall_initiated 0:0

I have the sample issue with you? Do you rÍmmber any solution for this? hope so.

Offline Kubig

  • Hero Member
  • *****
  • Posts: 2576
  • Karma: 42
Re: composer error in gvp 8.1.6
« Reply #11 on: March 29, 2016, 07:52:18 PM »
It is usually caused by incorrect SIP configuration
Genesys certified professional consultant (GVP, SIP, GIR and Troubleshooting)