Author Topic: Genesys SIP port conflict due to GVP Resource manager installation  (Read 8889 times)

Offline Vishwasam

  • Newbie
  • *
  • Posts: 28
  • Karma: 1
Genesys SIP port conflict due to GVP Resource manager installation
« on: September 18, 2014, 06:19:29 AM »
I am working on Lab environment with all components on single server. We installed framework and able to work on the register the DNs with SIP server. We are seeing the following error after installing the GVP components, particularly after installing RM

Build information:
Timestamp: Nov 22 201312:01:06
Management Framework Components:
Configuration library v.8.1.300.06
Common library v.8.1.300.14 C2 MT-Safe
Service library v.8.1.300.04 MT
Message library v.8.1.300.00
Log library v.8.1.300.07 MT
LCA library v.8.1.300.07
Thread library v.8.1.300.00
GVP Components:
resourcemgr.exe v.8.5.001.89
GVP Common v.8.5.010.98
Dependencies:
SSLEAY32.dll
LIBEAY32.dll
libapr-1.dll
libaprutil-1.dll

Application name: VP_ResourceManager
Application type: CFGGVPResourceMgr (149)
Command line:    C:\Program Files\GCTI\gvp\VP Resource Manager 8.5\VP_ResourceManager\bin\resourcemgr.exe -host 192.168.3.43 -port 3030 -app VP_ResourceManager -service vpResMngr64
Host name:        WIN-B3NODD1C3U9
DST:              TZ = 0, timeb = 0
Time zone:        -19800, India Standard Time, India Daylight Time
UTC time:        2014-09-17T12:33:07.922
Local time:      2014-09-17T18:03:07.922
Start time (UTC): 2014-09-17T12:33:07
Running time:    0:00:00:00
Host info:        Windows 6.1.7600, 2, , 0.0, 0110, 3
File:            (1) ../logs/ResourceMgr.20140917_180307_924.log

2014-09-17T18:03:07.921 Std 04106 Log Messages file 'C:\Program Files\GCTI\gvp\VP Resource Manager 8.5\VP_ResourceManager\bin\..\config\RM_EMSMF.lms' successfully loaded
2014-09-17T18:03:07.926 Std 04106 Log Messages file 'C:\Program Files\GCTI\gvp\VP Resource Manager 8.5\VP_ResourceManager\bin\..\config\RM_EMSMF.lms' successfully loaded
2014-09-17T18:03:07.927 Std 02016 Unable to open log file 'D:\Genesys Logs\VP_RM Logs\rm.log.20140917_180307_928.log', error code 2
2014-09-17T18:03:07.929 Std 04503 Connected to Message server 'MessageServer' at host 'WIN-B3NODD1C3U9', port 7003
2014-09-17T18:03:09.049 Std 20145 WARN 00000000-00000000 1564 09400336 RM starts in FIPS disabled mode
2014-09-17T18:03:09.049 Std 20125 WARN 00000000-00000000 1564 09400329 SNMPAgent could not be created; SNMP will be disabled
2014-09-17T18:03:09.052 Std 20139 WARN 00000000-00000000 1564 09400331 Starting RM against Single-Tenant MF
2014-09-17T18:03:09.055 Std 20140 WARN 00000000-00000000 1564 09400332 HA mode configured with the value none, starting up in standalone mode
2014-09-17T18:03:09.055 Std 20141 NOTE 00000000-00000000 1564 0940040B loadHMTResources >> Entry()
2014-09-17T18:03:09.068 Std 20141 NOTE 00000000-00000000 1564 0940040B loadGVPRMSites >> Entry()
2014-09-17T18:03:10.875 Std 20141 NOTE 00000000-00000000 1564 0940040B loadPolicyDataStore >> Added Tenant [Environment]
2014-09-17T18:03:10.875 Std 20041 EROR 00000000-00000000 1564 09400223 loadPolicyDataStore >> Parent for tenant[1] not found
2014-09-17T18:03:10.875 Std 20141 NOTE 00000000-00000000 1564 0940040B loadPolicyDataStore >> Added Tenant [Resources]
2014-09-17T18:03:11.043 Std 20142 WARN 00000000-00000000 1564 09400333 RM Startup
2014-09-17T18:03:26.247 Std 20004 EROR 00000000-00000000 4032 08500000 Received non-RFC3261 compliance packet at SIP port, dropping the packet Cause: Invalid request/response line Message:


2014-09-17T18:03:56.248 Std 20004 EROR 00000000-00000000 4032 08500000 Received non-RFC3261 compliance packet at SIP port, dropping the packet Cause: Invalid request/response line Message:


