Getting Busy Signal When Calling Mobile Number To Europe?

[patrob]

I am trying to call my dad on his mobile # in Europe (Plus) and constantly getting busy signal using PAP2T. FPL customer service called and got through but I still can't

Does anyone know what to do??

Thanks in advance,

[dibsmft]

First, I assume that you have plenty of international calling credits and that you know calling cell phones in Europe from Canada is kind of expensive. Can you make calls to landline phones in Europe and "out of free calling" area numbers in Canada?

[Jake]

That sounds like it might be a dial plan error. Can you paste your current dial plan and the number you are actually dialling (put in a few Xs so people don't try and call your dad)

[patrob]

First, I assume that you have plenty of international calling credits and that you know calling cell phones in Europe from Canada is kind of expensive. Can you make calls to landline phones in Europe and "out of free calling" area numbers in Canada?

Yes I have credit and I have called many times before to land lines in Europe and Canada. I only get a busy signal to his cell phone.

[patrob]

That sounds like it might be a dial plan error. Can you paste your current dial plan and the number you are actually dialling (put in a few Xs so people don't try and call your dad)

How do I check my dial plan

Ok found it

(911|[2-9]xxxxxxxxx|1xxxxxxxxxx|011xxxxxxxxxxxx.|98*|[6-7]x*xxxxxxxxxxx.)
Trying to call this # 011 48 72210XXXX

I called FPL twice now about this and nobody ever mentioned anything about my dial plan

[Jake]

OK, I could be worng, but this might be worth a try. See in the middle of your dial plan there is this bit 011xxxxxxxxxxxx. There is 12 x in there which I think represent the number of digits it is expecting after the 011. I believe the final . stands for 'anything else'.

The trouble is your number only has 11 digits after 011, so try taking out one of the x and restart the ATA and see if the call goes through.

[patrob]

OK, I could be worng, but this might be worth a try. See in the middle of your dial plan there is this bit 011xxxxxxxxxxxx. There is 12 x in there which I think represent the number of digits it is expecting after the 011. I believe the final . stands for 'anything else'.

The trouble is your number only has 11 digits after 011, so try taking out one of the x and restart the ATA and see if the call goes through.

Thanks.

Deleted one "x" tried it & still busy signal

[Jake]

Sorry man.
Just to make sure, you did change the right dial plan. You will have two in your ATA, one for each line. Also I think you have to restart the ATA for it to take effect. I usually just pull the plug on it after it has saved the information then power it back up again after a few seconds.

[patrob]

Sorry man.
Just to make sure, you did change the right dial plan. You will have two in your ATA, one for each line. Also I think you have to restart the ATA for it to take effect. I usually just pull the plug on it after it has saved the information then power it back up again after a few seconds.

Line 2 Dial Plan looks diff.
(*xx|[3469]11|0|00|[2-9]xxxxxx|1xxx[2-9]xxxxxxS0|xxxxxxxxxxxx.)

Should they be the same??
Phone is connected to Line 1

Edit: I had no issues calling any other number with 11 digits after 011.

[dibsmft]

(911|[2-9]xxxxxxxxx|1xxxxxxxxxx|011xxxxxxxxxxxx.|98*|[6-7]x*xxxxxxxxxxx.)
...looks like it should work. To make sure that the number pattern fits the Fongo database check the FPL rates table as see what that returns.
Is that a GSM Blackberry number? We had this problem back in March
http://forum.fongo.com/viewtopic.php?f= ... rry#p23708

OK. Just copy and preserve both dial plans. Change Dial Plan 1 to
(0048xxxxxxxxx)
and try calling Poland.
(|<5555:0048yyyyyyyyy>|) where yyyyyyyyy is the remainder of the real number. Dial only 5555
(One of those should work but if it does not then we know that we have to look elsewhere)
If you get success then rebuild the dial plan.

[patrob]

(911|[2-9]xxxxxxxxx|1xxxxxxxxxx|011xxxxxxxxxxxx.|98*|[6-7]x*xxxxxxxxxxx.)
...looks like it should work. To make sure that the number pattern fits the Fongo database check the FPL rates table as see what that returns.
Is that a GSM Blackberry number? We had this problem back in March
http://forum.fongo.com/viewtopic.php?f= ... rry#p23708

OK. Just copy and preserve both dial plans. Change Dial Plan 1 to
(0048xxxxxxxxx)
and try calling Poland.
(|<5555:0048yyyyyyyyy>|) where yyyyyyyyy is the remainder of the real number. Dial only 5555
(One of those should work but if it does not then we know that we have to look elsewhere)
If you get success then rebuild the dial plan.

Thanks again & PM sent.

Don't know if I should change the whole dial plan 1 or change part of it?

[dibsmft]

I wanted you to make a copy of the old dial plan so you can put it back later and replace it with the Polish number alone as (0048xxxxxxxxx) and if that does not work try the (|<5555:0048yyyyyyyyy>|) version where you actually dial 5555 and that actually sends the polish number. You should also check your call records on FPL ro see what is there about the calls.

[Jake]

What dibsmft is suggesting is a very good test. I believe it has something to do with your dial plan because I always get a fast busy signal straight away if I dial a number that is not compatible with my dial plan. For example if I dial 123456.

If the number passed your local dial plan but failed when it got to FPL, then I am sure you would get a message similar to "Your number cannot be completed as dialled...." or "This call is not covered by your ...."

Maybe something like (x.) might work to test. This should allow any number to go through. The main thing is to make sure the dial plan is taking effect when you change it. As I mentioned I always reboot the ATA.

[patrob]

I wanted you to make a copy of the old dial plan so you can put it back later and replace it with the Polish number alone as (0048xxxxxxxxx) and if that does not work try the (|<5555:0048yyyyyyyyy>|) version where you actually dial 5555 and that actually sends the polish number. You should also check your call records on FPL ro see what is there about the calls.

Tried both setups and nothing works.

I am back to my original dial plan.

Thanks for all he help!

[Jake]

Well I did some testing, I placed your original dial plan in my PAP2T and tried the number you gave with 1234 in stead of the XXXX and it got pass the dial plan and got stuck at my PBX as I don't have a dial plan set up to deal with that number. This shows that the dial plan is probably not at fault.

I then fired up my DellVoice on my mobile and tried to dial the same number. I was then given the "you don not have sufficient ..." message because I don't have any long distance credit. This would suggest that the call would have gone through if I had credit.

For testing purposes I would fire up the desktop softphone and try the call from there. I know this isn't how you want to call, but it would test the number. As dibsmft suggest, look in your online logs to see if there is anything that might help in there.

[patrob]

Well I did some testing, I placed your original dial plan in my PAP2T and tried the number you gave with 1234 in stead of the XXXX and it got pass the dial plan and got stuck at my PBX as I don't have a dial plan set up to deal with that number. This shows that the dial plan is probably not at fault.

I then fired up my DellVoice on my mobile and tried to dial the same number. I was then given the "you don not have sufficient ..." message because I don't have any long distance credit. This would suggest that the call would have gone through if I had credit.

For testing purposes I would fire up the desktop softphone and try the call from there. I know this isn't how you want to call, but it would test the number. As dibsmft suggest, look in your online logs to see if there is anything that might help in there.

There is no trace in the call log of me trying to make a call. I tried both suggestions, didn't work.

It's very weird that you can call everywhere else but not this one number

[Jake]

Well if you can't call via the softphone/app and you are not getting an error message, I can only think that Fongo does not have Polish Mobiles starting with 72 in their rate tables. I think this needs to be picked up by someone who is willing to go the extra mile. I think the forum has done about as much as it can, we obviously can't get in the actual workings of Fongo.

My recommendation is to PM FONGO_mike and /or FONGO_neil (although I have not seen him around for a while) and include a link to this thread, along with the full phone number you are trying to call, and ask them to try the number on their end, or at least double check in the rate tables that the number will actually go somewhere.

One of them might pick this up in the morning. If you have the patience you can always try calling in again.

Someone else might have some ideas in the meantime.

[patrob]

Well if you can't call via the softphone/app and you are not getting an error message, I can only think that Fongo does not have Polish Mobiles starting with 72 in their rate tables. I think this needs to be picked up by someone who is willing to go the extra mile. I think the forum has done about as much as it can, we obviously can't get in the actual workings of Fongo.

My recommendation is to PM FONGO_mike and /or FONGO_neil (although I have not seen him around for a while) and include a link to this thread, along with the full phone number you are trying to call, and ask them to try the number on their end, or at least double check in the rate tables that the number will actually go somewhere.

One of them might pick this up in the morning. If you have the patience you can always try calling in again.

Someone else might have some ideas in the meantime.

Actually FPL does have that same extension listed in their long distance rates:

Poland - Plus Gsm Mobile 48722 $0.16

My brother who also has FPL also cannot call that same mobile number

I will PM them & see what happens but so far FPL customer service has not been very helpful at all!

Thanks to everyone else who has been helping so far, really appreciate it

[Jake]

I will PM them & see what happens but so far FPL customer service has not been very helpful at all!

That's why I suggested to PM the FONGO staff that frequent the forum. They really are top notch and usually get the more trickier problems sorted out, or are able to ask the right people the right questions. I would also suggest to PM FONGO_steve, but I think he is still away.

Let us know how you get on, it might help us help others who have similar problems in the future.

[FONGO_mike]

Hello,

I know this sound silly, and you have likely done it, but i have seen this happen to many times before to not mention it. When updating the string, before rebooting, are you making sure to update/save in your Linksys? (again, i know it sounds silly, but even here we forget sometimes)

Also, the thread for the recommended configuration of your device (Linksys PAP2T) can be found in our forums here.

[Jake]

Hello,

I know this sound silly, and you have likely done it, but i have seen this happen to many times before to not mention it. When updating the string, before rebooting, are you making sure to update/save in your Linksys? (again, i know it sounds silly, but even here we forget sometimes)

Also, the thread for the recommended configuration of your device (Linksys PAP2T) can be found in our forums here.

I think he has tried to dial using the desktop app, or phone app - so I don't think the dial string has anything to do with it now. I also tried his dial string in my pap2t and it passed when I tried to dial the number. At least it got to my PBX before it got rejected.

[dibsmft]

I agree with Jake. From what I have been able to learn about the efforts to call these numbers, it does seem that the number is being rejected at the Fongo server level. It is difficult to know why but they are expensive numbers and are being charged at premium rates like calls to iNUM numbers. The going rate is probably about 10 US cents/min but, while FPL can charge what they like, it would be better if they were not listed at all if they can't be called. Very frustrating for the user who probably purchased calling credits just to make calls to family back home.

[FONGO_mike]

My best suggestion in this case would then be to call and speak to a live customer representative to report issues calling the number. They can then look into why it may not be going through. Let them know that when you call from the soft phone this is the result you are getting.