Outgoing rule is not handled correctly

Discussion in '3CX Phone System - General' started by 3cxisti, Feb 18, 2013.

Thread Status:
Not open for further replies.
  1. 3cxisti

    Joined:
    Dec 11, 2012
    Messages:
    21
    Likes Received:
    0
    Hi,

    I have a outgoing rule für mobile number beginning with "+" (eg. +49179....)

    If I call this number the outgoing rule is not mached and the call is not forwarded to the correct trunk.

    What can be the reason?

    This is my outgoing rule:
    +49151,+49152,+49157,+49159,+49160,+49162,+49163,+49170,+49171,+49172,+49173,+49174,+49175,+49176,+49177,+49178,+49179

    On the top of the rule-list. It is set that the first "+" must be cut and repleaced by "00".

    I see in the log, that the number is received correctly "+49179" but sent false "+49179". The reason is the a later rule matches which formats the number on a false way.

    Has somebody already had such troubles with correct but not matching rules?

    Thank you...

    I.
     
  2. AndreasP_3CX

    AndreasP_3CX New Member
    3CX Support

    Joined:
    Feb 15, 2013
    Messages:
    196
    Likes Received:
    2
    This blog explains the outbound rules in good detail please go to this link and follow the instructions. it should help you set up your rules correctly http://www.3cx.com/blog/voip-howto/outbound-rules-a-complete-example/
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. Roman.Stryuk

    Joined:
    Jan 15, 2015
    Messages:
    1
    Likes Received:
    0
    Hi 3cxisti,

    Have you found some solution for this problem? As far as the article mentioned above does not provide any example for the numbers leaded with "+".

    Thanks!
     
  4. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,374
    Likes Received:
    231
    I believe it has to do with the implementation of E164.

    have a look over this... http://www.3cx.com/forums/outbound-rules-with-solved-16569.html#p84305
     
Thread Status:
Not open for further replies.