2014-09-17T18:04:26.249 Std 20004 EROR 00000000-00000000 4032 08500000 Received non-RFC3261 compliance packet at SIP port, dropping the packet Cause: Invalid request/response line Message:


2014-09-17T18:04:56.249 Std 20004 EROR 00000000-00000000 4032 08500000 Received non-RFC3261 compliance packet at SIP port, dropping the packet Cause: Invalid request/response line Message:


2014-09-17T18:05:26.251 Std 20004 EROR 00000000-00000000 4032 08500000 Received non-RFC3261 compliance packet at SIP port, dropping the packet Cause: Invalid request/response line Message:


2014-09-17T18:05:56.251 Std 20004 EROR 00000000-00000000 4032 08500000 Received non-RFC3261 compliance packet at SIP port, dropping the packet Cause: Invalid request/response line Message:


2014-09-17T18:06:26.251 Std 20004 EROR 00000000-00000000 4032 08500000 Received non-RFC3261 compliance packet at SIP port, dropping the packet Cause: Invalid request/response line Message:


2014-09-17T18:06:56.252 Std 20004 EROR 00000000-00000000 4032 08500000 Received non-RFC3261 compliance packet at SIP port, dropping the packet Cause: Invalid request/response line Message:


2014-09-17T18:07:26.253 Std 20004 EROR 00000000-00000000 4032 08500000 Received non-RFC3261 compliance packet at SIP port, dropping the packet Cause: Invalid request/response line Message:


2014-09-17T18:07:56.254 Std 20004 EROR 00000000-00000000 4032 08500000 Received non-RFC3261 compliance packet at SIP port, dropping the packet Cause: Invalid request/response line Message:


2014-09-17T18:08:26.254 Std 20004 EROR 00000000-00000000 4032 08500000 Received non-RFC3261 compliance packet at SIP port, dropping the packet Cause: Invalid request/response line Message:


2014-09-17T18:08:56.255 Std 20004 EROR 00000000-00000000 4032 08500000 Received non-RFC3261 compliance packet at SIP port, dropping the packet Cause: Invalid request/response line Message:


2014-09-17T18:09:26.256 Std 20004 EROR 00000000-00000000 4032 08500000 Received non-RFC3261 compliance packet at SIP port, dropping the packet Cause: Invalid request/response line Message:


2014-09-17T18:09:56.256 Std 20004 EROR 00000000-00000000 4032 08500000 Received non-RFC3261 compliance packet at SIP port, dropping the packet Cause: Invalid request/response line Message:


2014-09-17T18:10:17.473 Std 20141 NOTE 00000000-00000000 5412 0940040B updateNotification()
2014-09-17T18:10:17.473 Std 20141 NOTE 00000000-00000000 5412 0940040B processResourceMgrUpdate()
2014-09-17T18:10:17.475 Std 20141 NOTE 00000000-00000000 5412 0940040B updateNotification()
2014-09-17T18:10:17.475 Std 20141 NOTE 00000000-00000000 5412 0940040B ProcessUSPAppUpdate()
2014-09-17T18:10:26.257 Std 20004 EROR 00000000-00000000 4032 08500000 Received non-RFC3261 compliance packet at SIP port, dropping the packet Cause: Invalid request/response line Message:


2014-09-17T18:10:27.098 Std 20143 WARN 00000000-00000000 1564 09400334 RM Shutdown

Offline Kubig

  • Hero Member
  • *****
  • Posts: 2752
  • Karma: 44
Re: Genesys SIP port conflict due to GVP Resource manager installation
« Reply #1 on: September 18, 2014, 07:35:44 AM »
Did you change the default SIP port range for RM object?

Offline cavagnaro

  • Administrator
  • Hero Member
  • *****
  • Posts: 7639
  • Karma: 56330
Re: Genesys SIP port conflict due to GVP Resource manager installation
« Reply #2 on: September 18, 2014, 01:25:49 PM »
Remember that was a bug on RM 8.1, 8.5 should have the fix.


Offline Vishwasam

  • Newbie
  • *
  • Posts: 28
  • Karma: 1
