Mobiion Forum  
May 23, 2012, 04:00:36 am *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
News:
 
   Home   Help Search Login Register  
Pages: 1   Go Down
  Print  
Author Topic: Error: Cannot complete the call  (Read 2608 times)
dylan.thurston
Newbie
*
Offline Offline

Posts: 3


View Profile
« on: March 23, 2009, 05:49:45 am »

So I'm testing out the software (trial) 2.2.2 and i've been running into problems:

I have a single rule setup to change outgoing phone numbers. Here is the rule:

Rule Type: outgoing call
Filter Type: All
Enabled: Always
Action 1: Change dailed number (you might want to fix that spelling mistake)
Call to: 801788XXXX, 2,-{phone}#

This rule is setup so that when i dial a number from my phone it actually dials my google voice account and then selects the menu (2) and then enters the phone number i want tried to dial. This is just like dialing via a calling card (i guess).

The problem is some times (most of the time) It tries to dial the actual number first, then it hangs up (this takes a few seconds (15-20)). Then it dials the phone number in the rule. When it attemps to dial the phone number (listed in the rule) it fails with an error listed below:

Cannot Complete the call the signal may be unavailable or the phone number may not be valid verify the number or later.

After this the phone usually stops being able to complete any call (magicall off or on), until i reset the phone. (i have a samsung i760)

The only thing i can figure is that the phone hangs up and tries to dial too quickly. This is just a shot in the dark. BTW is there any way to intercept the call prior to it dialing the first time. (ie not having to dial the real number, followed by a hang up). It seems like a much better thing to do.

On one final note, is there a way to blacklist numbers from a rule. I want it to alter the number except when i am directly dialing my google voice number (to check voice mail). Right now it tries change the number from 801788XXXX to 801788XXXX,2,801788XXXX#
(notice the redundant change.)

oh yeah and as a feature request i'd love to be able to filter the changed number out of the call history so i don't end up with two entries:
call history 1: 801319XXXX
call history 2: 801788XXXX,2,801319XXXX,#

I don't want "call history 2" to be in my call history.

Well thats it. Please let me know if there is a fix for my problem. Right now magicall is useless when i can't dial a number without my phone crashing.
-Dylan
Logged
LB2064
Jr. Member
**
Offline Offline

Posts: 63


View Profile
« Reply #1 on: March 23, 2009, 11:24:53 am »

Hi Dylan, let me see if I can help.

One the first problem: try Change dailed number (v2).  This tends to work better for the calling card type prompts.
Also you may want to try more commas, e.g:
Call to: 801788xxxx,,2,,-{phone},#

On the second problem, I think you should create another rule above your calling card rule like this:

Rule Type: Outgoing call
Filter Type: Specific Number
Phone #: 801788xxxx
Action1: System Default
Action2: Do Nothing 

Be sure this rule is above your calling card rule.

Hope this helps.  If not, I'm sure the Admin could probably solve your issues.

Logged

L
dylan.thurston
Newbie
*
Offline Offline

Posts: 3


View Profile
« Reply #2 on: March 23, 2009, 12:07:06 pm »

Sorry i wrote it wrong. I am using the change dialed number v2 (which in the program is spelled incorrectly.)

I did figure out that i can use ~80178XXXX as the phone number in the rule and it will apply the rule to everything but the 801788XXXX number.

Adding more pauses will not affect the problem, since the error happens before it actually gets to the part. It tries to dial the number first (801788XXXX) which would be follow by the the 2 and pauses and the rest. The problem is that it fails before it connects to the number (it never actually dials the the new outgoing rule based number). in the few instances that it doesn't report the cannot dial error it works just fine. The pauses are exactly the right length and everything works. However most of the it errors before ever connecting the modified number.

I hope that explains the problem i'm having.
-Dylan
Logged
admin
Administrator
Hero Member
*****
Offline Offline

Posts: 1188


View Profile
« Reply #3 on: March 23, 2009, 02:33:43 pm »

@lb2064
Thank you for your answer.

@dylan.thurston
Thank you for pointing out the spelling mistake. I will correct it in next version.

"Change dialed number" is better than v2 for you. I have received some reports that v2 is not working well sometimes. I will improve it in future versions. Since you don't use USSD, so v1 is a better choice for you. But you may need to add more pauses with v1. Take a look at the following:

Rule Type: Outgoing call
Filter Type: Specific number
Phone #: ~801788XXXX
Action 1: Change dialed number
Call to: 801788XXXX,,2,,-{phone}#

Hope my answer can help you. Thanks.
« Last Edit: March 23, 2009, 02:35:21 pm by admin » Logged
dylan.thurston
Newbie
*
Offline Offline

Posts: 3


View Profile
« Reply #4 on: March 23, 2009, 04:09:17 pm »

Wow thanks, i think that fixed. It even looks like it hooks the call prior to making the call (doesn't hang up and try dialing again) And so far calls seem to go through ok. This rocks.

On another great note. The new settings also eliminate the need to filter the call history. All of the calls being made now appear in the history unchanged. This is exactly what I need. Now my google voice account is a go.

Thanks so much.
-Dylan
Logged
Pages: 1   Go Up
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.11 | SMF © 2006, Simple Machines LLC Valid XHTML 1.0! Valid CSS!