Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Send all 4000's series numbers down route 6 1
- Thread starter RyanEOD
- Start date
NortelGuy1979
Programmer
Your endpoint config looks wrong. Out and rebuild it as a dynamic SIP, with the name that your signaling server has under "SIP Gateway Endpoint Name"; no IP address needed. Can you screenshot that please?
Then, the number you want to call goes as a CDP number under the Asterisk endpoint.
-M
Matthew - Technical Support Engineer
Then, the number you want to call goes as a CDP number under the Asterisk endpoint.
-M
Matthew - Technical Support Engineer
- Thread starter
- #42
Where is "SIP Gateway Endpoint Name"?
I have this set in the Asterisk Routing table:
I have this set in the Asterisk Routing table:
NortelGuy1979
Programmer
SIP Gateway Endpoint name is configured in the telephony node, under each Signaling Server (expand the signaling server section). Sorry; I don't have a webspace ...
Matthew - Technical Support Engineer
Matthew - Technical Support Engineer
- Thread starter
- #44
Matthew, it is set as tmetss in there and I am set as that also.
NortelGuy1979
Programmer
Sorry; I completely missed your trace. It's getting to the Asterisk now. Asterisk is replying with:
SIPCallTrace: (16/09/10 17:09:53) Incoming -- response 401 Unauthorized chid: 6 Far End Signaling IP: 192.168.1.80:5060 Calling: 6785 Called : 4790
and
SIPCallTrace: (16/09/10 17:09:53) Incoming -- response 403 Forbidden chid: 6 Far End Signaling IP: 192.168.1.80:5060 Calling: 6785 Called : 4790
Time to hunt down that Asterisk guru and see what the Asterisk doesn't like on the SIP INVITE. You're definitely reaching the Asterisk now though.
Matthew - Technical Support Engineer
SIPCallTrace: (16/09/10 17:09:53) Incoming -- response 401 Unauthorized chid: 6 Far End Signaling IP: 192.168.1.80:5060 Calling: 6785 Called : 4790
and
SIPCallTrace: (16/09/10 17:09:53) Incoming -- response 403 Forbidden chid: 6 Far End Signaling IP: 192.168.1.80:5060 Calling: 6785 Called : 4790
Time to hunt down that Asterisk guru and see what the Asterisk doesn't like on the SIP INVITE. You're definitely reaching the Asterisk now though.
Matthew - Technical Support Engineer
- Thread starter
- #46
- Thread starter
- #47
Matthew, Also I am still getting:
oam> 16/09/2010 18:26:46 LOG0003 GKNPM: gkNpmLightRRQ: Non-Ras Endpoint tmetss 192.168.1.30 is trying to register
16/09/2010 18:26:46 LOG0004 GKNPM: ITG4065 Endpoint tmetss 192.168.1.30 status: Unregistered (93)
16/09/2010 18:26:46 LOG0003 NPM: cmEvRASReject: GK 192.168.1.32 Registration rejected
16/09/2010 18:26:54 LOG0003 SIPNPM: CSTAAmlHandler_ItgMsgPBXAmlLinkRes: pbxAmlLinkInit( Unknown 0x1 )
16/09/2010 18:26:56 LOG0004 GKNPM: ITG4065 Endpoint tmetss 192.168.1.30 status: Registered (93)
16/09/2010 18:26:56 LOG0006 NPM: cmEvRASConfirm: GK 192.168.1.32, Registration OK, rasSession(0x2d11391c)
Is there any way to clean this up? As I know it has to do with what I have done because the problem wasn't there before!
oam> 16/09/2010 18:26:46 LOG0003 GKNPM: gkNpmLightRRQ: Non-Ras Endpoint tmetss 192.168.1.30 is trying to register
16/09/2010 18:26:46 LOG0004 GKNPM: ITG4065 Endpoint tmetss 192.168.1.30 status: Unregistered (93)
16/09/2010 18:26:46 LOG0003 NPM: cmEvRASReject: GK 192.168.1.32 Registration rejected
16/09/2010 18:26:54 LOG0003 SIPNPM: CSTAAmlHandler_ItgMsgPBXAmlLinkRes: pbxAmlLinkInit( Unknown 0x1 )
16/09/2010 18:26:56 LOG0004 GKNPM: ITG4065 Endpoint tmetss 192.168.1.30 status: Registered (93)
16/09/2010 18:26:56 LOG0006 NPM: cmEvRASConfirm: GK 192.168.1.32, Registration OK, rasSession(0x2d11391c)
Is there any way to clean this up? As I know it has to do with what I have done because the problem wasn't there before!
NortelGuy1979
Programmer
Hehe, you're quite welcome. I'm usually Phoenix, but in Kansas City at the moment.
SIP interop can be tricky with other systems, Nortel's is designed to be a peer-to-peer so the phone context and the like can be weird to other systems.
You can play with numbering type in NRS and on your DMI to find a combination that works for the Asterisk. Just run that SIP trace for each test and make sure you're actually getting to the Asterisk (look for 192.168.1.80) and not getting hosed up in NRS with the number lookup. For example, if you changed the number type in NRS to E.164 national, the lookup would fail.
Hopefully, a session border controller won't be necessary, but Nortel now makes a SIP Trunk Bridge with R7.0 that is basically a lightweight SBC...
Good luck!
-Matthew
Matthew - Technical Support Engineer
SIP interop can be tricky with other systems, Nortel's is designed to be a peer-to-peer so the phone context and the like can be weird to other systems.
You can play with numbering type in NRS and on your DMI to find a combination that works for the Asterisk. Just run that SIP trace for each test and make sure you're actually getting to the Asterisk (look for 192.168.1.80) and not getting hosed up in NRS with the number lookup. For example, if you changed the number type in NRS to E.164 national, the lookup would fail.
Hopefully, a session border controller won't be necessary, but Nortel now makes a SIP Trunk Bridge with R7.0 that is basically a lightweight SBC...
Good luck!
-Matthew
Matthew - Technical Support Engineer
- Thread starter
- #49
Matt, this one:
Matthew, Also I am still getting:
oam> 16/09/2010 18:26:46 LOG0003 GKNPM: gkNpmLightRRQ: Non-Ras Endpoint tmetss 192.168.1.30 is trying to register
16/09/2010 18:26:46 LOG0004 GKNPM: ITG4065 Endpoint tmetss 192.168.1.30 status: Unregistered (93)
16/09/2010 18:26:46 LOG0003 NPM: cmEvRASReject: GK 192.168.1.32 Registration rejected
16/09/2010 18:26:54 LOG0003 SIPNPM: CSTAAmlHandler_ItgMsgPBXAmlLinkRes: pbxAmlLinkInit( Unknown 0x1 )
16/09/2010 18:26:56 LOG0004 GKNPM: ITG4065 Endpoint tmetss 192.168.1.30 status: Registered (93)
16/09/2010 18:26:56 LOG0006 NPM: cmEvRASConfirm: GK 192.168.1.32, Registration OK, rasSession(0x2d11391c)
Is there any way to clean this up? As I know it has to do with what I have done because the problem wasn't there before!
Matthew, Also I am still getting:
oam> 16/09/2010 18:26:46 LOG0003 GKNPM: gkNpmLightRRQ: Non-Ras Endpoint tmetss 192.168.1.30 is trying to register
16/09/2010 18:26:46 LOG0004 GKNPM: ITG4065 Endpoint tmetss 192.168.1.30 status: Unregistered (93)
16/09/2010 18:26:46 LOG0003 NPM: cmEvRASReject: GK 192.168.1.32 Registration rejected
16/09/2010 18:26:54 LOG0003 SIPNPM: CSTAAmlHandler_ItgMsgPBXAmlLinkRes: pbxAmlLinkInit( Unknown 0x1 )
16/09/2010 18:26:56 LOG0004 GKNPM: ITG4065 Endpoint tmetss 192.168.1.30 status: Registered (93)
16/09/2010 18:26:56 LOG0006 NPM: cmEvRASConfirm: GK 192.168.1.32, Registration OK, rasSession(0x2d11391c)
Is there any way to clean this up? As I know it has to do with what I have done because the problem wasn't there before!
NortelGuy1979
Programmer
I think the NRS endpoint is hosed up; that's why I'd delete it and rebuild it as a dynamic SIP endpoint with the SIP Gateway name "tmetss"; right now if I remember right you have it as dynamic SIP but the IP address is typed in there too (and it's the wrong IP; you always put in the Node IP not the individual SS IP).
Build it w/ no password, then delete the SIP Gateway Authentication Password in the SS configuration, then transmit it again. Something may have just gotten confused in the software with all the messing around we were doing.
-Matthew
Matthew - Technical Support Engineer
Build it w/ no password, then delete the SIP Gateway Authentication Password in the SS configuration, then transmit it again. Something may have just gotten confused in the software with all the messing around we were doing.
-Matthew
Matthew - Technical Support Engineer
- Thread starter
- #51
NortelGuy1979
Programmer
I'd imagine you can just put any value like 1234 (that may even be the default); it won't matter unless authentication is turned on in NRS at the UDP, CDP or endpoint level...
Matthew - Technical Support Engineer
Matthew - Technical Support Engineer
- Thread starter
- #53
At UDP, Asterisk and tmetss it was set to not configured, I changed it to Authentication off on all.
Still flip flopping:
17/09/2010 10:06:03 LOG0006 mud1_t9: Turn on checkpointing operation after commit.
17/09/2010 10:06:03 LOG0006 mud1_t9: Turn on checkpointing successfully.
17/09/2010 10:06:03 LOG0006 GKNPM: nrsDBSettingsSelect: Updated DBSettings Cache!
17/09/2010 10:06:03 LOG0004 GKNPM: ITG4065 Endpoint tmetss 192.168.1.30 status: Registered (93)
17/09/2010 10:06:03 LOG0006 NPM: cmEvRASConfirm: GK 192.168.1.32, Registration OK, rasSession(0x2d11228c)
17/09/2010 10:06:14 LOG0003 SIPNPM: CSTAAmlHandler_ItgMsgPBXAmlLinkRes: pbxAmlLinkInit( Unknown 0x1 )
17/09/2010 10:06:28 LOG0003 GKNPM: gkNpmLightRRQ: Non-Ras Endpoint tmetss 192.168.1.30 is trying to register
17/09/2010 10:06:28 LOG0004 GKNPM: ITG4065 Endpoint tmetss 192.168.1.30 status: Unregistered (93)
17/09/2010 10:06:28 LOG0003 NPM: cmEvRASReject: GK 192.168.1.32 Registration rejected
17/09/2010 10:06:29 LOG0003 SIPNPM: CSTAAmlHandler_ItgMsgPBXAmlLinkRes: pbxAmlLinkInit( Unknown 0x1 )
Still flip flopping:
17/09/2010 10:06:03 LOG0006 mud1_t9: Turn on checkpointing operation after commit.
17/09/2010 10:06:03 LOG0006 mud1_t9: Turn on checkpointing successfully.
17/09/2010 10:06:03 LOG0006 GKNPM: nrsDBSettingsSelect: Updated DBSettings Cache!
17/09/2010 10:06:03 LOG0004 GKNPM: ITG4065 Endpoint tmetss 192.168.1.30 status: Registered (93)
17/09/2010 10:06:03 LOG0006 NPM: cmEvRASConfirm: GK 192.168.1.32, Registration OK, rasSession(0x2d11228c)
17/09/2010 10:06:14 LOG0003 SIPNPM: CSTAAmlHandler_ItgMsgPBXAmlLinkRes: pbxAmlLinkInit( Unknown 0x1 )
17/09/2010 10:06:28 LOG0003 GKNPM: gkNpmLightRRQ: Non-Ras Endpoint tmetss 192.168.1.30 is trying to register
17/09/2010 10:06:28 LOG0004 GKNPM: ITG4065 Endpoint tmetss 192.168.1.30 status: Unregistered (93)
17/09/2010 10:06:28 LOG0003 NPM: cmEvRASReject: GK 192.168.1.32 Registration rejected
17/09/2010 10:06:29 LOG0003 SIPNPM: CSTAAmlHandler_ItgMsgPBXAmlLinkRes: pbxAmlLinkInit( Unknown 0x1 )
NortelGuy1979
Programmer
I think I got it; H323 is or got turned on in the signaling server; GKNPM and NPM are H.323 registration modules. SIPNPM is for SIP. You can either add an H.323 endpoint in your NRS with the same name (it should be a RAS endpoint, IE, dynamic) as appears in the H323 settings of your signaling server, or, you can uncheck h.323 from the signaling server and telephony node config.
-Matthew
Matthew - Technical Support Engineer
-Matthew
Matthew - Technical Support Engineer
NortelGuy1979
Programmer
Solution Detail
H323 Registration rejected error message
Problem Description
The Network Routing Service (NRS) rejects the H323 Gatekeeper (GK) registration request:
27/08/2009 07:36:53 LOG0003 NPM: cmEvRASReject: GK 10.192.102.1 Registration rejected
27/08/2009 07:36:53 LOG0003 NPM: cmEvRASReject: GK 10.192.104.2 Registration rejected
Cause of problem
The endpoint is not using H323 protocol.
Problem Resolution
Unselect H323 from the Signaling Server (SS) setting and reboot the SS.
Affected Products
Enterprise VoIP Core CS 1000E
Enterprise VoIP Core CS 1000M Chassis/Cabinet
Enterprise VoIP Core CS 1000M Half Group
Enterprise VoIP Core CS 1000M Multi Group
Enterprise VoIP Core CS 1000M Single Group
Enterprise VoIP Core CS 1000S
Matthew - Technical Support Engineer
H323 Registration rejected error message
Problem Description
The Network Routing Service (NRS) rejects the H323 Gatekeeper (GK) registration request:
27/08/2009 07:36:53 LOG0003 NPM: cmEvRASReject: GK 10.192.102.1 Registration rejected
27/08/2009 07:36:53 LOG0003 NPM: cmEvRASReject: GK 10.192.104.2 Registration rejected
Cause of problem
The endpoint is not using H323 protocol.
Problem Resolution
Unselect H323 from the Signaling Server (SS) setting and reboot the SS.
Affected Products
Enterprise VoIP Core CS 1000E
Enterprise VoIP Core CS 1000M Chassis/Cabinet
Enterprise VoIP Core CS 1000M Half Group
Enterprise VoIP Core CS 1000M Multi Group
Enterprise VoIP Core CS 1000M Single Group
Enterprise VoIP Core CS 1000S
Matthew - Technical Support Engineer
- Thread starter
- #56
- Thread starter
- #57
WOW, that got rid of most of the errors now I am only getting:
17/09/2010 11:16:59 LOG0003 SIPNPM: CSTAAmlHandler_ItgMsgPBXAmlLinkRes: pbxAmlLinkInit( Unknown 0x1 )
17/09/2010 11:17:14 LOG0003 SIPNPM: CSTAAmlHandler_ItgMsgPBXAmlLinkRes: pbxAmlLinkInit( Unknown 0x1 )
17/09/2010 11:17:29 LOG0003 SIPNPM: CSTAAmlHandler_ItgMsgPBXAmlLinkRes: pbxAmlLinkInit( Unknown 0x1 )
17/09/2010 11:17:44 LOG0003 SIPNPM: CSTAAmlHandler_ItgMsgPBXAmlLinkRes: pbxAmlLinkInit( Unknown 0x1 )
17/09/2010 11:17:59 LOG0003 SIPNPM: CSTAAmlHandler_ItgMsgPBXAmlLinkRes: pbxAmlLinkInit( Unknown 0x1 )
17/09/2010 11:16:59 LOG0003 SIPNPM: CSTAAmlHandler_ItgMsgPBXAmlLinkRes: pbxAmlLinkInit( Unknown 0x1 )
17/09/2010 11:17:14 LOG0003 SIPNPM: CSTAAmlHandler_ItgMsgPBXAmlLinkRes: pbxAmlLinkInit( Unknown 0x1 )
17/09/2010 11:17:29 LOG0003 SIPNPM: CSTAAmlHandler_ItgMsgPBXAmlLinkRes: pbxAmlLinkInit( Unknown 0x1 )
17/09/2010 11:17:44 LOG0003 SIPNPM: CSTAAmlHandler_ItgMsgPBXAmlLinkRes: pbxAmlLinkInit( Unknown 0x1 )
17/09/2010 11:17:59 LOG0003 SIPNPM: CSTAAmlHandler_ItgMsgPBXAmlLinkRes: pbxAmlLinkInit( Unknown 0x1 )
NortelGuy1979
Programmer
Hmm; do a pbxLinkShow:
(oam)> pbxLinkShow
Active Call Server type = CS 1000E
Active Call Server S/W Release = 550J
Supported Features: CorpDir UserKeyLabel VirtualOffice UseCSPwd 2001P2 2004P2 2002P2 PD/RL/CL QoS Monitoring NAT Traversal ACF IP ACD 1150 NextGen Phones IP Phones 1
200
Call Server Main: ip = 137.135.128.253, ConnectID = 0x2e16c478, BroadcastID = 0x2e16c378, Link is up
Call Server Signaling Port = 15000
Call Server Broadcast Port = 15001
Broadcast PortID = 0x2d9958e0
RUDP portID = 0x2d995940
Tcp Link state = up
Tcp Signaling Port: 15000
Tcp socket fd: 29
Tcp msgs sent: 1042337
Tcp msgs recd: 13631772
Matthew - Technical Support Engineer
(oam)> pbxLinkShow
Active Call Server type = CS 1000E
Active Call Server S/W Release = 550J
Supported Features: CorpDir UserKeyLabel VirtualOffice UseCSPwd 2001P2 2004P2 2002P2 PD/RL/CL QoS Monitoring NAT Traversal ACF IP ACD 1150 NextGen Phones IP Phones 1
200
Call Server Main: ip = 137.135.128.253, ConnectID = 0x2e16c478, BroadcastID = 0x2e16c378, Link is up
Call Server Signaling Port = 15000
Call Server Broadcast Port = 15001
Broadcast PortID = 0x2d9958e0
RUDP portID = 0x2d995940
Tcp Link state = up
Tcp Signaling Port: 15000
Tcp socket fd: 29
Tcp msgs sent: 1042337
Tcp msgs recd: 13631772
Matthew - Technical Support Engineer
- Thread starter
- #59
pbxLinkShow
Active Call Server type = CS 1000E
Active Call Server S/W Release = 500W
Supported Features: CorpDir UserKeyLabel VirtualOffice UseCSPwd 2001P2 2004P2 2002P2 PD/RL/CL QoS Monitoring NAT Traversal ACF IP ACD 1150 NextGen Phones
Call Server Main: ip = 137.135.128.253, ConnectID = 0x2e16b878, BroadcastID = 0x2e16b778, Link is up
Call Server Signaling Port = 15000
Call Server Broadcast Port = 15001
Broadcast PortID = 0x2d994ce0
RUDP portID = 0x2d994d40
Tcp Link state = up
Tcp Signaling Port: 15000
Tcp socket fd: 29
Tcp msgs sent: 936
Tcp msgs recd: 15884
oam>
Active Call Server type = CS 1000E
Active Call Server S/W Release = 500W
Supported Features: CorpDir UserKeyLabel VirtualOffice UseCSPwd 2001P2 2004P2 2002P2 PD/RL/CL QoS Monitoring NAT Traversal ACF IP ACD 1150 NextGen Phones
Call Server Main: ip = 137.135.128.253, ConnectID = 0x2e16b878, BroadcastID = 0x2e16b778, Link is up
Call Server Signaling Port = 15000
Call Server Broadcast Port = 15001
Broadcast PortID = 0x2d994ce0
RUDP portID = 0x2d994d40
Tcp Link state = up
Tcp Signaling Port: 15000
Tcp socket fd: 29
Tcp msgs sent: 936
Tcp msgs recd: 15884
oam>
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Locked
- Question
- Locked
- Question