• V20: 3CX Re-engineered. Get V20 for increased security, better call management, a new admin console and Windows softphone. Learn More.

Free World Dialup outbound call problem

Status
Not open for further replies.

catweazle999

Joined
Feb 17, 2007
Messages
6
Reaction score
0
hi all, i have a question regarding calling into FWD and then to a peering partner of FWD like sipgate or any other SIP provider who can be dialled by using the **<SIP-No of provider> like **777 for sipgate Germany.

Everything is running fine, i can be called from outside, i also can reach the test numbers from FWD like the 613 echo test. But like mentioned i cannot go ahead dial another SIP provider.

I have an outbound rule with '0' as the prefix, i dial the 0613 for the echo test of FWD and it works.

But when i want to dial 0**77749xxxxxx for a number of sipgate germany it does not run. Anyhow it seems that this call is not recognized as an outbound call ?!?

the log show this:
19:12:06.875 CallConf::eek:nIncoming: Can not resolve target for call from "Koch, Marcel"<sip:[email protected]>;tag=c9723450 to "0**77749xxxxxxx"<sip:0**[email protected]>
19:12:06.875 CallConf::Rejected: Call (C:79) is rejected: Target is not resolved
19:12:06.845 CallConf::eek:nIncoming: Incoming call from Ext.101 to sip:0**[email protected]

it does not seem to use first the 10000 external line. Could it be that the problem is the '*' within the number ?

does anyone ever did a successful call from FWD to a peering partner with 3CX ?
 
The asterisk '*' causes the problem

ok, i did some more tests and i also could connect to other numbers.
So, the asterisk character in the dial string (like **777 for sipgate)
confuses the outbound rule.

Seems that only numbers with integers are working ?
Is there any workaround on this ?
 
Hi, Currently the * in the dialed number will make the call fail, so at the moment peering is not possible.
 
special characters not recognized within a dial string

ok, thanks for your fast feedback.

But that would mean that peering is not possible with lots of providers other than FWD. I checked a dozen of different SIP providers and the majority of them are having special characters like the * in their prefix dial strings when dialing a peering partner network.

will that issue be fixed in one of the future releases ?

or - can you recommend other providers who do not use a * in their prefixes ?

i know, at least SIPGate just uses integers....
 
Hi, Yes it should be resolved in the near future, we are sorry for the inconvinience it may be causing you in the meantime. I can't give you an exact date when it will be included, but please 'stay tuned' for the few next updates. You can keep an eye on the buildhistory at:

http://www.3cx.com/buildhistory.html
 
Status
Not open for further replies.
Get 3CX - Absolutely Free!

Link up your team and customers Phone System Live Chat Video Conferencing

Hosted or Self-managed. Up to 10 users free forever. No credit card. Try risk free.

3CX
A 3CX Account with that email already exists. You will be redirected to the Customer Portal to sign in or reset your password if you've forgotten it.