QUESTION Route Congestion Messages - how to set properly?

[papachumba]

So, at the moment when I dial an incorrect number from the extension, I get back
"All circuits are busy, please try again later"

Then, randomly when I dial the exact same incorrcet number I will get "You have dialled an incorrect number, please try again later". This seems to have been sent via our SIP provider I think (cannot see anything played back in console, its as if asterisk still thinks the call is ok - after the message there is no hangup, just a dead line until I put the phone down.

My question is how is it that sometimes I get the "all circuits busy" message, and sometimes the correct error message plays.

When all circuits message comes up, this is what I get in console:

 Using SIP RTP TOS bits 184
  == Using SIP RTP CoS mark 5
    -- Called SIP/orbtalk-out/0797324000
    -- SIP/MyCompany-000014a3 answered SIP/723-000014a2
    -- Got SIP response 503 "503-Service Unavailable" back from myproviderIP:5060
    -- SIP/orbtalk-out-000014a5 is circuit-busy
  == Everyone is busy/congested at this time (1:0/1/0)
    -- Executing [s@macro-dialout-trunk:23] NoOp("SIP/707-000014a4", "Dial failed for some reason with DIALSTATUS = CONGESTION and HANGUPCAUSE = 34") in new stack
    -- Executing [s@macro-dialout-trunk:24] GotoIf("SIP/707-000014a4", "0?continue,1:s-CONGESTION,1") in new stack
    -- Goto (macro-dialout-trunk,s-CONGESTION,1)
    -- Executing [s-CONGESTION@macro-dialout-trunk:1] Set("SIP/707-000014a4", "RC=34") in new stack
    -- Executing [s-CONGESTION@macro-dialout-trunk:2] Goto("SIP/707-000014a4", "34,1") in new stack
    -- Goto (macro-dialout-trunk,34,1)
    -- Executing [34@macro-dialout-trunk:1] Goto("SIP/707-000014a4", "continue,1") in new stack
    -- Goto (macro-dialout-trunk,continue,1)
    -- Executing [continue@macro-dialout-trunk:1] NoOp("SIP/707-000014a4", "TRUNK Dial failed due to CONGESTION HANGUPCAUSE: 34 - failing through to other trunks") in new stack
    -- Executing [continue@macro-dialout-trunk:2] Set("SIP/707-000014a4", "CALLERID(number)=707") in new stack
    -- Executing [0797324000@from-internal:7] Macro("SIP/707-000014a4", "outisbusy,") in new stack
    -- Executing [s@macro-outisbusy:1] Progress("SIP/707-000014a4", "") in new stack
    -- Executing [s@macro-outisbusy:2] GotoIf("SIP/707-000014a4", "0?emergency,1") in new stack
    -- Executing [s@macro-outisbusy:3] GotoIf("SIP/707-000014a4", "0?intracompany,1") in new stack
    -- Executing [s@macro-outisbusy:4] PlayTones("SIP/707-000014a4", "congestion") in new stack
    -- Executing [s@macro-outisbusy:5] Congestion("SIP/707-000014a4", "20") in new stack
  == Spawn extension (macro-outisbusy, s, 5) exited non-zero on 'SIP/707-000014a4' in macro 'outisbusy'
  == Spawn extension (from-internal, 0797324000, 7) exited non-zero on 'SIP/707-000014a4'
    -- Executing [h@from-internal:1] Hangup("SIP/707-000014a4", "") in new stack
  == Spawn extension (from-internal, h, 1) exited non-zero on 'SIP/707-000014a4'

When "you have dialled an incorrect number comes up, this is all i get:

 -- SIP/orbtalk-out-000014b6 is making progress passing it to SIP/707-000014b5
  == Spawn extension (macro-dialout-trunk, s, 22) exited non-zero on 'SIP/707-000014b5' in macro 'dialout-trunk'
  == Spawn extension (from-internal, 0797324000, 6) exited non-zero on 'SIP/707-000014b5'
    -- Executing [h@from-internal:1] Hangup("SIP/707-000014b5", "") in new stack
  == Spawn extension (from-internal, h, 1) exited non-zero on 'SIP/707-000014b5'

How can I ensure correct message plays ALL the time, and I do not get the "All circuits are busy?" Is this to do with our provider?
I tried changing settings in "Route congestion messages", and picked "Congestion Tones" instead of "Default Message", so now Im getting a mix of either a long beep (congestion tone) or "you have dialled an incorrect number..."

 

[CoinTos]

It's your provider that is becoming conjested according to your logs, look at this line:

 -- Got SIP response 503 "503-Service Unavailable" back from myproviderIP:5060

Then reference this wiki page:
http://en.wikipedia.org/wiki/List_of_SIP_response_codes

Here's a quote from the above:

503 Service Unavailable
The server is undergoing maintenance or is temporarily overloaded and so cannot process the request. A "Retry-After" header field may specify when the client may reattempt its request.

 

[papachumba]

Thanks, thought so....
I have already informed them.