I don't think it is a filter (SIP uses UDP, so telneting to the port
(which uses TCP) doesn't mean much.
There is a problem right now with receiving incoming calls from
iconnecthere/d3. Something on d3's end is messed up. It hits the
asterisk server, and then cancels the connection. I'm
I don't think it is a filter (SIP uses UDP, so telneting to the port
(which uses TCP) doesn't mean much.
There is a problem right now with receiving incoming calls from
iconnecthere/d3. Something on d3's end is messed up. It hits the
asterisk server, and then cancels the connection. I'm stumped.
Symptoms: when calling my iconnect phone number (13033913323 in my
bogus example below) from my cell phone, I can see that the call
makes it to my asterisk server, and my phones even ring once as *
passes the call through during the 180 Ringing period. However, it
seems that iconnecthere.com
John,
A heads-up: iconnect has apparently put up a filter against my IP address,
for whichever reason (apparently they don't like people using asterisk?).
I've sent them an email and am pursuing this also through sales side (I'm
about to make a resale deal with them), so hopefully tomorrow
John Todd wrote:
Symptoms: when calling my iconnect phone number (13033913323 in my bogus
example below) from my cell phone, I can see that the call makes it to
my asterisk server, and my phones even ring once as * passes the call
through during the 180 Ringing period. However, it seems that