Bash – Setting environment variables for a service without a login shell on Debian

Read "asterisk the future of telephony" o'rellys book

it have all sip protocol nice described.

your qestion can be solved as

host=dynamic
defaultip=ip_of_other_side
deny=0.0.0.0/0.0.0.0
permit=ip_of_other_side/255.255.255.255

or

host=

on both side and no register string

http://www.voip-info.org/wiki/view/Asterisk+config+sip.conf

BASH_ENV is only going to be set via the environment, or another script that is sourced during initialization. For a non-interactive shell, it will only be trying to source additional files if that shell is also a login shell. (in which case it'll read ~/.bash_profile, ~/.bash_login, and ~/.profile...but if it was doing that, you wouldn't be experiencing an issue)

The first place to look is the environment in which the subshell is being invoked.

• An exported BASH_ENV variable will be passed through. Keep in mind that this may be buried in a sourced file.
• It can be fed in as a parameter on the same line calling the script, i.e. BASH_ENV=blah /path/to/somecommand.sh. This stands out like a sore thumb so you probably would have caught it.

If it's being set after you log in but you can't figure out where, you may need to look at what is responsible for constructing the login environment.

• All of the usual files that get sourced by a login shell. man bash for the exhaustive list.

• PAM: As freiheit suggested in the comments, check /etc/security/pam_env.conf, and any additional files that are referenced by pam_env.so. Other PAM modules could also be responsible, but if your PAM configs look identical this is probably not the case.

• sshd: It will scan the following files, in order:

  • ~/.ssh/environment (before changing to the home directory; only if PermitUserEnvironment is enabled in sshd_config)
  • ~/.ssh/rc (after changing to the home directory; always)
  • /etc/ssh/sshrc (if ~/.ssh/rc is not present)

Note: sshd will also scan for environment=value lines in the user's authorized keys file (if PermitUserEnvironment is enabled), but it is not clear from the man page where that step falls in the above sequence.