This downstream blocking will happen without our knowledge. Redials to the same number should be spaced at least one minute apart.Įxcessive redialing may result in automatic blocks for a variety of reasons, including downstream carriers that specifically react to dialer traffic patterns. Please only retry calls on another IP if the first IP you attempted is down (as determined by OPTIONS Polling or INVITE timeout). Please avoid unnecessary signaling and treat all rejection codes as being final: do not retry such calls to another Voxox IP address, or from another one of yours, if the first Voxox IP rejected the call. For example, do not immediately retry on an alternate IP if you receive from us '503 Service Unavailable', '486 Busy Here' or '404 Not Found'. In case you cannot use OPTIONS Polling to determine the state of our IPs, please avoid trying calls twice based on cause-code. This will save you PDD and unnecessary signaling during a Voxox incident. You may detect such an event by pinging each IP with “SIP OPTIONS Polling”, rather than waiting for one or more INVITE to time out. In an unlikely case that one of these IPs is down, all calls will be processed by the IPs that remains in-service. Under normal conditions, we expect you to load-balance your calls between two or more of our IP addresses. You should treat a rejection from one of our servers as final, and not immediately resend that call to any other Voxox IP nor immediately resend from another one of your IP. We have observed measurable improvement in customer traffic once moved away from this server. For the time being, please retest using two or more of the other servers below (as described in the next point), and either remove 69.26.183.204 from routing or give it the lowest priority. This is a vitally important change to your configuration - Voxox is currently investigating an issue with our server at 69.26.183.204. If two legitimately unique calls are being placed to the same destination, they should have unique 'Call-ID' values your duplicate INVITE are identical.

This behavior might be the consequence of an improperly configured 'SIP Retry Timer' or similar feature, or some network element might be literally sending a duplicate packet. RFC permits you to resend an INVITE that does not receive a timely reply (100 Trying), but this is not the same as immediately sending two INVITE 0.1 second apart. This issue is yet to be resolved and I am told that we double dial numbers immediately or call the same number twice at the same time, etc.Ĭode: Select all You should never send duplicate INVITE. Ok, I've used this company for over two years and honestly have the same problem ALL THE TIME.

Voxox call rates