[lonnie2]

Using ICH with a SPA-1001 is working fine and dandy.

I was looking at my firewall logs, and whenever I call a local (402 - Nebraska) number, the UDP session for the call is always to IP address: 194.152.113.13.

It appears that this address is in Austria (as in Europe)! My ISP is Cox.net.

Can some explain why this is, or may there be a routing issue with DeltaThree? ...or am I getting faked out somehow?

The voice quality of the calls are pretty good.

Thanks,

traceroute to 194.152.113.13 (194.152.113.13), 30 hops max, 40 byte packets
1 firewall (192.168.100.100) 9.101 ms 1.368 ms 1.496 ms
2 10.100.0.1 (10.100.0.1) 27.001 ms 10.967 ms 29.208 ms
3 68.13.8.173 (68.13.8.173) 17.02 ms 9.996 ms 10.427 ms
4 68.13.9.161 (68.13.9.161) 17.162 ms 18.253 ms 10.105 ms
5 mtc1dsrc02-gew0304.rd.om.cox.net (68.13.14.17) 18.464 ms 19.276 ms 22.469 ms
6 68.13.15.1 (68.13.15.1) 25.616 ms 10.515 ms 12.738 ms
7 12.125.72.49 (12.125.72.49) 16.634 ms 17.92 ms 19.886 ms
8 gar1-p370.mpsmn.ip.att.net (12.122.2.218) 21.553 ms 18.077 ms 22.008 ms
9 tbr1-p012701.cgcil.ip.att.net (12.122.2.222) 30.866 ms 31.511 ms 30.43 ms
10 ggr2-p310.cgcil.ip.att.net (12.123.6.65) 25.906 ms 31.165 ms 31.777 ms
11 att-gw.chi.gblx.net (192.205.32.126) 49.071 ms 48.547 ms 72.803 ms
12 so4-0-0-2488m.ar2.fra2.gblx.net (67.17.65.78) 147.05 ms 148.793 ms 149.227 ms
13 e-tel-austria-ag.ge-1-2-0.402.ar2.fra2.gblx.net (208.51.42.70) 162.926 ms 164.07 ms 163.744 ms
14 pos8-0-0.at-v-d01.redip.etel.at (213.225.19.2) 164.231 ms 165.777 ms 163.324 ms
15 * * *

[PhoneBoy]

They use calling gateways all over the world, so I wouldn't be surprised to see something like you describe. Austria seems to be a bit odd of a place for a calling gateway used for a US call, though.

[mberlant]

This is a little off topic, but in looking at your tracert I see that you have two NAT traversals. What scheme are you using to receive inbound calls successfully?

[lonnie2]

Originally Posted by mberlant

This is a little off topic, but in looking at your tracert I see that you have two NAT traversals. What scheme are you using to receive inbound calls successfully?

I am only doing outbound calls, no phone number.

I have only one NAT device my side of the cable modem, so the cable modem is doing NAT or COX.net is.

I just dumped packet8, and that worked fine for inbound calls.

[lonnie2]

Originally Posted by PhoneBoy

... Austria seems to be a bit odd of a place for a calling gateway used for a US call, though.

Could this be a configuration problem with DeltaThree? Area code 402 is not in their list of incoming numbers yet.

[mberlant]

Dunno. I was keying off the fact that you have a 192.168.y.z address (private) feeding a 10.100.y.z address (also private) before hitting the first public IP address on cox.net. Packet8 must employ a keep-alive mechanism that can reach backwards through two (or more?) NAT boundaries.

[lonnie2]

From iConnectHere Customer Care:

As I understand you wish to better understand the way our routers route outgoing calls to their destinations.

Please be advised that our routers route calls in the most optimal route
at a given moment. This means the call may be routed through Europe or
other destination along the way to its final destination.

This does not necessarily indicates a problem with our service.

However, if you are experiencing any problems with our service please
let us know so we can assist you in troubleshooting these problems.

I don't feel any smarter... I understand that on occasion a European route for a US call might be best, but ALL the time?