3 beeps on out going calls

[Olan263]

When we anyone tries to make an out going call we get 3 beeps and a message saying waiting for line then the calls connects. Has anyone had this issue and if so how did you fix it?

 

[dwill02]

Check your short codes and ARS routing. It sounds like outbound calls are hitting an ARS table that have trunks Out of service, then the call is failing over to another working trunk?

 

[Olan263]

I've checked and everything looks correct, I was trying to set up a block list and deleted all my changes and its still happening

 

[IPOLackey]

This is an ARS issue. Run monitor with default filters, make a test call then follow the targeting for the call.

If you can't get your head around the trace then post it here (Just need the few lines around where it says "ARS Found")

 

[dwill02]

Also check Outgoing Group ID for your trunks. For example, if you have a PRI that is outgoing group 0, but you also have analog trunks configured as outgoing group 0. Something similar to this could be causing the issue.

 

[IPGuru]

If it has only just started happening have the relavent lines checked


Do things on the cheap & it will cost you dear

 

[Olan263]

Here is the logs

 

[snowman50]

You should have said it was SIP lines at the start.

 

[IPOLackey]

Sorry I didn't get back to this yesterday.

I've looked at the trace and there are no CMARS lines to look at. Did you default the filters? Can you re-run and ensure that the CALL : Targeting and ARS filters are checked, then make a test call and provide the number dialled so I can follow the callflow?

Thanks,

 

[Olan263]

I did default the filters targeting ARS. I did a few test calls yesterday and phone numbers ended in 1380 at 10:19 am, 4569 at 10:20 am and 6879 at 10:21.

 

[IPOLackey]

Ah. The trace is only from 10.33 till 10.34...

 

[Olan263]

I will post more trace

 

[Olan263]

more

 

[IPOLackey]

Ermm....

UNICODE-UTF8
default

isn't a lot to go on there.

 

[Olan263]

trace

 

[Olan263]

I'm still learning this new voip system we just switched to it a month ago. I had crash course training on this so please bare with me.

 

[sizbut]

Maybe a lot quicker to post the config rather than traces. Save it as a file, open offline and excise anything sensitive (customer names, external IP addresses and then share). I suspect with a view of shortcode-ARS-lines the glitch will stand out.

Stuck in a never ending cycle of file copying.

 

[sizbut]

... also it may be easier to capture the events using System Status (SSA) and play them back. Tends to be less cryptic than System Monitor.

Stuck in a never ending cycle of file copying.

 

[Olan263]

After being on a call with avaya and the help from everyone here we found we out our sbc was down and we are on the secondary connection. The server is fired and trying to get the back up going is creating more headaches. Thx for all the help everyone.
If any one has any training videos or documents that would be great. Thanks again

 

[derfloh]

What training are you looking for?

Need some help with IP Office?

https://www.fwilke.com/home

CLI based cale blocking:

https://blog.fwilke.com/ip-office-block-calls-from-specific-cli/

SCN fallback over PSTN:

https://blog.fwilke.com/ip-office-scn-fallback/