RedTech443
MIS
Hello again all.
I am attempting to install and configure Avaya Aura Messaging 6.3.1 into my lab for learning, however I am having some problems. (I am starting to feel like a regular here)
My System Info / topology.
cm 6.3 (duplicated VM's)
aam 6.3.1 (single server install)
system manager 6.3
session manager 6.3 with sp15
So far I have successfully got the AAM to register to system manager as a sip entity, but I cannot for the life of my figure out why I cannot get the signaling group and trunk groups up in CM. I have read many different documents on configuring and they are all basically the same. I think I am having some issues with my sip registration because I do not see anything happening in traceSM from session manager. I am sure I should be seeing something from CM trying to register.
My trunk is OOS/FE and Signaling group is far-end bypass
Below is some screen shots of CM
******************************************************
CM
Contains: 03.0.124.0
CM Reports as: R016x.03.0.124.0
CM Release String: vcm-016-03.0.124.0
Publication Date: 04 October 2012
UPDATES:
Update ID Status Type Update description
------------------------------- ------------ ------- ---------------------------
03.0.124.0-21904 activated hot fix for shellshock bug
03.0.124.0-22147 activated cold 6.3.10.0-SP10
VMWT-2.6.18-400.AV1-5.5-004 activated hot VMware Tools-VMTSP0004
KERNEL-2.6.18-400.AV1 activated cold KERNEL-KSP03
Platform/Security ID Status Type Update description
------------------------------- ------------ ------- ---------------------------
PLAT-rhel5.3-3019 activated cold RHEL5.3-SSP306
Messaging ID Status Type Update description
------------------------------- ------------ ------- ---------------------------
CM Translation Saved: 2015-11-03 18:47:49
CM License Installed: 2015-11-03 19:15:21
CM Memory Config: Large
************************************************************
AAM
Contains: 03.0.124.0
CM Reports as: S016x.03.0.124.0
CM Release String: vmsg-016-03.0.124.0
Publication Date: 04 October 2012
UPDATES:
Update ID Status Type Update description
------------------------------- ------------ ------- ---------------------------
03.0.124.0-21904 activated hot fix for shellshock bug
VMWT-2.6.18-400.AV2-5.5-005 activated hot VMware Tools-VMTSP0004
KERNEL-2.6.18-400.AV2 activated cold KERNEL-KSP04
Platform/Security ID Status Type Update description
------------------------------- ------------ ------- ---------------------------
PLAT-rhel5.3-3019 activated cold RHEL5.3-SSP306
Messaging ID Status Type Update description
------------------------------- ------------ ------- ---------------------------
MSG-03.0.124.0-321_0103 activated cold MSG 6.3.1 SP 1
Messaging: +-N6.3-62.0--321Cac+Aac+----mad+-
CM Information
Trunk 99
TRUNK GROUP
Group Number: 99 Group Type: sip CDR Reports: y
Group Name: MSG TRUNK COR: 1 TN: 1 TAC: *99
Direction: two-way Outgoing Display? n
Dial Access? n Night Service:
Queue Length: 0
Service Type: tie Auth Code? n
Member Assignment Method: manual
Group Type: sip
TRUNK PARAMETERS
Unicode Name: yes
Redirect On OPTIM Failure: 5000
page 2
SCCAN? n Digital Loss Group: 18
Preferred Minimum Session Refresh Interval(sec): 600
Disconnect Supervision - In? y Out? y
XOIP Treatment: auto Delay Call Setup When Accessed Via IGAR? n
Caller ID for Service Link Call to H.323 1xC: station-extension
Signaling Group 99
SIGNALING GROUP
Group Number: 99 Group Type: sip
IMS Enabled? n Transport Method: tls
Q-SIP? n
IP Video? n Enforce SIPS URI for SRTP? y
Peer Detection Enabled? y Peer Server: Others
Prepend '+' to Outgoing Calling/Alerting/Diverting/Connected Public Numbers? n
Remove '+' from Incoming Called/Calling/Alerting/Diverting/Connected Numbers? y
Alert Incoming SIP Crisis Calls? n
Near-end Node Name: procr Far-end Node Name: msgserver
Near-end Listen Port: 5061 Far-end Listen Port: 5061
Far-end Network Region: 1
Far-end Domain: sip.homebase.com
Bypass If IP Threshold Exceeded? n
Incoming Dialog Loopbacks: eliminate RFC 3389 Comfort Noise? n
DTMF over IP: rtp-payload Direct IP-IP Audio Connections? y
Session Establishment Timer(min): 3 IP Audio Hairpinning? y
Enable Layer 3 Test? y Initial IP-IP Direct Media? n
H.323 Station Outgoing Direct Media? n Alternate Route Timer(sec): 6
I am attempting to install and configure Avaya Aura Messaging 6.3.1 into my lab for learning, however I am having some problems. (I am starting to feel like a regular here)
My System Info / topology.
cm 6.3 (duplicated VM's)
aam 6.3.1 (single server install)
system manager 6.3
session manager 6.3 with sp15
So far I have successfully got the AAM to register to system manager as a sip entity, but I cannot for the life of my figure out why I cannot get the signaling group and trunk groups up in CM. I have read many different documents on configuring and they are all basically the same. I think I am having some issues with my sip registration because I do not see anything happening in traceSM from session manager. I am sure I should be seeing something from CM trying to register.
My trunk is OOS/FE and Signaling group is far-end bypass
Below is some screen shots of CM
******************************************************
CM
Contains: 03.0.124.0
CM Reports as: R016x.03.0.124.0
CM Release String: vcm-016-03.0.124.0
Publication Date: 04 October 2012
UPDATES:
Update ID Status Type Update description
------------------------------- ------------ ------- ---------------------------
03.0.124.0-21904 activated hot fix for shellshock bug
03.0.124.0-22147 activated cold 6.3.10.0-SP10
VMWT-2.6.18-400.AV1-5.5-004 activated hot VMware Tools-VMTSP0004
KERNEL-2.6.18-400.AV1 activated cold KERNEL-KSP03
Platform/Security ID Status Type Update description
------------------------------- ------------ ------- ---------------------------
PLAT-rhel5.3-3019 activated cold RHEL5.3-SSP306
Messaging ID Status Type Update description
------------------------------- ------------ ------- ---------------------------
CM Translation Saved: 2015-11-03 18:47:49
CM License Installed: 2015-11-03 19:15:21
CM Memory Config: Large
************************************************************
AAM
Contains: 03.0.124.0
CM Reports as: S016x.03.0.124.0
CM Release String: vmsg-016-03.0.124.0
Publication Date: 04 October 2012
UPDATES:
Update ID Status Type Update description
------------------------------- ------------ ------- ---------------------------
03.0.124.0-21904 activated hot fix for shellshock bug
VMWT-2.6.18-400.AV2-5.5-005 activated hot VMware Tools-VMTSP0004
KERNEL-2.6.18-400.AV2 activated cold KERNEL-KSP04
Platform/Security ID Status Type Update description
------------------------------- ------------ ------- ---------------------------
PLAT-rhel5.3-3019 activated cold RHEL5.3-SSP306
Messaging ID Status Type Update description
------------------------------- ------------ ------- ---------------------------
MSG-03.0.124.0-321_0103 activated cold MSG 6.3.1 SP 1
Messaging: +-N6.3-62.0--321Cac+Aac+----mad+-
CM Information
Trunk 99
TRUNK GROUP
Group Number: 99 Group Type: sip CDR Reports: y
Group Name: MSG TRUNK COR: 1 TN: 1 TAC: *99
Direction: two-way Outgoing Display? n
Dial Access? n Night Service:
Queue Length: 0
Service Type: tie Auth Code? n
Member Assignment Method: manual
Group Type: sip
TRUNK PARAMETERS
Unicode Name: yes
Redirect On OPTIM Failure: 5000
page 2
SCCAN? n Digital Loss Group: 18
Preferred Minimum Session Refresh Interval(sec): 600
Disconnect Supervision - In? y Out? y
XOIP Treatment: auto Delay Call Setup When Accessed Via IGAR? n
Caller ID for Service Link Call to H.323 1xC: station-extension
Signaling Group 99
SIGNALING GROUP
Group Number: 99 Group Type: sip
IMS Enabled? n Transport Method: tls
Q-SIP? n
IP Video? n Enforce SIPS URI for SRTP? y
Peer Detection Enabled? y Peer Server: Others
Prepend '+' to Outgoing Calling/Alerting/Diverting/Connected Public Numbers? n
Remove '+' from Incoming Called/Calling/Alerting/Diverting/Connected Numbers? y
Alert Incoming SIP Crisis Calls? n
Near-end Node Name: procr Far-end Node Name: msgserver
Near-end Listen Port: 5061 Far-end Listen Port: 5061
Far-end Network Region: 1
Far-end Domain: sip.homebase.com
Bypass If IP Threshold Exceeded? n
Incoming Dialog Loopbacks: eliminate RFC 3389 Comfort Noise? n
DTMF over IP: rtp-payload Direct IP-IP Audio Connections? y
Session Establishment Timer(min): 3 IP Audio Hairpinning? y
Enable Layer 3 Test? y Initial IP-IP Direct Media? n
H.323 Station Outgoing Direct Media? n Alternate Route Timer(sec): 6