Hi,
I am having problem using calling card with freephoneline recently. I use Calling Card to make international calls. It works fine until October. Now I can call the calling card # 416-477-5555 or 416-477-7777. I can hear prompt. But it doesn't seem to reconginize touch tone for PIN or international call #.
Using the same card with Fongo on Android tablet works fine.
No setting change. I am using PAP2t with Acanac Cable internet. Any suggestion?
Thanks.
Jim
Can't Use Calling Card since October 2013
-
- Just Passing Thru
- Posts: 5
- Joined: 03/18/2013
- SIP Device Name: Linksys PAP2T-NA
- Firmware Version: 5.1.6(LS)
- ISP Name: DSL
- Computer OS: Windows 7
- Router: Linksys Wireless G WRT54G
-
- Technical Support
- Posts: 2837
- Joined: 10/18/2009
Re: Can't Use Calling Card since October 2013
Try changing your DTMF type to inband and see it that works.
Log in as admin, click on Line 1, then look for the 'audio configuration' section towards the bottom. There you should see 'DTMF Tx Method:' Try changing that to other things and test.
Log in as admin, click on Line 1, then look for the 'audio configuration' section towards the bottom. There you should see 'DTMF Tx Method:' Try changing that to other things and test.
-
- Just Passing Thru
- Posts: 5
- Joined: 03/18/2013
- SIP Device Name: Linksys PAP2T-NA
- Firmware Version: 5.1.6(LS)
- ISP Name: DSL
- Computer OS: Windows 7
- Router: Linksys Wireless G WRT54G
Re: Can't Use Calling Card since October 2013
Thanks.
I changed my pap2t line 1 DTMF Tx Method from InBand to Auto and it seems allow me to enter the PIN and dial long distance # through the Calling Card. However, once connected, I can hear the other party but they can not hear me. Before October I have no issue using Calling Card and make oversea calls.
Also, when I call another VOIP phone #(CIK telecom), I can hear other party, but they can not hear me. Not sure if these 2 problem are related. Any other suggestion?
Thx
Jim
I changed my pap2t line 1 DTMF Tx Method from InBand to Auto and it seems allow me to enter the PIN and dial long distance # through the Calling Card. However, once connected, I can hear the other party but they can not hear me. Before October I have no issue using Calling Card and make oversea calls.
Also, when I call another VOIP phone #(CIK telecom), I can hear other party, but they can not hear me. Not sure if these 2 problem are related. Any other suggestion?
Thx
Jim
-
- Site Moderator
- Posts: 1689
- Joined: 01/01/2013
Re: Can't Use Calling Card since October 2013
Hi there,JimX wrote:Thanks.
I changed my pap2t line 1 DTMF Tx Method from InBand to Auto and it seems allow me to enter the PIN and dial long distance # through the Calling Card. However, once connected, I can hear the other party but they can not hear me. Before October I have no issue using Calling Card and make oversea calls.
Also, when I call another VOIP phone #(CIK telecom), I can hear other party, but they can not hear me. Not sure if these 2 problem are related. Any other suggestion?
Thx
Jim
Looks like a DNS issue at your end.
Can you open a command prompt on any PC in your network and type this:
ping voip.freephoneline.ca
Please post the output here.
Thanks,
-
- Just Passing Thru
- Posts: 5
- Joined: 03/18/2013
- SIP Device Name: Linksys PAP2T-NA
- Firmware Version: 5.1.6(LS)
- ISP Name: DSL
- Computer OS: Windows 7
- Router: Linksys Wireless G WRT54G
Re: Can't Use Calling Card since October 2013
Thanks. I use voip2.freephoneline.ca. But here are the ping results for both. I chose voip2.freephoneline.ca because I got only one way voice using the voip.freephoneline.ca. I use a TP-link router TL-WR740N and Acanac Cable internet. Thx
1. Pinging fplproxy.fongo.com [208.65.240.44] with 32 bytes of data:
Reply from 208.65.240.44: bytes=32 time=16ms TTL=59
Reply from 208.65.240.44: bytes=32 time=13ms TTL=59
Reply from 208.65.240.44: bytes=32 time=11ms TTL=59
Reply from 208.65.240.44: bytes=32 time=11ms TTL=59
Ping statistics for 208.65.240.44:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 16ms, Average = 12ms
********************************************************************************
2. Pinging fplproxy2.fongo.com [208.65.240.165] with 32 bytes of data:
Reply from 208.65.240.165: bytes=32 time=13ms TTL=59
Reply from 208.65.240.165: bytes=32 time=18ms TTL=59
Reply from 208.65.240.165: bytes=32 time=11ms TTL=59
Reply from 208.65.240.165: bytes=32 time=22ms TTL=59
Ping statistics for 208.65.240.165:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 22ms, Average = 16ms
1. Pinging fplproxy.fongo.com [208.65.240.44] with 32 bytes of data:
Reply from 208.65.240.44: bytes=32 time=16ms TTL=59
Reply from 208.65.240.44: bytes=32 time=13ms TTL=59
Reply from 208.65.240.44: bytes=32 time=11ms TTL=59
Reply from 208.65.240.44: bytes=32 time=11ms TTL=59
Ping statistics for 208.65.240.44:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 16ms, Average = 12ms
********************************************************************************
2. Pinging fplproxy2.fongo.com [208.65.240.165] with 32 bytes of data:
Reply from 208.65.240.165: bytes=32 time=13ms TTL=59
Reply from 208.65.240.165: bytes=32 time=18ms TTL=59
Reply from 208.65.240.165: bytes=32 time=11ms TTL=59
Reply from 208.65.240.165: bytes=32 time=22ms TTL=59
Ping statistics for 208.65.240.165:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 22ms, Average = 16ms
-
- Site Moderator
- Posts: 1689
- Joined: 01/01/2013
Re: Can't Use Calling Card since October 2013
Hi there,JimX wrote:Thanks. I use voip2.freephoneline.ca. But here are the ping results for both. I chose voip2.freephoneline.ca because I got only one way voice using the voip.freephoneline.ca. I use a TP-link router TL-WR740N and Acanac Cable internet. Thx
1. Pinging fplproxy.fongo.com [208.65.240.44] with 32 bytes of data:
Reply from 208.65.240.44: bytes=32 time=16ms TTL=59
Reply from 208.65.240.44: bytes=32 time=13ms TTL=59
Reply from 208.65.240.44: bytes=32 time=11ms TTL=59
Reply from 208.65.240.44: bytes=32 time=11ms TTL=59
Ping statistics for 208.65.240.44:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 16ms, Average = 12ms
********************************************************************************
2. Pinging fplproxy2.fongo.com [208.65.240.165] with 32 bytes of data:
Reply from 208.65.240.165: bytes=32 time=13ms TTL=59
Reply from 208.65.240.165: bytes=32 time=18ms TTL=59
Reply from 208.65.240.165: bytes=32 time=11ms TTL=59
Reply from 208.65.240.165: bytes=32 time=22ms TTL=59
Ping statistics for 208.65.240.165:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 22ms, Average = 16ms
Can you try updating your TPlink to latest firmware and disable sip alg?
http://www.geekzone.co.nz/forums.asp?fo ... icid=94707
In the current firmware version you cannot disable it.(button missing)
http://screenshots.portforward.com/rout ... curity.htm
Thanks,