Re: Genesys SIP port conflict due to GVP Resource manager installation
« Reply #3 on: September 18, 2014, 02:05:05 PM »
[quote author=cavagnaro link=topic=8518.msg37486#msg37486 date=1411046749]
Remember that was a bug on RM 8.1, 8.5 should have the fix.
[/quote]

What would be the ideal port number to change ?

Offline cavagnaro

  • Administrator
  • Hero Member
  • *****
  • Posts: 7639
  • Karma: 56330
Re: Genesys SIP port conflict due to GVP Resource manager installation
« Reply #4 on: September 18, 2014, 03:45:48 PM »
Depends on your environment. I have MCP on 5070, RM on 5060 and SIP Server on 5066. But is just my configuration. There are other ports opened. What I think is your error is that something else is sending non SIP data to the RM SIP proxy port. Verify your connections and configurations

Offline Vishwasam

  • Newbie
  • *
  • Posts: 28
  • Karma: 1
Re: Genesys SIP port conflict due to GVP Resource manager installation
« Reply #5 on: September 24, 2014, 05:52:56 AM »
Thanks. I was able to resolve the Port issue but unable to start the RM or MCP below are the logs
RM log:

Build information:
Timestamp: Nov 22 201312:01:06
Management Framework Components:
Configuration library v.8.1.300.06
Common library v.8.1.300.14 C2 MT-Safe
Service library v.8.1.300.04 MT
Message library v.8.1.300.00
Log library v.8.1.300.07 MT
LCA library v.8.1.300.07
Thread library v.8.1.300.00
GVP Components:
resourcemgr.exe v.8.5.001.89
GVP Common v.8.5.010.98
Dependencies:
SSLEAY32.dll
LIBEAY32.dll
libapr-1.dll
libaprutil-1.dll

Application name: VP_ResourceManager
Application type: CFGGVPResourceMgr (149)
Command line:    C:\Program Files\GCTI\gvp\VP Resource Manager 8.5\VP_ResourceManager_850\bin\resourcemgr.exe -host 192.168.3.43 -port 3030 -app VP_ResourceManager -service vpResMngr64
Host name:        WIN-B3NODD1C3U9
DST:              TZ = 0, timeb = 0
Time zone:        -19800, India Standard Time, India Daylight Time
UTC time:        2014-09-24T05:28:18.728
Local time:      2014-09-24T10:58:18.728
Start time (UTC): 2014-09-24T05:28:18
Running time:    0:00:00:00
Host info:        Windows 6.1.7600, 2, , 0.0, 0110, 3
File:            (1) ../logs/ResourceMgr.20140924_105818_728.log

2014-09-24T10:58:18.727 Std 04106 Log Messages file 'C:\Program Files\GCTI\gvp\VP Resource Manager 8.5\VP_ResourceManager_850\bin\..\config\RM_EMSMF.lms' successfully loaded
2014-09-24T10:58:18.736 Std 04106 Log Messages file 'C:\Program Files\GCTI\gvp\VP Resource Manager 8.5\VP_ResourceManager_850\bin\..\config\RM_EMSMF.lms' successfully loaded
2014-09-24T10:58:21.913 Std 20125 WARN 00000000-00000000 2748 09400329 SNMPAgent could not be created; SNMP will be disabled
2014-09-24T10:58:21.915 Std 20139 WARN 00000000-00000000 2748 09400331 Starting RM against Single-Tenant MF
2014-09-24T10:58:21.918 Std 20140 WARN 00000000-00000000 2748 09400332 HA mode configured with the value none, starting up in standalone mode
2014-09-24T10:58:21.918 Std 20141 NOTE 00000000-00000000 2748 0940040B populateLogicalResourceObject >> Setting Logical Resource Properties: name:desc:service-types:port-usage-type:is-cti:cti-res:cti-flag:monitor-method:conf-max-cnt:conf-max-size [VP_ResourceManager]:[]:[gateway]:[in-and-out]:[no-cti]:[-1]:[undefined]:[none]:[2147483647]:[-1]
2014-09-24T10:58:21.918 Std 20141 NOTE 00000000-00000000 2748 0940040B populateLogicalResourceObject >> Setting Logical Resource Properties: name:preference:load-balance-scheme:geolocation [VP_ResourceManager]:[0]:[round-robin]:[]
2014-09-24T10:58:21.918 Std 20141 NOTE 00000000-00000000 2748 0940040B loadGVPResourceProvisionTable >> Added Logical Resource [VP_ResourceManager] to Provision Table
2014-09-24T10:58:21.919 Std 20141 NOTE 00000000-00000000 2748 0940040B populatePhysicalResourceObject >> Setting Physical Resource Properties: aor:port-cap [sip:192.168.3.43:5060]:[100]
2014-09-24T10:58:21.919 Std 20141 NOTE 00000000-00000000 2748 0940040B loadGVPResourceProvisionTable >> Added Physical Resource [SIP Server] to Provision Table
2014-09-24T10:58:21.919 Std 20141 NOTE 00000000-00000000 2748 0940040B loadHMTResources >> Entry()
2014-09-24T10:58:21.931 Std 20141 NOTE 00000000-00000000 2748 0940040B loadGVPRMSites >> Entry()
2014-09-24T10:58:22.085 Std 20007 EROR 00000000-00000000 2748 09400201 Failed to initialize ResourceModule [-117]
2014-09-24T10:58:22.085 Std 20143 WARN 00000000-00000000 2748 09400334 RM Shutdown
2014-09-24T10:58:22.085 Std 20006 CRIT 00000000-00000000 2748 09400101 ResourceMgr Proxy::Initialize failed

MCP log:


Build information:
Timestamp: Dec  9 201318:42:46
Management Framework Components:
Configuration library v.8.1.300.06
Common library v.8.1.300.14 C2 MT-Safe
Service library v.8.1.300.04 MT
Message library v.8.1.300.00
Log library v.8.1.300.07 MT
LCA library v.8.1.300.07
Thread library v.8.1.300.00
GVP Components:
pwcallmgr.exe v.8.5.041.14
GVP Common v.8.5.011.11
Dependencies:
js32.dll
nspr4.dll
SSLEAY32.dll
LIBEAY32.dll
libcurl.dll

Application name: VP_MediaControlPlatform
Application type: CFGGVPMCP (145)
Command line:    C:\Program Files\GCTI\gvp\VP Media Control Platform 8.5\VP_MediaControlPlatform\bin\pwcallmgr.exe -host 192.168.3.43 -port 3030 -app VP_MediaControlPlatform -service vpMediaControl64
Host name:        WIN-B3NODD1C3U9
DST:              TZ = 0, timeb = 0
Time zone:        -19800, India Standard Time, India Daylight Time
UTC time:        2014-09-24T05:30:30.619
Local time:      2014-09-24T11:00:30.619
Start time (UTC): 2014-09-24T05:30:30
Running time:    0:00:00:00
Host info:        Windows 6.1.7600, 2, , 0.0, 0110, 3
File:            (1) ../logs/MCP.20140924_110030_612.log

2014-09-24T11:00:30.608 Std 04106 Log Messages file '..\config/MCP_EMSMF.lms' successfully loaded
2014-09-24T11:00:30.640 Std 04106 Log Messages file '..\config/MCP_EMSMF.lms' successfully loaded
2014-09-24T11:00:30.641 Std 02016 Unable to open log file 'D:\Genesys Logs\VP_MCP Logs\mcp.log.20140924_110030_642.log', error code 2
2014-09-24T11:00:30.643 Std 04503 Connected to Message server 'MessageServer' at host 'WIN-B3NODD1C3U9', port 7003
2014-09-24T11:00:36.201 Std 20165 CRIT 00000000-00000000 5416 01F003EE Configuration parameter callmgr.linemanagers is not set properly.



Offline Kubig

  • Hero Member
  • *****
  • Posts: 2752
  • Karma: 44
Re: Genesys SIP port conflict due to GVP Resource manager installation
« Reply #6 on: September 24, 2014, 05:39:03 PM »
[quote author=cavagnaro link=topic=8518.msg37486#msg37486 date=1411046749]
Remember that was a bug on RM 8.1, 8.5 should have the fix.
[/quote]
Cav, which bug did you mean?

Offline cavagnaro

  • Administrator
  • Hero Member
  • *****
  • Posts: 7639
  • Karma: 56330
Re: Genesys SIP port conflict due to GVP Resource manager installation
« Reply #7 on: September 24, 2014, 07:46:20 PM »
come on dude, read your logs at least...answers are there....

Configuration parameter callmgr.linemanagers is not set properly.

Hey Kubig,
One that when a malformed packet arrived MCP crashed... I had an MCP once running for 6 months, then a network issue began to make some noise and MPC crashed...solution was upgrade

Offline Kubig

  • Hero Member
  • *****
  • Posts: 2752
  • Karma: 44
Re: Genesys SIP port conflict due to GVP Resource manager installation
« Reply #8 on: September 25, 2014, 05:01:24 AM »
Yes, I know about that. Not only MCP has the problem and the packet may not be malformed, the security port scanner (vulnerability scan) cause similar issue.
I have bad understood your previous post that the latest RM has different default SIP port range from release 8.1 :-)

Offline cavagnaro

  • Administrator
  • Hero Member
  • *****
  • Posts: 7639
  • Karma: 56330
Re: Genesys SIP port conflict due to GVP Resource manager installation
« Reply #9 on: September 25, 2014, 03:28:59 PM »
Oh...no hehe ;)