Getting 483 Too Many Hops Error

Discussion:

Brian Buckles

2012-10-19 17:31:54 UTC

________________________________

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.

Tony Graziano

2012-10-19 18:05:54 UTC

Permalink

ingates are pretty resilient. the pcap is not attached. the cert if
re-issues would have nothing to do with it.

its more likely a problem with the dial plan within the ingate as it
connects to broadvox. but as there is no pcap or details on this (some
ITSP's use different dialplans for LD versus told free calls) but
there is really not much information to go on.

Post by Brian Buckles
________________________________
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
List Archive: http://list.sipfoundry.org/archive/sipx-users/

--
LAN/Telephony/Security and Control Systems Helpdesk:
Telephone: 434.984.8426
sip: ***@voice.myitdepartment.net

Helpdesk Customers: http://myhelp.myitdepartment.net
Blog: http://blog.myitdepartment.net

Matt White

2012-10-19 18:18:23 UTC

Permalink

Attachments typically don't make ti to the list. Post them to a webserver and provide a url.

483 Too many Hops is generally because the call is getting referred/re-invited too many times.

The ITSP will typically send the call with predefined number of "hops" set in the SIP header. We often find that this changes even within a single ITSP depending on where the call originates. Most ITSP set this around 10 hops.

its not hard for this to decrement down to 0. Call hits the ingate (1)...Call Goes to an alias on an AA (2), call is sent from the alias to the AA (3), AA transfers to a hunt group (4)....etc. A few hops are used internally to sipx as well. Eventually it bounces around too many times.

So for starters see if you can simplify your call routing.

Its also good to fully qualify call forwarding routes as it removes a hop. For example.

Lets say you have extension 201 as a dumy user and it sends calls to hunt group 202.
When you setup the call forwarding enter it as ***@sipx.domain

If you just put 202 in their...it will take 2 hops. One when it sends 202 to the proxy, and a second when the proxy changes 202 to ***@sipx.domain.
You can see it can eat up hops real quick.

Same goes for alias. If you can route calls to the actual user extension it will take one less hop than an alias to the same user.

If all else fails, see if the itsp can up the hops for you.

-m
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.

Tony Graziano

2012-10-19 18:30:33 UTC

Permalink

Except with an ingate we can probably preserve the hop count inside
and make it a non issue (I think).

Post by Matt White
Attachments typically don't make ti to the list. Post them to a webserver
and provide a url.
483 Too many Hops is generally because the call is getting
referred/re-invited too many times.
The ITSP will typically send the call with predefined number of "hops" set
in the SIP header. We often find that this changes even within a single
ITSP depending on where the call originates. Most ITSP set this around 10
hops.
its not hard for this to decrement down to 0. Call hits the ingate
(1)...Call Goes to an alias on an AA (2), call is sent from the alias to the
AA (3), AA transfers to a hunt group (4)....etc. A few hops are used
internally to sipx as well. Eventually it bounces around too many times.
So for starters see if you can simplify your call routing.
Its also good to fully qualify call forwarding routes as it removes a hop.
For example.
Lets say you have extension 201 as a dumy user and it sends calls to hunt group 202.
If you just put 202 in their...it will take 2 hops. One when it sends 202
You can see it can eat up hops real quick.
Same goes for alias. If you can route calls to the actual user extension it
will take one less hop than an alias to the same user.
If all else fails, see if the itsp can up the hops for you.
-m
________________________________
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
List Archive: http://list.sipfoundry.org/archive/sipx-users/

Matt White

2012-10-19 18:38:56 UTC

Permalink

You might be able to get the ingate to increase the Max-Forwards in newer firmware.

Most of the ingates I have deployed are running firmware at least a year or so old, and i had a ticket open with ingate to add this feature but at the time it wasn't there.

Regardless of what the ingate does, you still need good routing. Even if the ingate can hide the low max-forwards and send sipX a new invite with higher max-forwards, sipx will still keep track of the hops as it goes through the system and if it hits zero, it will drop the call.

-M
Except with an ingate we can probably preserve the hop count inside
and make it a non issue (I think).

Brian Buckles

2012-10-22 14:18:00 UTC

Permalink

Thanks for all the replies from everyone. I'll upload the captures to a website and re-send. I mentioned the Max Forwards setting to Ingate, but they said the issue was on the phone system and offered no other changes to be made. I'll read through all the replies to see what else we can do from our end, then send the captures to the SipXecs mailing list.

________________________________
From: Matt White <***@thesummit-grp.com>
To: sipx-***@list.sipfoundry.org; ***@myitdepartment.net
Sent: Friday, October 19, 2012 2:38 PM
Subject: Re: [sipx-users] Getting 483 Too Many Hops Error

You might be able to get the ingate to increase the Max-Forwards in newer firmware.

Most of the ingates I have deployed are running firmware at least a year or so old, and i had a ticket open with ingate to add this feature but at the time it wasn't there.

Regardless of what the ingate does, you still need good routing. Even if the ingate can hide the low max-forwards and send sipX a new invite with higher max-forwards, sipx will still keep track of the hops as it goes through the system and if it hits zero, it will drop the call.

-M
Except with an ingate we can probably preserve the hop count inside
and make it a non issue (I think).

Brian Buckles

2012-10-22 17:18:18 UTC

Permalink

All,
Please see the link below for the captures from the Ingate and BroadVox. The Ingate capture is called "Configured by Ingate Startup Tool..." and can be viewed from a web browser. You can scroll toward the bottom to see the capture and search for "483 too many hops if needed". The BroadVox capture is labeled "BroadVox_Capture_726910-3.pcap" and is just a standard pcap file. Once you follow link just click on download for each file then click "Click here to start download from sendspace" at the bottom to save to your PC. As an FYI I spoke to Ingate and we can upgrade the Ingate a new version that will allow the preservation of hops. I'm going to hold off on this for now to prevent downtime of the phone system until necessary and see if BroadVox can increase the hops. Thanks for the help and please let me know if the captures offer any further help and suggestions you may have.

http://www.sendspace.com/filegroup/6kkw1N%2BO9fAUeWPKwPXWTg

________________________________
From: Tony Graziano <***@myitdepartment.net>
To: Discussion list for users of sipXecs software <sipx-***@list.sipfoundry.org>
Cc: ***@yahoo.com
Sent: Friday, October 19, 2012 2:30 PM
Subject: Re: [sipx-users] Getting 483 Too Many Hops Error

Except with an ingate we can probably preserve the hop count inside
and make it a non issue (I think).

Attachments typically don't make ti to the list. Post them to a webserver
and provide a url.
483 Too many Hops is generally because the call is getting
referred/re-invited too many times.
The ITSP will typically send the call with predefined number of "hops" set
in the SIP header. We often find that this changes even within a single
ITSP depending on where the call originates. Most ITSP set this around 10
hops.
its not hard for this to decrement down to 0. Call hits the ingate
(1)...Call Goes to an alias on an AA (2), call is sent from the alias to the
AA (3), AA transfers to a hunt group (4)....etc. A few hops are used
internally to sipx as well. Eventually it bounces around too many times.
So for starters see if you can simplify your call routing.
Its also good to fully qualify call forwarding routes as it removes a hop.
For example.
Lets say you have extension 201 as a dumy user and it sends calls to hunt group 202.
If you just put 202 in their...it will take 2 hops. One when it sends 202
You can see it can eat up hops real quick.
Same goes for alias. If you can route calls to the actual user extension it
will take one less hop than an alias to the same user.
If all else fails, see if the itsp can up the hops for you.
-m
________________________________
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
List Archive: http://list.sipfoundry.org/archive/sipx-users/

Matt White

2012-10-22 18:37:14 UTC

Permalink

A sipx-trace will be far more beneficial. What you have is only gonna show whats happening at the gateway...its not gonna show us anything about how sipx is dealing with it internally.

http://www.sipfoundry.org/web/mpicher/~/426137/blogs/-/asset_publisher/xfZRF9U0rLa7/blog/id/78163

-M
All,
Please see the link below for the captures from the Ingate and BroadVox. The Ingate capture is called "Configured by Ingate Startup Tool..." and can be viewed from a web browser. You can scroll toward the bottom to see the capture and search for "483 too many hops if needed". The BroadVox capture is labeled "BroadVox_Capture_726910-3.pcap" and is just a standard pcap file. Once you follow link just click on download for each file then click "Click here to start download from sendspace" at the bottom to save to your PC. As an FYI I spoke to Ingate and we can upgrade the Ingate a new version that will allow the preservation of hops. I'm going to hold off on this for now to prevent downtime of the phone system until necessary and see if BroadVox can increase the hops. Thanks for the help and please let me know if the captures offer any further help and suggestions you may have.

http://www.sendspace.com/filegroup/6kkw1N%2BO9fAUeWPKwPXWTg

From: Tony Graziano <***@myitdepartment.net>
To: Discussion list for users of sipXecs software <sipx-***@list.sipfoundry.org>
Cc: ***@yahoo.com
Sent: Friday, October 19, 2012 2:30 PM
Subject: Re: [sipx-users] Getting 483 Too Many Hops Error

Except with an ingate we can probably preserve the hop count inside
and make it a non issue (I think).

Brian Buckles

2012-10-22 19:12:14 UTC

Permalink

Thanks Mike,
I'll get a capture together from the SipXecs and post it as well.

________________________________
From: Matt White <***@thesummit-grp.com>
To: sipx-***@list.sipfoundry.org; ***@yahoo.com
Sent: Monday, October 22, 2012 2:37 PM
Subject: Re: [sipx-users] Getting 483 Too Many Hops Error

A sipx-trace will be far more beneficial. What you have is only gonna show whats happening at the gateway...its not gonna show us anything about how sipx is dealing with it internally.

http://www.sipfoundry.org/web/mpicher/~/426137/blogs/-/asset_publisher/xfZRF9U0rLa7/blog/id/78163

-M
All,
Please see the link below for the captures from the Ingate and BroadVox. The Ingate capture is called "Configured by Ingate Startup Tool..." and can be viewed from a web browser. You can scroll toward the bottom to see the capture and search for "483 too many hops if needed". The BroadVox capture is labeled "BroadVox_Capture_726910-3.pcap" and is just a standard pcap file. Once you follow link just click on download for each file then click "Click here to start download from sendspace" at the bottom to save to your PC. As an FYI I spoke to Ingate and we can upgrade the Ingate a new version that will allow the preservation of hops. I'm going to hold off on this for now to prevent downtime of the phone system until necessary and see if BroadVox can increase the hops. Thanks for the help and please let me know if the captures offer any further help and suggestions you may have.

http://www.sendspace.com/filegroup/6kkw1N%2BO9fAUeWPKwPXWTg

________________________________
From: Tony Graziano <***@myitdepartment.net>
To: Discussion list for users of sipXecs software <sipx-***@list.sipfoundry.org>
Cc: ***@yahoo.com
Sent: Friday, October 19, 2012 2:30 PM
Subject: Re: [sipx-users] Getting 483 Too Many Hops Error

Except with an ingate we can probably preserve the hop count inside
and make it a non issue (I think).

Attachments typically don't make ti to the list. Post them to a webserver
and provide a url.
483 Too many Hops is generally because the call is getting
referred/re-invited too many times.
The ITSP will typically send the call with predefined number of "hops" set
in the SIP header. We often find that this changes even within a single
ITSP depending on where the call originates. Most ITSP set this around 10
hops.
its not hard for this to decrement down to 0. Call hits the ingate
(1)...Call Goes to an alias on an AA (2), call is sent from the alias to the
AA (3), AA transfers to a hunt group (4)....etc. A few hops are used
internally to sipx as well. Eventually it bounces around too many times.
So for starters see if you can simplify your call routing.
Its also good to fully qualify call forwarding routes as it removes a hop.
For example.
Lets say you have extension 201 as a dumy user and it sends calls to hunt group 202.
If you just put 202 in their...it will take 2 hops. One when it sends 202
You can see it can eat up hops real quick.
Same goes for alias. If you can route calls to the actual user extension it
will take one less hop than an alias to the same user.
If all else fails, see if the itsp can up the hops for you.
-m
________________________________
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
List Archive: http://list.sipfoundry.org/archive/sipx-users/

Brian Buckles

2012-10-22 21:34:14 UTC

Permalink

Mike I'll send you a copy of a trace once I get the complete trace. In the mean time I have a quick question. The link for SipViewer that was in the url you sent is broken. I've searched and the links I've found point to the same broken url. Do you happen to know where I can get a working copy of the SipViewer.

Thanks

________________________________
From: Brian Buckles <***@yahoo.com>
To: Matt White <***@thesummit-grp.com>; "sipx-***@list.sipfoundry.org" <sipx-***@list.sipfoundry.org>
Sent: Monday, October 22, 2012 3:12 PM
Subject: Re: [sipx-users] Getting 483 Too Many Hops Error

Thanks Mike,
I'll get a capture together from the SipXecs and post it as well.

________________________________
From: Matt White <***@thesummit-grp.com>
To: sipx-***@list.sipfoundry.org; ***@yahoo.com
Sent: Monday, October 22, 2012 2:37 PM
Subject: Re: [sipx-users] Getting 483 Too Many Hops Error

A sipx-trace will be far more beneficial. What you have is only gonna show whats happening at the gateway...its not gonna show us anything about how sipx is dealing with it internally.

http://www.sipfoundry.org/web/mpicher/~/426137/blogs/-/asset_publisher/xfZRF9U0rLa7/blog/id/78163

-M
All,
Please see the link below for the captures from the Ingate and BroadVox. The Ingate capture is called "Configured by Ingate Startup Tool..." and can be viewed from a web browser. You can scroll toward the bottom to see the capture and search for "483 too many hops if needed". The BroadVox capture is labeled "BroadVox_Capture_726910-3.pcap" and is just a standard pcap file. Once you follow link just click on download for each file then click "Click here to start download from sendspace" at the bottom to save to your PC. As an FYI I spoke to Ingate and we can upgrade the Ingate a new version that will allow the preservation of hops. I'm going to hold off on this for now to prevent downtime of the phone system until necessary and see if BroadVox can increase the hops. Thanks for the help and please let me know if the captures offer any further help and suggestions you may have.

http://www.sendspace.com/filegroup/6kkw1N%2BO9fAUeWPKwPXWTg

________________________________
From: Tony Graziano <***@myitdepartment.net>
To: Discussion list for users of sipXecs software <sipx-***@list.sipfoundry.org>
Cc: ***@yahoo.com
Sent: Friday, October 19, 2012 2:30 PM
Subject: Re: [sipx-users] Getting 483 Too Many Hops Error

Except with an ingate we can probably preserve the hop count inside
and make it a non issue (I think).

On Fri, Oct 19, 2012 at 2:18 PM, Matt White <***@thesummit-grp.com> wrote:
Attachments typically don't make ti to the list. Post them to a webserver

Post by Matt White
and provide a url.
483 Too many Hops is generally because the call is getting
referred/re-invited too many times.
The ITSP will typically send the call with predefined number of "hops" set
in the SIP header. We often find that this changes even within a single
ITSP depending on where the call originates. Most ITSP set this around 10
hops.
its not hard for this to decrement down to 0. Call hits the ingate
(1)...Call Goes to an alias on an AA (2), call is sent from the alias to the
AA (3), AA transfers to a hunt group (4)....etc. A few hops are used
internally to sipx as well. Eventually it bounces around too many times.
So for starters see if you can simplify your call routing.
Its also good to fully qualify

call forwarding routes as it removes a hop.

Post by Matt White
For example.
Lets say you have extension 201 as a dumy user and it sends calls to hunt group 202.
If you just put 202 in their...it will take 2 hops. One when it sends 202
You can see it can eat up hops real quick.
Same goes for alias. If you can route calls to the actual user extension it
will take one less hop than an alias to the same user.
If all else fails, see if the itsp can up the hops for you.
-m

Brian

a cell phone to

Post by Matt White
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

Post by Matt White
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
List Archive: http://list.sipfoundry.org/archive/sipx-users/

Brian Buckles

2012-10-22 21:55:52 UTC

Permalink

All,
I've heard that we could get a commercial copy of SipXecs that would have phone support. Is this true and if so what would be the cost? Is the phone support 24/7? Also what all would be involved? Would we simply be able to purchase a license and not have to update the SipXecs software or alter the the configuration? I wanted to ask within this post, so we know what are options are for commercial license. Can someone please provide any info on commercial support?

________________________________
From: Brian Buckles <***@yahoo.com>
To: Brian Buckles <***@yahoo.com>; Matt White <***@thesummit-grp.com>; "sipx-***@list.sipfoundry.org" <sipx-***@list.sipfoundry.org>; Discussion list for users of sipXecs software <sipx-***@list.sipfoundry.org>
Sent: Monday, October 22, 2012 5:34 PM
Subject: Re: [sipx-users] Getting 483 Too Many Hops Error

Mike I'll send you a copy of a trace once I get the complete trace. In the mean time I have a quick question. The link for SipViewer that was in the url you sent is broken. I've searched and the links I've found point to the same broken url. Do you happen to know where I can get a working copy of the SipViewer.

Thanks

________________________________
From: Brian Buckles <***@yahoo.com>
To: Matt White <***@thesummit-grp.com>; "sipx-***@list.sipfoundry.org" <sipx-***@list.sipfoundry.org>
Sent: Monday, October 22, 2012 3:12 PM
Subject: Re: [sipx-users] Getting 483 Too Many Hops Error

Thanks Mike,
I'll get a capture together from the SipXecs and post it as well.

________________________________
From: Matt White <***@thesummit-grp.com>
To: sipx-***@list.sipfoundry.org; ***@yahoo.com
Sent: Monday, October 22, 2012 2:37 PM
Subject: Re: [sipx-users] Getting 483 Too Many Hops Error

A sipx-trace will be far more beneficial. What you have is only gonna show whats happening at the gateway...its not gonna show us anything about how sipx is dealing with it internally.

http://www.sipfoundry.org/web/mpicher/~/426137/blogs/-/asset_publisher/xfZRF9U0rLa7/blog/id/78163

-M
All,
Please see the link below for the captures from the Ingate and BroadVox. The Ingate capture is called "Configured by Ingate Startup Tool..." and can be viewed from a web browser. You can scroll toward the bottom to see the capture and search for "483 too many hops if needed". The BroadVox capture is labeled "BroadVox_Capture_726910-3.pcap" and is just a standard pcap file. Once you follow link just click on download for each file then click "Click here to start download from sendspace" at the bottom to save to your PC. As an FYI I spoke to Ingate and we can upgrade the Ingate a new version that will allow the preservation of hops. I'm going to hold off on this for now to prevent downtime of the phone system until necessary and see if BroadVox can increase the hops. Thanks for the help and please let me know if the captures offer any further help and suggestions you may have.

http://www.sendspace.com/filegroup/6kkw1N%2BO9fAUeWPKwPXWTg

________________________________
From: Tony Graziano <***@myitdepartment.net>
To: Discussion list for users of sipXecs software <sipx-***@list.sipfoundry.org>
Cc: ***@yahoo.com
Sent: Friday, October 19, 2012 2:30 PM
Subject: Re: [sipx-users] Getting 483 Too Many Hops Error

Except with an ingate we can probably preserve the hop count inside
and make it a non issue (I think).

On Fri, Oct 19, 2012 at 2:18 PM, Matt White <***@thesummit-grp.com> wrote:
Attachments typically don't make ti to the list. Post them to a webserver

call forwarding routes as it removes a hop.

Brian

a cell phone to

toward the bottom to see the capture. You can search for the

Todd Hodgen

2012-10-22 22:14:25 UTC

Permalink

eZuce provides commercial support with OpenUC, their commercial version. I
suspect one of the sales staff for eZuce will reach out to you due to this
email. There are other features you gain via OpenUC which you should have
explained as well, and add to the value of the product.

From: sipx-users-***@list.sipfoundry.org
[mailto:sipx-users-***@list.sipfoundry.org] On Behalf Of Brian Buckles
Sent: Monday, October 22, 2012 2:56 PM
To: Brian Buckles; Matt White; sipx-***@list.sipfoundry.org; Discussion
list for users of sipXecs software
Subject: Re: [sipx-users] Getting 483 Too Many Hops Error

All,

I've heard that we could get a commercial copy of SipXecs that would have
phone support. Is this true and if so what would be the cost? Is the phone
support 24/7? Also what all would be involved? Would we simply be able to
purchase a license and not have to update the SipXecs software or alter the
the configuration? I wanted to ask within this post, so we know what are
options are for commercial license. Can someone please provide any info on
commercial support?

_____

From: Brian Buckles <***@yahoo.com>
To: Brian Buckles <***@yahoo.com>; Matt White
<***@thesummit-grp.com>; "sipx-***@list.sipfoundry.org"
<sipx-***@list.sipfoundry.org>; Discussion list for users of sipXecs
software <sipx-***@list.sipfoundry.org>
Sent: Monday, October 22, 2012 5:34 PM
Subject: Re: [sipx-users] Getting 483 Too Many Hops Error

Mike I'll send you a copy of a trace once I get the complete trace. In the
mean time I have a quick question. The link for SipViewer that was in the
url you sent is broken. I've searched and the links I've found point to the
same broken url. Do you happen to know where I can get a working copy of
the SipViewer.

Thanks

_____

From: Brian Buckles <***@yahoo.com>
To: Matt White <***@thesummit-grp.com>; "sipx-***@list.sipfoundry.org"
<sipx-***@list.sipfoundry.org>
Sent: Monday, October 22, 2012 3:12 PM
Subject: Re: [sipx-users] Getting 483 Too Many Hops Error

Thanks Mike,

I'll get a capture together from the SipXecs and post it as well.

_____

From: Matt White <***@thesummit-grp.com>
To: sipx-***@list.sipfoundry.org; ***@yahoo.com
Sent: Monday, October 22, 2012 2:37 PM
Subject: Re: [sipx-users] Getting 483 Too Many Hops Error

A sipx-trace will be far more beneficial. What you have is only gonna show
whats happening at the gateway...its not gonna show us anything about how
sipx is dealing with it internally.

http://www.sipfoundry.org/web/mpicher/~/426137/blogs/-/asset_publisher/xfZRF
9U0rLa7/blog/id/78163

-M
All,

Please see the link below for the captures from the Ingate and BroadVox.
The Ingate capture is called "Configured by Ingate Startup Tool..." and can
be viewed from a web browser. You can scroll toward the bottom to see the
capture and search for "483 too many hops if needed". The BroadVox capture
is labeled "BroadVox_Capture_726910-3.pcap" and is just a standard pcap
file. Once you follow link just click on download for each file then click
"Click here to start download from sendspace" at the bottom to save to your
PC. As an FYI I spoke to Ingate and we can upgrade the Ingate a new version
that will allow the preservation of hops. I'm going to hold off on this for
now to prevent downtime of the phone system until necessary and see if
BroadVox can increase the hops. Thanks for the help and please let me know
if the captures offer any further help and suggestions you may have.

http://www.sendspace.com/filegroup/6kkw1N%2BO9fAUeWPKwPXWTg

_____

From: Tony Graziano <***@myitdepartment.net>
To: Discussion list for users of sipXecs software
<sipx-***@list.sipfoundry.org>
Cc: ***@yahoo.com
Sent: Friday, October 19, 2012 2:30 PM
Subject: Re: [sipx-users] Getting 483 Too Many Hops Error

Except with an ingate we can probably preserve the hop count inside
and make it a non issue (I think).

Can

Post by Matt White
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
List Archive: http://list.sipfoundry.org/archive/sipx-users/

--
~~~~~~~~~~~~~~~~~~
Tony Graziano, Manager
Telephone: 434.984.8430
sip: ***@voice.myitdepartment.net
Fax: 434.465.6833
~~~~~~~~~~~~~~~~~~
Linked-In Profile:
http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4
Ask about our Internet Fax services!
~~~~~~~~~~~~~~~~~~

Using or developing for sipXecs from SIPFoundry? Ask me about sipX-CoLab
2013!
--
LAN/Telephony/Security and Control Systems Helpdesk:
Telephone: 434.984.8426
sip: ***@voice.myitdepartment.net

Helpdesk Customers: http://myhelp.myitdepartment.net
<http://myhelp.myitdepartment.net/>
Blog: http://blog.myitdepartment.net <http://blog.myitdepartment.net/>
_______________________________________________
sipx-users mailing list
sipx-***@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipx-users/

_______________________________________________
sipx-users mailing list
sipx-***@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipx-users/

Tony Graziano

2012-10-22 22:35:23 UTC

Permalink

I have never EVER used the startup tool configuration with ingate. Its very
generic and probably just needs a tweak.

Post by Brian Buckles
All,
I've heard that we could get a commercial copy of SipXecs that would have
phone support. Is this true and if so what would be the cost? Is the
phone support 24/7? Also what all would be involved? Would we simply be
able to purchase a license and not have to update the SipXecs software or
alter the the configuration? I wanted to ask within this post, so we know
what are options are for commercial license. Can someone please provide
any info on commercial support?
------------------------------
*Sent:* Monday, October 22, 2012 5:34 PM
*Subject:* Re: [sipx-users] Getting 483 Too Many Hops Error
Mike I'll send you a copy of a trace once I get the complete trace. In
the mean time I have a quick question. The link for SipViewer that was in
the url you sent is broken. I've searched and the links I've found point
to the same broken url. Do you happen to know where I can get a working
copy of the SipViewer.
Thanks
------------------------------
*Sent:* Monday, October 22, 2012 3:12 PM
*Subject:* Re: [sipx-users] Getting 483 Too Many Hops Error
Thanks Mike,
I'll get a capture together from the SipXecs and post it as well.
------------------------------
*Sent:* Monday, October 22, 2012 2:37 PM
*Subject:* Re: [sipx-users] Getting 483 Too Many Hops Error
A sipx-trace will be far more beneficial. What you have is only gonna
show whats happening at the gateway...its not gonna show us anything about
how sipx is dealing with it internally.
http://www.sipfoundry.org/web/mpicher/~/426137/blogs/-/asset_publisher/xfZRF9U0rLa7/blog/id/78163
-M
All,
Please see the link below for the captures from the Ingate and BroadVox.
The Ingate capture is called "Configured by Ingate Startup Tool..." and can
be viewed from a web browser. You can scroll toward the bottom to see the
capture and search for "483 too many hops if needed". The BroadVox capture
is labeled "BroadVox_Capture_726910-3.pcap" and is just a standard pcap
file. Once you follow link just click on download for each file then click
"Click here to start download from sendspace" at the bottom to save to your
PC. As an FYI I spoke to Ingate and we can upgrade the Ingate a new
version that will allow the preservation of hops. I'm going to hold off on
this for now to prevent downtime of the phone system until necessary and
see if BroadVox can increase the hops. Thanks for the help and please let
me know if the captures offer any further help and suggestions you may have.
http://www.sendspace.com/filegroup/6kkw1N%2BO9fAUeWPKwPXWTg
------------------------------
*To:* Discussion list for users of sipXecs software <
*Sent:* Friday, October 19, 2012 2:30 PM
*Subject:* Re: [sipx-users] Getting 483 Too Many Hops Error
Except with an ingate we can probably preserve the hop count inside
and make it a non issue (I think).

Post by Matt White
Attachments typically don't make ti to the list. Post them to a

webserver

set

Post by Matt White
in the SIP header. We often find that this changes even within a single
ITSP depending on where the call originates. Most ITSP set this around

Post by Matt White
hops.
its not hard for this to decrement down to 0. Call hits the ingate
(1)...Call Goes to an alias on an AA (2), call is sent from the alias to

the

Post by Matt White
AA (3), AA transfers to a hunt group (4)....etc. A few hops are used
internally to sipx as well. Eventually it bounces around too many times.
So for starters see if you can simplify your call routing.
Its also good to fully qualify call forwarding routes as it removes a

hop.

Post by Matt White
For example.
Lets say you have extension 201 as a dumy user and it sends calls to hunt group 202.
If you just put 202 in their...it will take 2 hops. One when it sends

202
.

Post by Matt White
You can see it can eat up hops real quick.
Same goes for alias. If you can route calls to the actual user

extension it

Post by Matt White
will take one less hop than an alias to the same user.
If all else fails, see if the itsp can up the hops for you.
-m
________________________________
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

Post by Matt White
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

Post by Matt White
BroadVox. The client is unable to receive calls to most of their toll

free

Post by Matt White
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

but

Post by Matt White
there's been one or 2 land based offices that were able to successfully

call

Post by Matt White
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

Post by Matt White
the SipXecs system, is that the selt signed cert had expired and was

renewed

Post by Matt White
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

Post by Matt White
of 8004144231 was used during the gathering of the 2 attached captures.

Can

--
~~~~~~~~~~~~~~~~~~
Tony Graziano, Manager
Telephone: 434.984.8430
Fax: 434.465.6833
~~~~~~~~~~~~~~~~~~
http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4
Ask about our Internet Fax services!
~~~~~~~~~~~~~~~~~~
Using or developing for sipXecs from SIPFoundry? Ask me about sipX-CoLab 2013!
--
Telephone: 434.984.8426
Helpdesk Customers: http://myhelp.myitdepartment.net
Blog: http://blog.myitdepartment.net
_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users/
_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users/
_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users/
_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users/

Melcon Moraes

2012-10-22 23:31:32 UTC

Permalink

Here you can have it:
http://wiki.sipfoundry.org/display/sipXecs/Display+SIP+message+flow+using+Sipviewer

-
MM

Post by Todd Hodgen
Mike I'll send you a copy of a trace once I get the complete trace. In
the mean time I have a quick question. The link for SipViewer that was in
the url you sent is broken. I've searched and the links I've found point
to the same broken url. Do you happen to know where I can get a working
copy of the SipViewer.
Thanks
------------------------------
*Sent:* Monday, October 22, 2012 3:12 PM
*Subject:* Re: [sipx-users] Getting 483 Too Many Hops Error
Thanks Mike,
I'll get a capture together from the SipXecs and post it as well.
------------------------------
*Sent:* Monday, October 22, 2012 2:37 PM
*Subject:* Re: [sipx-users] Getting 483 Too Many Hops Error
A sipx-trace will be far more beneficial. What you have is only gonna
show whats happening at the gateway...its not gonna show us anything about
how sipx is dealing with it internally.
http://www.sipfoundry.org/web/mpicher/~/426137/blogs/-/asset_publisher/xfZRF9U0rLa7/blog/id/78163
-M
All,
Please see the link below for the captures from the Ingate and BroadVox.
The Ingate capture is called "Configured by Ingate Startup Tool..." and can
be viewed from a web browser. You can scroll toward the bottom to see the
capture and search for "483 too many hops if needed". The BroadVox capture
is labeled "BroadVox_Capture_726910-3.pcap" and is just a standard pcap
file. Once you follow link just click on download for each file then click
"Click here to start download from sendspace" at the bottom to save to your
PC. As an FYI I spoke to Ingate and we can upgrade the Ingate a new
version that will allow the preservation of hops. I'm going to hold off on
this for now to prevent downtime of the phone system until necessary and
see if BroadVox can increase the hops. Thanks for the help and please let
me know if the captures offer any further help and suggestions you may have.
http://www.sendspace.com/filegroup/6kkw1N%2BO9fAUeWPKwPXWTg
------------------------------
*To:* Discussion list for users of sipXecs software <
*Sent:* Friday, October 19, 2012 2:30 PM
*Subject:* Re: [sipx-users] Getting 483 Too Many Hops Error
Except with an ingate we can probably preserve the hop count inside
and make it a non issue (I think).

Post by Matt White
Attachments typically don't make ti to the list. Post them to a

webserver

set

Post by Matt White
in the SIP header. We often find that this changes even within a single
ITSP depending on where the call originates. Most ITSP set this around

Post by Matt White
hops.
its not hard for this to decrement down to 0. Call hits the ingate
(1)...Call Goes to an alias on an AA (2), call is sent from the alias to

the

hop.

Post by Matt White
For example.
Lets say you have extension 201 as a dumy user and it sends calls to hunt group 202.
If you just put 202 in their...it will take 2 hops. One when it sends

202
.

Post by Matt White
You can see it can eat up hops real quick.
Same goes for alias. If you can route calls to the actual user

extension it

trunks is

Post by Matt White
BroadVox. The client is unable to receive calls to most of their toll

free

Post by Matt White
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

but

Post by Matt White
there's been one or 2 land based offices that were able to successfully

call

Post by Matt White
the SipXecs system, is that the selt signed cert had expired and was

renewed

Post by Matt White
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

Post by Matt White
of 8004144231 was used during the gathering of the 2 attached

captures. Can

Brian Buckles

2012-10-23 14:18:00 UTC

Permalink

Matt or others interested in the SipXecs capture, please see the link below. Please follow the link below and choose "click here to start download from" SendSpace. This capture is of a call from 8595235338 to one of the problematic toll free numbers 800-414-4231. Please let me know if this provides any further info that may help to resolve this issue more quickly. Thanks in advance for any assistance.

http://www.sendspace.com/file/m2hoiu

________________________________
From: Matt White <***@thesummit-grp.com>
To: sipx-***@list.sipfoundry.org; ***@yahoo.com
Sent: Monday, October 22, 2012 2:37 PM
Subject: Re: [sipx-users] Getting 483 Too Many Hops Error

A sipx-trace will be far more beneficial. What you have is only gonna show whats happening at the gateway...its not gonna show us anything about how sipx is dealing with it internally.

http://www.sipfoundry.org/web/mpicher/~/426137/blogs/-/asset_publisher/xfZRF9U0rLa7/blog/id/78163

-M
All,
Please see the link below for the captures from the Ingate and BroadVox. The Ingate capture is called "Configured by Ingate Startup Tool..." and can be viewed from a web browser. You can scroll toward the bottom to see the capture and search for "483 too many hops if needed". The BroadVox capture is labeled "BroadVox_Capture_726910-3.pcap" and is just a standard pcap file. Once you follow link just click on download for each file then click "Click here to start download from sendspace" at the bottom to save to your PC. As an FYI I spoke to Ingate and we can upgrade the Ingate a new version that will allow the preservation of hops. I'm going to hold off on this for now to prevent downtime of the phone system until necessary and see if BroadVox can increase the hops. Thanks for the help and please let me know if the captures offer any further help and suggestions you may have.

http://www.sendspace.com/filegroup/6kkw1N%2BO9fAUeWPKwPXWTg

________________________________
From: Tony Graziano <***@myitdepartment.net>
To: Discussion list for users of sipXecs software <sipx-***@list.sipfoundry.org>
Cc: ***@yahoo.com
Sent: Friday, October 19, 2012 2:30 PM
Subject: Re: [sipx-users] Getting 483 Too Many Hops Error

Except with an ingate we can probably preserve the hop count inside
and make it a non issue (I think).

Attachments typically don't make ti to the list. Post them to a webserver
and provide a url.
483 Too many Hops is generally because the call is getting
referred/re-invited too many times.
The ITSP will typically send the call with predefined number of "hops" set
in the SIP header. We often find that this changes even within a single
ITSP depending on where the call originates. Most ITSP set this around 10
hops.
its not hard for this to decrement down to 0. Call hits the ingate
(1)...Call Goes to an alias on an AA (2), call is sent from the alias to the
AA (3), AA transfers to a hunt group (4)....etc. A few hops are used
internally to sipx as well. Eventually it bounces around too many times.
So for starters see if you can simplify your call routing.
Its also good to fully qualify call forwarding routes as it removes a hop.
For example.
Lets say you have extension 201 as a dumy user and it sends calls to hunt group 202.
If you just put 202 in their...it will take 2 hops. One when it sends 202
You can see it can eat up hops real quick.
Same goes for alias. If you can route calls to the actual user extension it
will take one less hop than an alias to the same user.
If all else fails, see if the itsp can up the hops for you.
-m
________________________________
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
List Archive: http://list.sipfoundry.org/archive/sipx-users/

Tony Graziano

2012-10-23 14:22:46 UTC

Permalink

Please confirm the dial plan rule for toll free is enabled (or not)
and what gateway it points to (as compared to your long distance rule,
for example).

Post by Brian Buckles
Matt or others interested in the SipXecs capture, please see the link below.
Please follow the link below and choose "click here to start download from"
SendSpace. This capture is of a call from 8595235338 to one of the
problematic toll free numbers 800-414-4231. Please let me know if this
provides any further info that may help to resolve this issue more quickly.
Thanks in advance for any assistance.
http://www.sendspace.com/file/m2hoiu
________________________________
Sent: Monday, October 22, 2012 2:37 PM
Subject: Re: [sipx-users] Getting 483 Too Many Hops Error
A sipx-trace will be far more beneficial. What you have is only gonna show
whats happening at the gateway...its not gonna show us anything about how
sipx is dealing with it internally.
http://www.sipfoundry.org/web/mpicher/~/426137/blogs/-/asset_publisher/xfZRF9U0rLa7/blog/id/78163
-M
All,
Please see the link below for the captures from the Ingate and BroadVox.
The Ingate capture is called "Configured by Ingate Startup Tool..." and can
be viewed from a web browser. You can scroll toward the bottom to see the
capture and search for "483 too many hops if needed". The BroadVox capture
is labeled "BroadVox_Capture_726910-3.pcap" and is just a standard pcap
file. Once you follow link just click on download for each file then click
"Click here to start download from sendspace" at the bottom to save to your
PC. As an FYI I spoke to Ingate and we can upgrade the Ingate a new version
that will allow the preservation of hops. I'm going to hold off on this for
now to prevent downtime of the phone system until necessary and see if
BroadVox can increase the hops. Thanks for the help and please let me know
if the captures offer any further help and suggestions you may have.
http://www.sendspace.com/filegroup/6kkw1N%2BO9fAUeWPKwPXWTg
________________________________
To: Discussion list for users of sipXecs software
Sent: Friday, October 19, 2012 2:30 PM
Subject: Re: [sipx-users] Getting 483 Too Many Hops Error
Except with an ingate we can probably preserve the hop count inside
and make it a non issue (I think).

Post by Matt White
Attachments typically don't make ti to the list. Post them to a webserver
and provide a url.
483 Too many Hops is generally because the call is getting
referred/re-invited too many times.
The ITSP will typically send the call with predefined number of "hops" set
in the SIP header. We often find that this changes even within a single
ITSP depending on where the call originates. Most ITSP set this around 10
hops.
its not hard for this to decrement down to 0. Call hits the ingate
(1)...Call Goes to an alias on an AA (2), call is sent from the alias to the
AA (3), AA transfers to a hunt group (4)....etc. A few hops are used
internally to sipx as well. Eventually it bounces around too many times.
So for starters see if you can simplify your call routing.
Its also good to fully qualify call forwarding routes as it removes a hop.
For example.
Lets say you have extension 201 as a dumy user and it sends calls to hunt group 202.
If you just put 202 in their...it will take 2 hops. One when it sends 202
You can see it can eat up hops real quick.
Same goes for alias. If you can route calls to the actual user extension it
will take one less hop than an alias to the same user.
If all else fails, see if the itsp can up the hops for you.
-m
________________________________
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
List Archive: http://list.sipfoundry.org/archive/sipx-users/

Tony Graziano

2012-10-23 14:23:31 UTC

Permalink

Also ensure your user or user group initiating the call has the
correct permissions.

On Tue, Oct 23, 2012 at 10:22 AM, Tony Graziano

Post by Tony Graziano
Please confirm the dial plan rule for toll free is enabled (or not)
and what gateway it points to (as compared to your long distance rule,
for example).

Post by Matt White
Attachments typically don't make ti to the list. Post them to a webserver
and provide a url.
483 Too many Hops is generally because the call is getting
referred/re-invited too many times.
The ITSP will typically send the call with predefined number of "hops" set
in the SIP header. We often find that this changes even within a single
ITSP depending on where the call originates. Most ITSP set this around 10
hops.
its not hard for this to decrement down to 0. Call hits the ingate
(1)...Call Goes to an alias on an AA (2), call is sent from the alias to the
AA (3), AA transfers to a hunt group (4)....etc. A few hops are used
internally to sipx as well. Eventually it bounces around too many times.
So for starters see if you can simplify your call routing.
Its also good to fully qualify call forwarding routes as it removes a hop.
For example.
Lets say you have extension 201 as a dumy user and it sends calls to hunt group 202.
If you just put 202 in their...it will take 2 hops. One when it sends 202
You can see it can eat up hops real quick.
Same goes for alias. If you can route calls to the actual user extension it
will take one less hop than an alias to the same user.
If all else fails, see if the itsp can up the hops for you.
-m
________________________________
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
List Archive: http://list.sipfoundry.org/archive/sipx-users/

Brian Buckles

2012-10-23 15:58:56 UTC

Permalink

Tony,
Both the Toll Free Dial Plan and the Long Distance Dial plan have the same gateway IP.

________________________________
From: Tony Graziano <***@myitdepartment.net>
To: Brian Buckles <***@yahoo.com>; Discussion list for users of sipXecs software <sipx-***@list.sipfoundry.org>
Cc: Matt White <***@thesummit-grp.com>
Sent: Tuesday, October 23, 2012 10:22 AM
Subject: Re: [sipx-users] Getting 483 Too Many Hops Error

Please confirm the dial plan rule for toll free is enabled (or not)
and what gateway it points to (as compared to your long distance rule,
for example).

Attachments typically don't make ti to the list. Post them to a webserver
and provide a url.
483 Too many Hops is generally because the call is getting
referred/re-invited too many times.
The ITSP will typically send the call with predefined number of "hops" set
in the SIP header. We often find that this changes even within a single
ITSP depending on where the call originates. Most ITSP set this around 10
hops.
its not hard for this to decrement down to 0. Call hits the ingate
(1)...Call Goes to an alias on an AA (2), call is sent from the alias to the
AA (3), AA transfers to a hunt group (4)....etc. A few hops are used
internally to sipx as well. Eventually it bounces around too many times.
So for starters see if you can simplify your call routing.
Its also good to fully qualify call forwarding routes as it removes a hop.
For example.
Lets say you have extension 201 as a dumy user and it sends calls to hunt group 202.
If you just put 202 in their...it will take 2 hops. One when it sends 202
You can see it can eat up hops real quick.
Same goes for alias. If you can route calls to the actual user extension it
will take one less hop than an alias to the same user.
If all else fails, see if the itsp can up the hops for you.
-m
________________________________
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
List Archive: http://list.sipfoundry.org/archive/sipx-users/

Tony Graziano

2012-10-23 16:10:04 UTC

Permalink

6 hops is just too low. If it "started" suddenly, it's a change at the
provider's end (meaning you didn't add a lot of phones to your hunt group,
etc. If it were me, and it's not, I'd make BVOX fix it. It does not adhere
to RFC3261.

http://tools.ietf.org/html/rfc3261#page-38

8.1.1.6 <http://tools.ietf.org/html/rfc3261#section-8.1.1.6> Max-Forwards

The Max-Forwards header field serves to limit the number of hops a
request can transit on the way to its destination. It consists of an
integer that is decremented by one at each hop. If the Max-Forwards
value reaches 0 before the request reaches its destination, it will
be rejected with a 483(Too Many Hops) error response.

A UAC MUST insert a Max-Forwards header field into each request it
originates with a value that SHOULD be 70. This number was chosen to
be sufficiently large to guarantee that a request would not be
dropped in any SIP network when there were no loops, but not so large
as to consume proxy resources when a loop does occur. Lower values
should be used with caution and only in networks where topologies are
known by the UA.

Another alternate way to do this is with an AA. Let the AA answer the call,
and reduce all the options to the minumum time and have it transfer to the
hunt group on failure OR make the user press a key to get to the hunt
group. Once the call is answered, the hops issue is removed, and the AA
will answer the call.

Alternately you could see if the ingate will artificially fix this, but the
cause s probably a new low cost route for toll free services added and/or
changed AT broadvox. How either party (Ingate support or Broadvox) could
say it is the cause of the sip proxy or sipx without admitting to this is
comical.

Post by Brian Buckles
Tony,
Both the Toll Free Dial Plan and the Long Distance Dial plan have the same gateway IP.
------------------------------
*Sent:* Tuesday, October 23, 2012 10:22 AM
*Subject:* Re: [sipx-users] Getting 483 Too Many Hops Error
Please confirm the dial plan rule for toll free is enabled (or not)
and what gateway it points to (as compared to your long distance rule,
for example).

Post by Brian Buckles
Matt or others interested in the SipXecs capture, please see the link

below.

Post by Brian Buckles
Please follow the link below and choose "click here to start download

from"

Post by Brian Buckles
SendSpace. This capture is of a call from 8595235338 to one of the
problematic toll free numbers 800-414-4231. Please let me know if this
provides any further info that may help to resolve this issue more

quickly.

Post by Brian Buckles
Thanks in advance for any assistance.
http://www.sendspace.com/file/m2hoiu
________________________________
Sent: Monday, October 22, 2012 2:37 PM
Subject: Re: [sipx-users] Getting 483 Too Many Hops Error
A sipx-trace will be far more beneficial. What you have is only gonna

show

Post by Brian Buckles
whats happening at the gateway...its not gonna show us anything about how
sipx is dealing with it internally.

http://www.sipfoundry.org/web/mpicher/~/426137/blogs/-/asset_publisher/xfZRF9U0rLa7/blog/id/78163

Post by Brian Buckles
-M
All,
Please see the link below for the captures from the Ingate and BroadVox.
The Ingate capture is called "Configured by Ingate Startup Tool..." and

can

Post by Brian Buckles
be viewed from a web browser. You can scroll toward the bottom to see

the

Post by Brian Buckles
capture and search for "483 too many hops if needed". The BroadVox

capture

Post by Brian Buckles
is labeled "BroadVox_Capture_726910-3.pcap" and is just a standard pcap
file. Once you follow link just click on download for each file then

click

Post by Brian Buckles
"Click here to start download from sendspace" at the bottom to save to

your

Post by Brian Buckles
PC. As an FYI I spoke to Ingate and we can upgrade the Ingate a new

version

Post by Brian Buckles
that will allow the preservation of hops. I'm going to hold off on this

for

Post by Brian Buckles
now to prevent downtime of the phone system until necessary and see if
BroadVox can increase the hops. Thanks for the help and please let me

know

Post by Brian Buckles
if the captures offer any further help and suggestions you may have.
http://www.sendspace.com/filegroup/6kkw1N%2BO9fAUeWPKwPXWTg
________________________________
To: Discussion list for users of sipXecs software
Sent: Friday, October 19, 2012 2:30 PM
Subject: Re: [sipx-users] Getting 483 Too Many Hops Error
Except with an ingate we can probably preserve the hop count inside
and make it a non issue (I think).

Post by Matt White
Attachments typically don't make ti to the list. Post them to a

webserver