Emergency Number 000 in Australia

Discussion in '3CX Phone System - General' started by Peter Richardson, May 27, 2017.

Thread Status:
Not open for further replies.
  1. Peter Richardson

    Peter Richardson New Member

    Joined:
    Apr 6, 2017
    Messages:
    149
    Likes Received:
    5
    Hi all,

    I am having trouble getting 000 to work. I have created an outbound rule for:

    Calls to numbers starting with prefix: 000
    Calls to numbers with a length of: 3
    Route 1: <sip trunk>
    Strip digits: 0
    Prepend: <blank>

    I just get the error: Call failed, Forbidden

    Please help!
     
  2. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,357
    Likes Received:
    224
    I'm assuming that you have looked at the 3CX Activity log generated for the call and that is where the "forbidden" is showing?
    There should be a place in 3CX to enter the emergency number (there used to be). That may allow the calls to go through.
    There may be an international number blocking function that is currently preventing that calls. If you haven't done so, try setting the log for more details, that may explain exactly why the call is forbidden.
     
  3. Peter Richardson

    Peter Richardson New Member

    Joined:
    Apr 6, 2017
    Messages:
    149
    Likes Received:
    5
    Thanks @leejor. I got that message from the soft phone. Here's a message from the log:

    05/27/2017 2:31:15 PM - Call to T:Line:10000>>000@[Dev:sip:SIP PROVIDER:5060] from L:839.1[Extn:108] failed, cause: Cause: 403 AU emergency numbers not enabled on this account/INVITE from IP ADDRESS:5060

    AU emergency numbers not enabled on this account - how do I enable? I've checked the logs on the SIP provider, and they're not registering any calls to 000, so it doesn't appear to be reaching the SIP provider.
     
  4. lneblett

    lneblett Well-Known Member

    Joined:
    Sep 7, 2010
    Messages:
    2,061
    Likes Received:
    56
    Form the text provided, I am guessing that the provider is the one rejecting the call. I doubt that 3CX knows enough to provide a rejection message of "AU emergency numbers,,,,,,,," on its own and also make reference to an account. I think you should contact the provider about this one. In the US, there is e911 and this requires a registration with the provider so that they know the address associated to the account/DID/DNIS in the event that responders are needed. Some may charge a small extra fee and I am guessing that something is similar in your case.
     
  5. Peter Richardson

    Peter Richardson New Member

    Joined:
    Apr 6, 2017
    Messages:
    149
    Likes Received:
    5
    @Ineblett thanks for your message. I'll email the SIP provider and I'll let you know their response.
     
  6. Peter Richardson

    Peter Richardson New Member

    Joined:
    Apr 6, 2017
    Messages:
    149
    Likes Received:
    5
    @leejor the "forbidden" is showing when I dial it from a softphone - ie: my laptop. It shows forbidden in the bit that normally says "on hook" then beeps three times.
    I have set the log to verbose.

    Here's an excerpt of the log:

    06/18/2017 11:45:32 AM - Event has been sent successfully
    06/18/2017 11:45:32 AM - Sent 1843 bytes
    06/18/2017 11:45:32 AM - Sending 1843 bytes to CHR
    06/18/2017 11:45:32 AM - Sending event to Call History Receiver
    06/18/2017 11:45:32 AM - ~Call(C:26)
    06/18/2017 11:45:32 AM - SLA: #0 'idle' -> 'idle'
    06/18/2017 11:45:32 AM - ~CallLeg(C:26.1)
    06/18/2017 11:45:32 AM - InviteADS::destroy:58
    06/18/2017 11:45:32 AM - Call(C:26) has been terminated already
    06/18/2017 11:45:32 AM - Call(C:26): Legs count: 0
    06/18/2017 11:45:32 AM - Stop call record for leg L:26.1[Extn:103]
    06/18/2017 11:45:32 AM - Removing leg L:26.1[Extn:103]
    06/18/2017 11:45:32 AM - L:26.1[Extn:103]: Terminating targets, reason:
    06/18/2017 11:45:32 AM - Leg L:26.1[Extn:103] is terminated: Cause: BYE from PBX
    06/18/2017 11:45:32 AM - Ignored: SE:26.1{OnHook}
    06/18/2017 11:45:32 AM - Issue: [Pres:103; act=Open;0;88626]
    06/18/2017 11:45:32 AM - StatusNotification: SE:26.1{OnHook}; Skip=0
    06/18/2017 11:45:32 AM - Device (1981915795) is used in 0 calls: []
    06/18/2017 11:45:32 AM - Terminated from "Peter MacBook Pro"<sip:103@obfuscated.3cx.com.au:5060>;tag=qzpCRsWsmhHpV.MNLGFDaqId9-x8g2AV to <sip:000@obfuscated.3cx.com.au:5060>;tag=d98cf33e; reason: Rejected
    06/18/2017 11:45:32 AM - L:26.1[Extn:103] Sending: OnSendResp Send 403/INVITE from 0.0.0.0:0 tid=PjE7tC2gYqbZ51SZH3VcaYDwSSQhqCOGrV Call-ID=gSWvhUhTg5rzw3J-qxcwf7nHEPtqZfra: SIP/2.0 403 Forbidden Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bK-524287-2---PjE7tC2gYqbZ51SZH3VcaYDwSSQhqCOGrV;rport=5080 Via: SIP/2.0/UDP 14.2.141.47:50922;branch=z9hG4bK-524287-1---tunneltid;rport;tnlid=clnt.1-e.su-dhtmrggokfjno9gexpt53peeixm Via: SIP/2.0/TCP 192.168.179.25:50195;rport;branch=z9hG4bKPjE7tC2gYqbZ51SZH3VcaYDwSSQhqCOGrV;alias To: <sip:000@obfuscated.3cx.com.au:5060>;tag=d98cf33e From: "Peter MacBook Pro"<sip:103@obfuscated.3cx.com.au:5060>;tag=qzpCRsWsmhHpV.MNLGFDaqId9-x8g2AV Call-ID: gSWvhUhTg5rzw3J-qxcwf7nHEPtqZfra CSeq: 14160 INVITE Warning: 499 3cx.obfuscated.com.au "Forbidden" Content-Length: 0
     
  7. JasonNadeau

    JasonNadeau Member

    Joined:
    Oct 14, 2015
    Messages:
    262
    Likes Received:
    46
    Leejor is almost certainly correct. Did you check with your provider yet? Not really worth troubleshooting further until you speak with them ...
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  8. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,357
    Likes Received:
    224
    I'm not certain how much more clear the messages (from your provider) need to be. It's spelling it out in plain English. Many VoIP providers will not "handle" emergency calls unless...you pay an additional charge, and/or , register the address that the service is used from. If you place an emergency call, then hang up before the call is answered, or after it is answered, they generally want to be able to trace to the location the call was originated. Your provider would have to provide your address to the Emergency Services.
     
    YiannisH_3CX and StefanW like this.
Thread Status:
Not open for further replies.