Welcome, Guest. Please login or register.

Author Topic: SPNET --> No User Response  (Read 7388 times)

0 Members and 2 Guests are viewing this topic.

Offline Ironhedz

  • Technician
  • Location: Jacksonville, FL
  • Posts: 114
SPNET --> No User Response
« on: September 12, 2011, 06:22:57 PM »
Ok all.  I have a 7100 networked with a 7200.  On a private network. The 7100 is 10.0.1.x network and the 7200 is 10.0.0.x network. Have all Ip's entered in correctly in 8xx. Every now and then I get a no user response error. I cannot figure out what is causing this. It is very intermittant. According to Samsung, the no user response means that the call cannot get to the other switch on the MPLS. Meaning that there is an issue with the private point to point network, but according to the telco providing the point to point, they never see the call hit the router to be processed. So I am kinda stuck in the middle here. Samsung is blaming the telco and telco is blaming the Samsung. So am I kinda stuck and dont know where to go from here.

Thanks in advance for everyone's help......

Offline Marc Haycook

  • Administrator
  • Location: Jefferson City, MO
  • Posts: 2680
Re: SPNET --> No User Response
« Reply #1 on: September 12, 2011, 07:12:22 PM »
Have you done a Wireshark capture? I would tend to agree with Samsung, the two systems do not see each other. Is the telco handling the routers on the point-to-point? How do they know the call wasn't hitting the router?
Marc Haycook
CCNA
Sport-Touring

Offline Ironhedz

  • Technician
  • Location: Jacksonville, FL
  • Posts: 114
Re: SPNET --> No User Response
« Reply #2 on: September 12, 2011, 07:20:43 PM »
Thanks for the reply marc.  Yes, telco handles the routers between the point to point.  I called telco and they were watching the routers when i was getting the no user response. They never saw the call hit the router. I can do a wireshark on it, but man is it hard trying to decode what it all means. I call across 9 out of 10 times it works. Then the 10th one wont go through. Even on the same spnet trunks that worked the previous 9 times.

Offline Ironhedz

  • Technician
  • Location: Jacksonville, FL
  • Posts: 114
Re: SPNET --> No User Response
« Reply #3 on: September 14, 2011, 07:09:14 AM »
I was able to get a wireshark capture.  But trying to decipher it takes some work.  I captured two failed calls and one good call. Any idea what I am looking for?  Right now I have samsung saying its the routers and telco saying its the PBX. Only other option is to take a 7100 out there, network it with the one on site and make some calls.

Offline Ironhedz

  • Technician
  • Location: Jacksonville, FL
  • Posts: 114
Re: SPNET --> No User Response
« Reply #4 on: September 16, 2011, 01:38:17 PM »
We got it fixed.  Problem ended up being the telco sonicwall's. They were natting the traffic between the two internal routers.

Offline matherton

  • Moderator
  • Location: Canada : British Columbia : Surrey
  • Posts: 513
    • Houle
Re: SPNET --> No User Response
« Reply #5 on: September 25, 2011, 12:01:53 PM »
thats awesome, i love hearing the telco finally realizing its their setup.
Marty Atherton

Was a Samsung 'expert' * Panasonic * Grandstream * Ascom TeleCareIP Nurse Call
Tunnel vision to retirement

Offline bmreen

  • Pro Shop Member
  • Location: Jacksonville,FL
  • Posts: 167
    • University of North Florida
Re: SPNET --> No User Response
« Reply #6 on: October 18, 2012, 07:50:33 PM »
Ironhedz, I am having the identical problem as you were now at one of my sites now. Do you have any specific settings or options on the Sonic Walls I should tell the CG to look at or change?
Bobby Mreen
Telecommunications Technician
www.unf.edu

Offline Ironhedz

  • Technician
  • Location: Jacksonville, FL
  • Posts: 114
Re: SPNET --> No User Response
« Reply #7 on: October 18, 2012, 11:12:06 PM »
Bobby,

I was never told what the specific problem was. It was NAT on of the MPLS routers, it usually takes a tier 3 or 4 guy to figure it out.  I wish I had more info for you, but I was never told what the exact problem was.  Sorry

Take a system (if you can) and network it with one, that will tell you real quick where the problem is..