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 TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Norstar VOIP Gateway
- Thread starter DigitelD
- Start date
SupportDude
Technical User
Never installed one on a BCM as its somewhat redundant, but I don't see why it shouldn't work.
-SD-
-SD-
I haven't installed one, but I do maintain a site with 3 MICS and 2 CICS that are all tied together with the Gateways. I've looked at the programming and there isn't much to it. If you can set up IP trunks on a BCM, I don't see why you couldn't configure one.
hawkflorida
Technical User
I've installed them on both CICS and MICS then networked to BCM400s and BCM50s. Question....You are talking about a N*VoIP GW on the CICS or MICS and then IP Trunks on the BCM, right? What is the issue?
Consulting -
If You're Not A Part Of The Solution, There's Good Money To Be Made In Prolonging The Problem.
Consulting -
If You're Not A Part Of The Solution, There's Good Money To Be Made In Prolonging The Problem.
- Thread starter
- #6
Here is the setup. In site A there is a BCM50 that has been upgraded to Rls 2.0. In site B there is a MICS and site C has a CICS. Sites B and C have the Norstar Gateways. The Gateways can call to each other and they can make calls to the BCM50. The issue is that the BCM50 cannot make calls to the Gateways. When they pickup and dial the destination code and the extension number they get dial tone again. Then they are able to dial the extension and ring the desired party. Nortel has verified that the programming on the Gateways and the BCM50 is correct. Now here is the kicker. The BCM50 was originally a Rls1. I troubleshooted the issue and tested a BCM50 Rls2 and the calls worked. Nortel tested their Gateways with my programming on a BCM50 Rls2 and it worked. Nortel then recommended that we upgrade because the Gateways have only been tested and verified on a Rls2. However, on this particular BCM50 we cannot get the calls to go through. Could it be that there is an issue with an upgraded BCM50 verses an original Rls2? Again, Nortel has verified all of the programming.
SHK Certified (School of Hard Knocks)
NCSS
SHK Certified (School of Hard Knocks)
NCSS
hawkflorida
Technical User
What are your settings in the BCM's Remote Gateway tab under Telephony Resources?
Consulting -
If You're Not A Part Of The Solution, There's Good Money To Be Made In Prolonging The Problem.
Consulting -
If You're Not A Part Of The Solution, There's Good Money To Be Made In Prolonging The Problem.
- Thread starter
- #8
Due to 2 of the sites having the same extension numbers we had to do things a little different. Here is the info:
Site Dest digits IP GW type GW Protocol
B 32 XXX Other None
C 22 XXX Other None
There is no option under GW Type for Norstar Gateway as there is in BCM200/400 3.X machines. Before the upgrade I played with the different options under GW Protocol.
SHK Certified (School of Hard Knocks)
NCSS
Site Dest digits IP GW type GW Protocol
B 32 XXX Other None
C 22 XXX Other None
There is no option under GW Type for Norstar Gateway as there is in BCM200/400 3.X machines. Before the upgrade I played with the different options under GW Protocol.
SHK Certified (School of Hard Knocks)
NCSS
hawkflorida
Technical User
The trunks on the far end(MICS and CICS) have Answer Mode set for Auto and DISA is turned off right? I know you said they work dialing back and forth to one another but I was just wondering.
Can you make a desti code of 3 with an absorb of none on the BCM50 routing and 3 on the IP trunk digits? Then make a test call but just dial the target extension on the MICS from the BCM.
Consulting -
If You're Not A Part Of The Solution, There's Good Money To Be Made In Prolonging The Problem.
Can you make a desti code of 3 with an absorb of none on the BCM50 routing and 3 on the IP trunk digits? Then make a test call but just dial the target extension on the MICS from the BCM.
Consulting -
If You're Not A Part Of The Solution, There's Good Money To Be Made In Prolonging The Problem.
MikeBrinkerhoff
IS-IT--Management
I'm dealing with a similar problem, linking a BCM50 v1 and a BCM50 v2. I discovered yesterday that the router at Site B wasn't handling the H.323 packets correctly. A firmware update (a costly one, at that) now includes an H.323 proxy that SHOULD fix my problem.
If nothing on the Nortel side of things gives an indicator of the problem, you may want to check the logging on the router...
-mike
If nothing on the Nortel side of things gives an indicator of the problem, you may want to check the logging on the router...
-mike
- Thread starter
- #11
Redhawkfla, yes the trunks are set for Auto and DISA is turned off.
I am curious to find out if there are ANY differences in an upgraded BCM and an out of the box Rls2. Nortel got this to work with a Rls2 and I did also, however, from this site that particular BCM does not work.
SHK Certified (School of Hard Knocks)
NCSS
I am curious to find out if there are ANY differences in an upgraded BCM and an out of the box Rls2. Nortel got this to work with a Rls2 and I did also, however, from this site that particular BCM does not work.
SHK Certified (School of Hard Knocks)
NCSS
hawkflorida
Technical User
On one system in this set up that I am using is an upgraded BCM50 Rls1 to Rls2 and so I don't think it's the issue. Heck, I've been wrong before so I'll look into that angle. I'm beginning to think my quote is coming into play here.... I regret that I am not helping you quickly enough. In situations like this I usually tear the system apart and start over but that's in a lab setting and I know that it's not so easy in the field.
Consulting -
If You're Not A Part Of The Solution, There's Good Money To Be Made In Prolonging The Problem.
Consulting -
If You're Not A Part Of The Solution, There's Good Money To Be Made In Prolonging The Problem.
- Thread starter
- #13
Here is an update:
I have tested this on 2 out of the box BCM50 Rls2.0. I get the same issue that I had with the original BCM50 that is at the customer's site. What happens is you dial the destination code and the extension number. Instead of the call ringing the set you get dial tone. You can then dial the extension again and it goes through. Nortel verified the programming on the BCM50 as well as the Gateways. Now here is the kicker. One of the BCM50's that I am using for testing actually worked 1 time when I called. I dialed the destination code and the extension number and it rang through. Now I can't get it to do it again. Someone please help me before I jump off our office building. Something I may not have mentioned is this, the customers IT tech put the BCM and the Gateway's on public IP's against our wishes. Could it be that not going through a VPN is causing trouble through the public network?
Thanks, I'll be waiting on top of our building for your reply.
SHK Certified (School of Hard Knocks)
NCSS
I have tested this on 2 out of the box BCM50 Rls2.0. I get the same issue that I had with the original BCM50 that is at the customer's site. What happens is you dial the destination code and the extension number. Instead of the call ringing the set you get dial tone. You can then dial the extension again and it goes through. Nortel verified the programming on the BCM50 as well as the Gateways. Now here is the kicker. One of the BCM50's that I am using for testing actually worked 1 time when I called. I dialed the destination code and the extension number and it rang through. Now I can't get it to do it again. Someone please help me before I jump off our office building. Something I may not have mentioned is this, the customers IT tech put the BCM and the Gateway's on public IP's against our wishes. Could it be that not going through a VPN is causing trouble through the public network?
Thanks, I'll be waiting on top of our building for your reply.
SHK Certified (School of Hard Knocks)
NCSS
- Thread starter
- #14
SupportDude
Technical User
I had a very similar problem on an E&M T1 once.
Exact symptoms!
Found out that telco was sending CLID along with the DNIS.
Is the 50 sending OLI, Name Display, or anything else the Norstar can't understand?
-SD-
Exact symptoms!
Found out that telco was sending CLID along with the DNIS.
Is the 50 sending OLI, Name Display, or anything else the Norstar can't understand?
-SD-
- Thread starter
- #16
Deweyhumbolt
Technical User
I would think you need a Gateway Protocol and Type. What are your choices?
Adversity is Opportunity
Adversity is Opportunity
- Thread starter
- #18
GW type is Other and protocol is None. Nortel verified that these were the correct settings. I wonder if we need a VPN setup instead of going out on public IP's. I wonder if we are losing info that the Norstar Gateway needs.
SHK Certified (School of Hard Knocks)
NCSS
SHK Certified (School of Hard Knocks)
NCSS
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Locked
- Question