]> git.ipfire.org Git - thirdparty/asterisk.git/commit
res_pjsip: Add new endpoint option "suppress_moh_on_sendonly"
authorGeorge Joseph <gjoseph@sangoma.com>
Tue, 5 Nov 2024 18:30:55 +0000 (11:30 -0700)
committerGeorge Joseph <gjoseph@sangoma.com>
Wed, 13 Nov 2024 16:06:50 +0000 (16:06 +0000)
commit03ab004e2665146771214bde158805bd44028244
tree65be68ffeffa5ac788fe694f76bfbb163b798f6b
parent1c0fcd583d6695cf5f7db367b3c0be823e2ab688
res_pjsip: Add new endpoint option "suppress_moh_on_sendonly"

Normally, when one party in a call sends Asterisk an SDP with
a "sendonly" or "inactive" attribute it means "hold" and causes
Asterisk to start playing MOH back to the other party. This can be
problematic if it happens at certain times, such as in a 183
Progress message, because the MOH will replace any early media you
may be playing to the calling party. If you set this option
to "yes" on an endpoint and the endpoint receives an SDP
with "sendonly" or "inactive", Asterisk will NOT play MOH back to
the other party.

Resolves: #979

UserNote: The new "suppress_moh_on_sendonly" endpoint option
can be used to prevent playing MOH back to a caller if the remote
end sends "sendonly" or "inactive" (hold) to Asterisk in an SDP.
configs/samples/pjsip.conf.sample
contrib/ast-db-manage/config/versions/4f91fc18c979_add_suppress_moh_on_sendonly.py [new file with mode: 0644]
include/asterisk/res_pjsip.h
res/res_pjsip/pjsip_config.xml
res/res_pjsip/pjsip_configuration.c
res/res_pjsip_sdp_rtp.c