Dismiss Notice
We would like to remind you that we’re updating our login process for all 3CX forums whereby you will be able to login with the same credentials you use for the Partner or Customer Portal. Click here to read more.

Outbound rules; Forwarding; hours out of office

Discussion in '3CX Phone System - General' started by DomoJP, Mar 11, 2010.

Thread Status:
Not open for further replies.
  1. DomoJP

    Joined:
    Mar 11, 2010
    Messages:
    6
    Likes Received:
    0
    Hello to everyone and thanks for taking time to read my post.

    At my place, we have to line coming in...
    Let's call them
    - 000 000 0001
    - 000 000 0002

    The two of them are plugged in a Spa400 which is configurated as a gateway in 3cx

    What I'd like to do is to make customs forwarding rules.

    I already have a Virtual Extension which get the line before the AA and if it's in the work-hours, it sends the line to the AA. I did it this way cause I'd like to forward the line to a given cell phone number if its before 9am.

    In this way, I created a forward rule with specific hours, let's say, 7ham to 9ham to send it to the given cellphone.

    When I try from inside, like I hit 170(my virtual extension) it works no problem, the forward happens and make my cell rings. But if the call is from outside, my system isnt able to take a line to call me.

    This happens ( I think ) because of the Spa400 which is considered as only one line by the system, even if I actually have two lines plugged in it.


    So...

    Let me rephrase ;

    If I call 170 from my office phone : my Cellular rings.
    If I call at the office with an external phone : Call is terminated in events.

    11:00:21.083 [CM503008]: Call(121): Call is terminated
    11:00:21.061 [CM503020]: Normal call termination. Reason: No outbound rule
    11:00:21.060 [CM503016]: Call(121): Attempt to reach <sip:170@192.168.2.6:5060> failed. Reason: Busy
    11:00:21.060 [CM303006]: There's no outbound rule for external number '9819*******' defined
    11:00:21.058 [CM303006]: There's no outbound rule for external number '9819*******' defined
    11:00:21.054 [CM503010]: Making route(s) to <sip:170@192.168.2.6:5060>
    11:00:21.051 [CM505002]: Gateway:[spa400] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [] PBX contact: [sip:10000@192.168.2.6:5060]
    11:00:21.040 [CM503001]: Call(121): Incoming call from anonymous@(Ln.10000@spa400) to <sip:170@192.168.2.6:5060>
    11:00:21.029 [CM503012]: Inbound office hours rule (10300) for 10000 forwards to DN:170

    Of course I do have outbounds rules set to if my number start by 9, and contains from 9 to 12 numbers, trim the first number and call. For exemple, if I call from office : It works.


    Any Idea how to do this ? ;) Thanks for your support:D
     
  2. mfm

    mfm Active Member

    Joined:
    Mar 4, 2010
    Messages:
    641
    Likes Received:
    2
    HI,

    Welcome to the Community :p . Check that your outbound rule is not set to allow only extension to dial out. The system is even trying to route it out so your second line is not the problem at this point.

    If that is not the case create a new rule set it as top priority as follows:

    Calls to numbers starting with (Prefix) "1,2,3,4,5,6,7,8,9,0"

    Leave everything else blank and route trough your gateway. If that fails paste the logs again.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
    1701 likes this.
  3. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    11,112
    Likes Received:
    329
    There have been some similar problems with anonymous callers. http://www.3cx.com/forums/anonymous-callerid-will-not-forward-to-outside-line-13344.html#p68587
     
  4. DomoJP

    Joined:
    Mar 11, 2010
    Messages:
    6
    Likes Received:
    0
    This community kick a**!!!

    It's all working, doing an outbound rules as you said (leaving it blank) worked perfectly!
    ¸
    Thanks again :)
     
Thread Status:
Not open for further replies.