Strange Asterisk trunk behaviour

[Eugene]

Hello,

I've stumbled on very strange inbound sip trunk behaviour. There are some phones and sip trunk configured in carriers. sip-vicidial.conf reads:

Code: Select all

; Cisco Call Manager 1
[CiscoCallManager1]
type=friend
host=10.X.X.X
context=trunkinbound
canreinvite=no
dtmfmode=inband
disallow=all
allow=alaw
allow=ulaw
deny=0.0.0.0/0
permit=10.X.X.X./32
incominglimit=0
insecure=invite,port

[6150]
username=6150
secret=XXXXX
accountcode=6150
callerid="6150" <6150>
mailbox=6150
context=default
type=friend
host=dynamic

There is test extension included in both trunkinbound and default contexts in extensions.conf

Code: Select all

; ***** Echo test *****
exten => 6199,1,Wait(1)
exten => 6199,n,Answer()
exten => 6199,n,Playback(demo-echotest)
exten => 6199,n,Echo()
exten => 6199,n,Hangup()

When I changed default asterisk language in sip.conf phone happily accepted it and test call played proper prompts, while incoming calls from trunk still played default prompts. When I tried to change trunk context to default one, the conf file was properly regenerated, but the trunk continued to place inbound calls in trunkinbound context! Changing context in sip.conf rerouted calls to the default context, but did not solve language issue.

I.e. there are two problems:
-- trunk does not accept language change, nor through sip.conf, nor through vicidial carrier configuration interface (sip-vicidial.conf)
-- trunk does not accept context change through vicidial carrier configuration interface (sip-vicidial.conf)

Could you advise and/or comment, please?

Thank you!
Gene

[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 (7.X.X?) and vicidial version with build (VERSION: 2.X-XXXx ... 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 "manual/from scratch" you must post your operating system with version (and the .iso version from which you installed your original operating system) plus a link to the installation instructions you used. 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) In case you didn't quite catch that: The single most important bit you can place in your post is the Vicidial Version with Build. While the Installer version is unquestionably useful (Vicibox), that installer can be used to install almost any version of Vicidial. So always include (at the very least) your Vicidial Version with Build.

4) Since you are also posting asterisk configuration file snippets, listing your Asterisk version would probably be a Very Good Thing, yes?

5) If you have edited your "sip.conf", please revert to the original file. It should never be edited except for the "externip" value. Anything you are tempted to put into sip.conf belongs in a carrier "Account Entry" field with its own [context] for each carrier (more than one context can actually be used per carrier if you find a need, such as [carrierx-in] and [carrierx-out]).

6) If you have edited your "extensions.conf", please revert to the original file. It should never be edited. Anything you are tempted to put into extensions.conf belongs in a carrier "Dialplan Entry" field without a [context] entry (as these are all placed in [default] and if you put a context in, all carrier dialplan entries that generate after this one will be broken, along with this one). If you feel the need to put something in a context other than [default] (special dialplan entry!) you can check the manual for proper use of "Admin->System Settings->Custom Dialplan Entry". But be very careful.

7) If you are saying that the values in the "-vicidial.conf" versions of these files no longer update, it is likely due to your changing the IP address of the server after building it. This can be resolved by reading the Splash Screen any time you log in to Vicidial via ssh or the console. There is a very specific blurb about what to do if you change the IP address. It's there for a purpose: Everyone eventually needs it! LOL

Happy Hunting

[Eugene]

Thank you for your answer!

You are correct: Asterisk version is missed in the post. It is 11.22.0-vici.
The rest of required information has been posted in the message signature already.
Yes, I have studied both free and hi-res manuals.

No, I did not change IP address and *-vicidial.conf files are regenerated correctly.

I believe it is Asterisk-specific problem not to accept default Asterisk-wide language change and do not accept language override on incoming trunk configuration.

And even more strange problem to me is that Asterisk does not accept default context override on incoming trunk configuration.

Regards,
Gene