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!

SCN dialing only works one-way intermittently

Status
Not open for further replies.

tmckeown

IS-IT--Management
Nov 15, 2002
448
US
Hi,
I've got two phone systems, a IP412 and an IP406. They are in different states and are programmed for SCN so we can dial extensions from either location and get to anyone within the domain. In the last few weeks, I'm finding that users on the IP406 system are (intermittently) unable to initiate calls to the IP412 system. Everyone on the IP412 can make direct calls via extension number to the IP406 system. Can someone give me a few ideas on what to look for and how to diagnose the problem? It seems that this problem began when we changed the ISP for the IP412 system. We went from a local carrier to Frontier and now have a 100MB up/down connection. So, speed doesn't seem to be the cause. Could it have anything to do with VCM usage? It's very odd. yesterday it worked fine all day and today they can't call extensions from the IP406 system. it has been working fine for 8 years. It seems to have only started having the problem when we changed ISP. I had them check MTU and all seems fine there. Got any ideas?

IP412 3.2 (69)
IP406 3.2 (69)

Thanks for the help
 
Thank you very much amriddle01
I will keep working on this till I solve it or go insane and have to be institutionalized.
 
delete and add the trunks again reboot the units and it will work again. seen it before.

Avaya_Red.gif

___________________________________________
It works! Now if only I could remember what I did...

Dain Bramaged (Avaya Search tool )
______________________________________
 
Bas1234
When you say "Delete trunks", do you mean remove the IP routes and IP line and add them again or are you thinking something different?
 
I deleted the IP Routes on the LA system, recreated them and rebooted their IP Office. Same results. They get a "INCOMPATIBLE" when they dial my extension in Chicago. I have not trouble getting to them.
 
Not the routes, the trunks that form the SCN in system programming :)

 
I'm feeling like a total idiot, but I need clarification. Are you refering to the IP line? Sorry to sound so stupid. I just don't see anything that says "trunk" in my version of Manager (3.2 (69))
 
I did a lot more tests today. I deleted the trunks (IP Line) used for SCN and recreated it on both sides. Then I rebooted both systems. Still the same problem. The problem seemed to appear when we changed over to a new ISP at the Chicago office. So, I setup another firewall and created the tunnel using our old ISP (yes, I'm still paying for it but hopefully not for long). I thought this would cure the problem. I was wrong. We had the exact same problem. I guess I can rule out the ISP now.

Chicago can call LA
LA can't call Chicago
Would you think there is a misconfiguration in LA or in Chicago?
I'm going to start looking for someone smarter than me to jump in and help. I'm really out of ideas.
 
It looks like it's what multiple folks keep saying....the Sonicwalls, they are renowned for such issues and being difficult to figure out what it is. Unless of course during your testing you eliminated Sonicwalls from the equation :)

 
Well if you have a support contract you could have your vendor show up with an IPO and connect it locally to site A ( on the same subnet with SCN ) to see if its the ipo.
Same deal with site B after that.

I'm guessing its your network. This always seems to be the case 90% of the time.

It's only dialtone!!!
 
I have a SCN connection among three sites. They're using VPN and sonicwall is there firewall in all of their sites. After I established the SCN, I can't make calls to others sites. "Call rejected" and "Incompatible" is what I see on the IP phones. I said to the IT guy that I just did the right implementation. Found out my calls are blocking by their sonicwalls. What the IT guy was he disable the SIP and H.323 options on all sonicwalls and reboot it all and it worked. Hope this helps.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top