| |||||||||
![]() | | ||||||||
| |||||||||||||||
| |||||||||||||||
| Meridian Systems Welcome to the Nortel Meridian Forums Including Meridian Options 11-81C CS1000M Meridian Mail Call Pilot Companion and Sucession Hospitality OTM MAT MICB RAN NetGateway ..., and all other Applications |
| Tags: causing, hair, loss, server, sig, stress |
![]() |
| | LinkBack | Thread Tools | Display Modes |
| | #1 (permalink) | ||||||||
| Guest
| I just installed a sig server. I am running Succession 3 on a 1000M Cabinet. It has an SMC card. The i2004 phones are working fine, but as soon as I turn on the gatekeeper functionality on my sig server I start to get the following 3 messages every 10 seconds. 29/08/04 16:43:26 LOG0003 GKNPM: gkDbmNpmRRQ: DBM_NPM_RC_invalidAlias 0 29/08/04 16:43:26 LOG0005 GKNPM: RAS FAILURE: RAS_TYPE : RRQ,Reason=invalidAlias,SrcIP=208.6.214.36:1719 29/08/04 16:43:26 LOG0003 NPM: cmEvRASReject: GK 208.6.214.37 Registration rejected I don't see where the invalid alias message comes from. The TLAN node IP is .36 and the TLAN voice IP is .37. The GK is also .37 as per the IP Peer NTP. I have included info from the sig server and the SMC card. If anyone can see an obvious config problem it would be appreciated as I have very little hair left to pull out! Gatekeeper Info --------------- GK Version : 2.11.03 GK Role : Primary GK Status : Active Alt GK status : GK_OUT_OF_SERVICE SS Role : Leader SS Primary GK IP : 208.6.214.37(1719) Alternate GK IP : 0.0.0.0(1719) Alt-GK Switchover: Permanent in service is (OFF) Npm status: Active Active GateKeeper: 208.6.214.37 (primary) GateKeeper registration status: not registered, TTL: 3595 secs, re-register: 8 secs Channels Busy / Idle / Total: 0 / 382 / 382 Stack version: RadVision 4.1.0.19 Channel tracing: -1 Signaling Server H323 ID : SSE_Node1_ldr SSE> itgCardShow Index : 1 Role : Leader Node : 1 Leader IP : 208.6.214.36 Card IP : 208.6.214.37 Uptime : 0 days, 0 hours, 46 mins, 40 secs (2800 secs) Codecs : G711Ulaw(default), G711Alaw, G711CC, T38FAX SSE> IPInfoShow Maintenance Interface = fei0 Maintenance IP address = 10.1.7.138 Maintenance subnet mask = 255.255.255.0 Voice Interface = fei1 Voice IP address = 208.6.214.37 Voice subnet mask = 255.255.255.224 SSE> electShow Node ID : 1 Node Master : Yes Up Time : 0 days, 1 hours, 54 mins, 57 secs TN : 00 00 Host Type : ISP 1100 TLAN IP Addr : 208.6.214.37 ELAN IP Addr : 10.1.7.138 Election Duration : 15 Wait for Result time : 35 Master Broadcast period : 30 ===== master tps ===== Host Type TN TLAN IP Addr ISP 1100 00 00 208.6.214.37 Next timeout : 29 sec AutoAnnounce : 1 Timer duration : 60 (Next timeout in 42 sec) ====== all tps ====== Num TN Host Type ELAN MAC TLAN IP Addr ELAN IP Addr Up Time NumOfSets TimeOut 001 00 00 ISP 1100 00:02:b3:f1:d7:e2 208.6.214.37 10.1.7.138 000 01:54:57 3 0 002 04 00 SMC 00 d8:d0:6b:7b 208.6.214.35 10.1.7.133 000 01 32 0 2====== All cards in node configuration are registered ====== SMC> itgCardShow Index : 2 Type : EXUT Role : Follower Node : 1 Leader IP : 208.6.214.36 Card IP : 208.6.214.35 Card TN : Slot 4 Card State : ENBL Uptime : 0 days, 0 hours, 4 mins, 47 secs (287 secs) Codecs : G711Ulaw(default), G711Alaw, G711CC, T38FAX ELAN (ixpMac1) stat: 10 Mbps, Half duplex (Carrier OK) TLAN (ixpMac0) stat: 100 Mbps, Full duplex (Carrier OK) SMC> IPInfoShow Maintenance Interface = ixpMac1 Maintenance IP address = 10.1.7.133 Maintenance subnet mask = 255.255.255.0 Voice Interface = ixpMac0 Voice IP address = 208.6.214.35 Voice subnet mask = 255.255.255.224 | ||||||||
|
| | #5 (permalink) | ||||||||
| Guest
| DB, electrojoe and madhu, Thanks for listening in. Yes I am in with element manager. I did not setup a RAS domain. It is the only sig server. I will check that RAS domain out. At present it is the only system but as soon as I resolve this issue I will be looking at setting up a residential/SOHO VoIP gateway that supports analog phones. Any tips there (assuming I resolve the current problem would be appreciated. | ||||||||
|
| | #7 (permalink) | ||||||||
| Guest
| Well the messages were in fact caused by having no endpoint defined in the gatekeeper for the sig server. It is also necessary that the endpoint alias match the H323 ID of the sig server because if it doesn't then the messages persist. Thanks for leading me there guys. | ||||||||
|
![]() |
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
| Thread Tools | |
| Display Modes | |
| |