Engin trunk issue

[nicdevlin]

Version Details:

Code: Select all

Asterisk 1.8.29.0-vici

CLI Output during error:

Code: Select all

[Aug 19 17:00:21] NOTICE[3321]: chan_sip.c:21268 handle_response_invite: Failed to authenticate on INVITE to '"Alpha Test Phone" <sip:0731371916@byo.engin.com.au>;tag=as429076d7'

Registration String:

Code: Select all

register => 0731371916:XXXXXX@byo.engin.com.au

Account Entry:

Code: Select all

[0731371916]
disallow=all
allow=ulaw
type=peer
insecure=invite,port
fromuser=0731371916
fromdomain=byo.engin.com.au
qualify=yes
secret=XXXXXX
host=byo.engin.com.au
dtmfmode=rfc2833
defaultexpiry=900
context=default

Globals String:

Code: Select all

ENG=SIP/0731371916

Dial Plan:

Code: Select all

exten => _8.,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _8.,n,Dial(${ENG}/${EXTEN},,To)
exten => _8.,n,Hangup

I have made the switch over to Engin for their unlimited sip trunk plan and they have specified that I need to do the following to get my inbound DIDs working.

"You will need to configure your IP-PBX to read the 'to' field in the SIP header in order to recognise which in-Dial was called and then carry the call to the corresponding handset/extension."

I dare say that I will need to add some lines to my default context to utilise this?

The trunk is connected and status is OK.

However, my main issue is whenever I try to dial out I get the Failed to authenticate on INVITE to error.

Would anyone have any ideas what I am doing wrong here? Engin has absolutely no support for their sip trunks and I have found info on google about this as well.

Thanks in advance.

[williamconley]

1) Welcome to the Party!

2) As you are obviously new here, I have some suggestions to help us all help you:

When you post, please post your entire configuration including (but not limited to) your installation method and vicidial version with build.

This IS a requirement for posting along with reading the stickies (at the top of each forum) and the manager's manual (available on EFLO.net, both free and paid versions)

You should also post: Asterisk version, telephony hardware (model number is helpful here), cluster information if you have one, and whether any other software is installed in the box. If your installation method is "from scratch" you must post your operating system and should also post the .iso version from which you installed your original operating system. If your installation is "Hosted" list the site name of the host.

If this is a "Cloud" or "Virtual" server, please note the technology involved along with the version of that techology (ie: VMware Server Version 2.0.2). If it is not, merely stating the Motherboard model # and CPU would be helpful.

Similar to This:

Vicibox X.X from .iso | Vicidial X.X.X-XXX Build XXXXXX-XXXX | Asterisk X.X.X | Single Server | No Digium/Sangoma Hardware | No Extra Software After Installation | Intel DG35EC | Core2Quad Q6600

3) Their instruction relates to routing an inbound call to a user. Your request is to authenticate for making an outbound call. The two are not related to one another.

Ask them for the "sip.conf" entries you need for successful registration and calling out. You may not need a user/password to call out at all if they have IP authentication as an option.

4) ANY carrier who uses "unlimited" will have a problem when hooked up to Vicidial. Word of Warning: Regardless of what their sales person said, there is ALWAYS a fair use clause (which is often on a sheet of paper you've never seen, but "included" by reference on a paper you DID see) that says you are not allowed to dial too many calls on their system. Do not give them more money than you can afford to LOSE and have another "pay per minute" carrier lined up and tested/working immediately.

5) Happy Hunting