Fongo Community Forums

anyone know what's wrong? thanks.

Are you dialing without a 1? Using ATA or softphone?
I was just testing a bunch of 800 numbers for someone before I left yesterday and didn't experience any issues.

FPL-steve wrote:Are you dialing without a 1? Using ATA or softphone?
I was just testing a bunch of 800 numbers for someone before I left yesterday and didn't experience any issues.

I am using Softphone. I did dial 1. The number I dialed are 1-866 and 1-888.

stevew wrote:

FPL-steve wrote:Are you dialing without a 1? Using ATA or softphone?
I was just testing a bunch of 800 numbers for someone before I left yesterday and didn't experience any issues.

I am using Softphone. I did dial 1. The number I dialed are 1-866 and 1-888.

try without 1. Our system automatically prefixes it

FPL-steve wrote:

stevew wrote:

FPL-steve wrote:Are you dialing without a 1? Using ATA or softphone?
I was just testing a bunch of 800 numbers for someone before I left yesterday and didn't experience any issues.

I am using Softphone. I did dial 1. The number I dialed are 1-866 and 1-888.

try without 1. Our system automatically prefixes it

Same problem. it display"failed"

What's the number you're calling? If it can't be posted publicly, then feel free to send it in a PM to me. I'll give it a try with my account and check your SIP Logs here.

FPL-steve wrote:What's the number you're calling? If it can't be posted publicly, then feel free to send it in a PM to me. I'll give it a try with my account and check your SIP Logs here.

Please try this one: 1-888 242 2100

stevew wrote:

FPL-steve wrote:What's the number you're calling? If it can't be posted publicly, then feel free to send it in a PM to me. I'll give it a try with my account and check your SIP Logs here.

Please try this one: 1-888 242 2100

I could reach that one just fine on my ATA configured with or default settings. I tried on the softphone and for some reason their IVR didn't pickup on the first call that connected, but my next two calls went through just fine. Checking your PM one now

I could reach it with and without the 1:

08:33:12.181 Wed 13 Jan 2010, 208.65.240.142:5060/udp (241 bytes): received
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.124:6060;rport=6060;branch=z9hG4bK30508
From: <sip:1519804xxxx@208.65.240.142>;tag=z9hG4bK01117848
To: <sip:18882422100@208.65.240.142>
Call-ID: 081315759612@208.65.240.142
CSeq: 1 PING
Server: Sippy

-----End-of-message-----

UA: ACCEPTED/CALL
JMFAudioLauncher: launching JMF-Audio...

08:30:54.924 Wed 13 Jan 2010, 208.65.240.142:5060/udp (613 bytes): SIP/2.0 200 OK, received
08:30:54.934 Wed 13 Jan 2010, 208.65.240.142:5060/udp (404 bytes): ACK sip:8882422100@voip.freephoneline.ca SIP/2.0, sent
08:30:54.934 Wed 13 Jan 2010, 208.65.240.142:5060/udp (482 bytes): ACK sip:208.65.240.142:5061 SIP/2.0, sent

UA: ACCEPTED/CALL
UA: DEBUG: media application is already running

08:30:57.446 Wed 13 Jan 2010, 208.65.240.142:5060/udp (420 bytes): BYE sip:208.65.240.142:5061 SIP/2.0, sent
08:30:57.456 Wed 13 Jan 2010, 208.65.240.142:5060/udp (294 bytes): SIP/2.0 200 OK, received
08:31:12.170 Wed 13 Jan 2010, 208.65.240.142:5060/udp (375 bytes): PING sip:1@208.65.240.142 SIP/2.0, sent
08:31:12.180 Wed 13 Jan 2010, 208.65.240.142:5060/udp (241 bytes): SIP/2.0 200 OK, received
08:31:42.170 Wed 13 Jan 2010, 208.65.240.142:5060/udp (375 bytes): PING sip:1@208.65.240.142 SIP/2.0, sent
08:31:42.180 Wed 13 Jan 2010, 208.65.240.142:5060/udp (241 bytes): SIP/2.0 200 OK, received
08:32:12.171 Wed 13 Jan 2010, 208.65.240.142:5060/udp (375 bytes): PING sip:1@208.65.240.142 SIP/2.0, sent
08:32:12.181 Wed 13 Jan 2010, 208.65.240.142:5060/udp (241 bytes): SIP/2.0 200 OK, received

it might be something wrong. by the way i am using laptop and wireless router. do i need set-up something on laptop or router for enabling dialing 1-800? thanks

It should work right away, if you have a DMZ I might but my laptop in it, but it's up to you.

Just an update on this for our curious readers: many 800 number carriers will block incoming calls from people who hide their caller-ID and call as 'anonymous'.
That was simply the issue here that I found in our logs. The original poster has confirmed that it works great after unblocking caller-ID.

Thanks Steve. The reason is the blocked the ID. Now it is working.