Page 386 - Asterisk™: The Future of Telephony
P. 386
trustrpid
Specifies whether or not Asterisk should trust the value in the Remote-Party-ID
header:
trustrpid=yes|no
useragent
useragent takes as its argument a string specifying the value for the useragent field
in the SIP header. The default value is asterisk:
useragent=Asterisk PBX v1.4
usereqphone
The usereqphone option tells Asterisk to add ;user=phone to SIP URIs that contain
a valid phone number:
usereqphone
videosupport (both)
You can set videosupport to yes or no. You can turn it off on a per-peer basis if
general video support is enabled, but you can’t enable it for one peer only without
enabling it in the general section:
videosupport=yes|no
vmexten
This option sets the dialplan extension to reach the voicemailbox, and will be sent
in the Message-Account section of the MWI NOTIFY message. Set this if your SIP
device supports the Message-Account setting. This option defaults to asterisk:
vmexten=8500
SIP Channel Definitions
Now that we’ve covered the global SIP parameters, we will discuss the channel-specific
parameters. These parameters can be defined for a user, a peer, or both (as noted in
parentheses):
accountcode (both)
The account code can be defined on a per-user basis. If defined, this account code
will be assigned to a call record whenever no specific user account code is set. The
accountcode name configured will be used as the <filename>.csv in
the /var/log/asterisk/cdr-csv/ directory to store CDRs for the user/peer/friend:
accountcode=iax-username
allow and disallow (both)
Specific codecs can be allowed or disallowed, limiting codec use to those preferred
by the system designer. allow and disallow can also be defined on a per-channel
basis. Keep in mind that allow statements in the [general] section will carry over
to each of the channels, unless you reset with a disallow=all. Codec negotiation
358 | Appendix A: VoIP Channels