Cannot connect to outlying exchanges

[nelson@3quirks.ca]

Any calls in Canada to area codes and exchanges within FPL work, but if I call others in Canada that would be LD, I get no ringing and no answer on the other end.

LD calls to US cities appear to work.

Some examples:

1-902-862-xxxx New Waterford, NS (tried many)
1-902-533-28xx Guysborough, NS
1-902-564-9670 Sydney, NS

Plenty of calls tested and in my logs for reference

Any thoughts?

[nelson@3quirks.ca]

I also had a friend of mine who uses the same hardware on FPL the Sydney # with the same results. He is also using an SPA-1001 but with an earlier firmware version.

Plan to have an additional friend try with a Grandstream from FPL tonight to see the results.

[nelson@3quirks.ca]

When dialed, within approx 2-3 seconds, it appears as though the call connects, but after 30-35 seconds, I get a fast busy signal.

interestingly enough, the first few calls you can see it states No User responding (it rang on their end, but when they picked up, nothing. I couldn't hear a ring nor hear them) After that, it referenced Normal Call Clearing and continue to do so. Confirmed with receiving party they hear no incoming call/ring.

16136639215 190286276xx 0:00 11.05.12 19:40:21 11.05.12 19:40:21 No user responding CANADA $ 0.00
16136639215 19025332854 0:00 11.05.12 19:41:28 11.05.12 19:41:28 No user responding CANADA $ 0.00
16136639215 190286276xx 0:00 11.05.12 19:52:05 11.05.12 19:52:05 Normal call clearing CANADA $ 0.00
16136639215 190286276xx 0:00 11.05.12 19:53:34 11.05.12 19:53:34 Normal call clearing CANADA $ 0.00

Interestingly enough, after calling many #s many times, the odd time I get No User responding. No connect charges and the fast busy after 30-35 seconds

1613663xxxx 19028626050 0:00 11.05.12 21:11:30 11.05.12 21:11:30 Normal call clearing CANADA $ 0.00
1613663xxxx 19025649670 0:00 11.05.12 21:14:46 11.05.12 21:14:46 Normal call clearing CANADA $ 0.00
1613663xxxx 19028626050 0:00 11.05.12 21:16:59 11.05.12 21:16:59 Normal call clearing CANADA $ 0.00
1613663xxxx 19028626050 0:00 11.05.12 21:18:34 11.05.12 21:18:34 Normal call clearing CANADA $ 0.00
1613663xxxx 19028626050 0:00 11.05.12 21:29:51 11.05.12 21:29:51 Normal call clearing CANADA $ 0.00
1613663xxxx 14169472333 0:00 11.05.12 21:42:17 11.05.12 21:42:17 Normal call clearing Toronto ON $ 0.00
1613663xxxx 19028801395 0:00 11.05.12 21:46:18 11.05.12 21:46:18 Normal call clearing Halifax NS $ 0.00
1613663xxxx 19028626050 0:00 11.05.12 21:47:30 11.05.12 21:47:30 Normal call clearing CANADA $ 0.00
1613663xxxx 19025332854 0:00 11.05.12 21:51:22 11.05.12 21:51:22 Normal call clearing CANADA $ 0.00
1613663xxxx 19025649670 0:00 11.05.12 21:57:43 11.05.12 21:57:43 Normal call clearing CANADA $ 0.00
1613663xxxx 19025649670 0:00 11.05.12 22:18:45 11.05.12 22:18:45 No user responding CANADA $ 0.00
1613663xxxx 19025649670 0:00 11.05.12 23:24:44 11.05.12 23:24:44 Normal call clearing CANADA $ 0.00
1613663xxxx 19025649670 0:00 12.05.12 08:04:03 12.05.12 08:04:03 Normal call clearing CANADA $ 0.00

[FONGO_steve]

Hi nelson,
Have you tried your calls since Friday? I noticed all the call logs you've been posting are dated by quite a few days.
Let me know if you're seeing any improvement after the weekend.

[nelson@3quirks.ca]

Steve

I found the issue. I've used many dial strings

FPL Recommended - (911|[2-9]xxxxxxxxx|1xxxxxxxxxx|011xxxxxxxxxxxx.|98*|[6-7]x*xxxxxxxxxxx.)
Dial String from friend using same device - (*xx|911|1xxxxxxxxxx|[2-9]xxxxxxxxx|0xxxxx.)
My own custom - (911S0|<311:6135802400>S0|<411:18005551212>S0|[2-9]xxxxxxxxxS0|1xxx.S0|011xxxxxxxxxxxx.|x11S0|*xxS0|[6-7]x*xxxxxxxxxxx.)

All 3 gave me the same results. However, although I have 1xxxxxxxxxx, if I use the leading 1 it doesn't connect. If I drop the leading 1, it connects. Interestingly enough, using the 1 in front of another 902 area code (in Halifax) which is part of the covered exchanges by FPL, the leading 1 will connect.

What I did was modify the dial string to 1xxx. and it now works with the leading 1.

What's even more bizarre, is two people using the following dial string (*xx|911|1xxxxxxxxxx|[2-9]xxxxxxxxx|0xxxxx.) and an SPA-1001, and both in 613 have different results. One works with the leading 1, the other doesn't. And, another colleague has the same issue I have using a FPL provided Grandstream 286.