Solved Unable to dial to numbers starting with + after upgrade from V15 to V16

Status
Not open for further replies.

danavni

Customer
Joined
Dec 5, 2010
Messages
22
Reaction score
0
On V15 using the 3cx windows client we were able to dial to +972541234567. After the upgrade to V16 I now get an error on the activity log and the client imminently hangs
The activity log has the following
10/04/2019 4:47:19 PM - [CM503016]: Call(C:5): Attempt to reach <sip:+972541234567@ip:0> from Extn:241 has failed. Reason: Not Found
10/04/2019 4:47:19 PM - [CM503014]: Call(C:5): No known route from Extn:241 to target: <sip:+972541234567@ip:0/UDP>
10/04/2019 4:47:19 PM - Call(C:5): from Extn:241 to +972541234567 doesn't match any outbound rule. No outbound rule could be selected.
10/04/2019 4:47:19 PM - [Flow] Target endpoint for +972541234567 can not be built!
10/04/2019 4:47:19 PM - Looking for outbound rule: dialed = [+972541234567], processed: [541234567]; from-ext:
10/04/2019 4:47:19 PM - [Flow] Building target endpoint to +972541234567 from "Extension" <sip:241@ip:0>

I do have an outbound rule for numbers with prefix +972 and length 13 strip 4 digits and prepend 0 and send to the SIP trunk we are connected to (resulting in replacing +972 with 0 so the number would be 0541234567

What am I missing? As I said this was working in V15
 
dialled as [+XXX541234567]
processed in outbound rules as [541234567]

The processed as comes from your E165 settings

ps ( I would mask the phone numbers to avoid someone spamming you with calls)
 
Please look at your outbound rules one by one, and ensure that Route 1 points to the trunk you want to use.
 
Please look at your outbound rules one by one, and ensure that Route 1 points to the trunk you want to use.
All outbound routes have route1 set and the others are blocked (see attached image - actual route name was blurred)

@StefanW, I know my SIP provider cannot handle the + sign that is why I have an outbound rule to remove the +972 and replace it with 0 (converting +972541234567 to 0541234567).
P.S All numbers were already obfuscated. I do not have a phone number 1234567 :)
 

Attachments

  • Routes.jpg
    Routes.jpg
    100.3 KB · Views: 24
You should be using the 3CX E164 options to convert the + to the correct national/international prefix, then use the outbound rules to strip/prepend then route, based on the new (all numeric) number.
 
I changed the E164 settings to append a 0 prefix and it looks ok now. Has this changed from V15?
 
Hi @danavni

I'm glad to hear it works now. I don't think this has changed
 
Status
Not open for further replies.

Forum statistics

Threads
111,934
Messages
589,818
Members
164,810
Latest member
astrobalaji