________________________________
Sorry if this gets re-posted a second time. I haven't gotten any confirmation
from the admins that this was or wasn't accepted, and this is something we need
to resolve quickly. Please see my previous email below for details.
Attention SipXecs support community,
We have a client that is running SipXecs 4.4.0. The Session Boarder Controller
is an InGate Siparator and the SIP provider for the SIP trunks is BroadVox.
The client is unable to receive calls to most of their toll free numbers
properly. Our client noticed that prior to calling us, that it seemed they
could get a call to successfully go through from a cell phone to the toll free
numbers, but not from land lines. After further testing it appears the some
calls go through for most cell phone carriers and not others. It appears most
land line calls to the toll free numbers fail, but there's been one or 2 land
based offices that were able to successfully call the toll free numbers. All
calls to the local numbers have went through without incident as to the best of
our knowledge. We talked to the SIP provider and vendor for the SBC. They
found that the SipXecs system is giving a "483 Too Many Hops" error. I've
attached a capture (see the
726910-3.pcap file ) from the SIP provider as well as capture (See the
"Configured by Ingate...." file) from the SBC vendor that was ran on the SBC.
You'll can view the capture from the SBC using a web browser, then scroll down
toward the bottom to see the capture. You can search for the error code given
above. The only changes we are aware of that happened on the SipXecs system,
is that the selt signed cert had expired and was renewed about a month ago.
The issue with the "483 Too Many Hops" has only been noticed by the client
within the last 1.5 to 2 weeks. The toll free number of 8004144231 was used
during the gathering of the 2 attached captures. Can someone please take a
look at the attached capture files ASAP and let us know of any suggestions you
have to resolve this issue? This issue is having a major impact the client's
normal business operations.
_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users/