Our customer has 2 sites with SCN setup using point to point through T1s with IP Trunking. Both sites have IP500 V2 with R7.0.12 and required licenses added. Everything seems to be working fine except for errors I see on SSA: "No response to IP trunk call request IP Trunk Line Number: 41 Remote end IP address: xx.xx.xx.xx". It seems to happen every 40 to 60 minutes. This only happens at the local site where the VMPro server resides. The remote site is fine, no errors. Also at the remote site if system is idle for a period of time and a user initiates a call from the remote site, they receive a wave off and is disconnected, And when they try again, the call goes through. Any ideas? Thanks in advance.
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 John Tel on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Point to Point VPN
- Thread starter ceejcast
- Start date
I am having the exact same issues with my SCN. Same set-up, 2 sites with SCN on a point to point T1. My main site is seeing the exact same error in the SSA "No response to IP trunk call request". The other error im getting is the remote site - several call quality of service errors with round-trip delay times being very high... Please help!
MandyDroid
Programmer
I have setup several VPN SCN with IPO V1 and V2. I am osrry to say but it does sound like a poor VPN connection. The only time I have seen "No response to IP trunk call request" is when the VPN goes down. Check for a keep alive option or try to run a script to ping each site every minute and see if the errors occur.
Avaya, Panasonic, Polycom, APC, MCP, A+
##################################
"When I was a child, I spoke like a child, I thought like a child, I reasoned like a child.
When I became a man, I gave up childish ways.
Avaya, Panasonic, Polycom, APC, MCP, A+
##################################
"When I was a child, I spoke like a child, I thought like a child, I reasoned like a child.
When I became a man, I gave up childish ways.
I agree with Mandy. Try setting up some simple repetitive pings between the IP Office systems to see if you get any drops within this time frame. If you ping from one side to the other for over an hour and don't get any drops, then the configuration of the VPN would need to be inspected. It might be possible that they are configured to drop in the absence of any traffic? Not likely they are configured with idle time-outs but defintely sounds like it is the VPN itself that is causing the issues.
- Thread starter
- #6
Thanks all, the customer has a vendor who administers the firewall where the VPN is configured which are Cisco ASA 5505's at both sites. Therefore, I have no way of checking their settings and I am not familiar with that firewall. The vendor is very accomodating but I have no way of knowing if the settings are correct except for his word. He tells me that both sites are set to stay up 24/7 and that the settings are good on his side. But yet I still see the same alarms. Could this be equipment or connection failure on one or both IPOs? Or can anyone suggest possible settings on the firewall that could resolve this? Thanks again.
- Status
Similar threads
- Locked
- Question
- Locked
- Question