Jump to: navigation, search

GVP MCP:sip:referxferwaitnotify

 
(7 intermediate revisions by 2 users not shown)
Line 4: Line 4:
 
|valid=Choose between: 0 or 1
 
|valid=Choose between: 0 or 1
 
|takeseffect=At start/restart
 
|takeseffect=At start/restart
|shortdesc=This parameter is applicable to REFER transfer. If this is set to Enable, LMSIP2 will wait for NOTIFY with a sipflag message with a final response after receiving a 2xx REFER response. If this is set to Disable, LMSIP will not wait for NOTIFY. After that, LMSIP2 will either be sending a BYE request or expecting a BYE request from the caller depending on the value of sip.referxferwaitbye.
+
|shortdesc=This parameter is applicable to REFER transfer.
 +
If this is set to Enable, LMSIP2 will wait for NOTIFY with
 +
a sipflag message with a final response after
 +
receiving a 2xx REFER response. If this is set to Disable,
 +
LMSIP will not wait for NOTIFY. After that, LMSIP2
 +
will either be sending a BYE request or expecting a
 +
BYE request from the caller depending on the value of
 +
sip.referxferwaitbye.
 +
 
 
}}
 
}}
 
{{DraftOption}}
 
{{DraftOption}}
 
 
 
 
  
 
{{PubExtended}}
 
{{PubExtended}}
 
 
 
  
 
{{DraftExtended}}
 
{{DraftExtended}}
 
 
 
 
  
 
{{OptionCreate
 
{{OptionCreate

Latest revision as of 15:38, June 29, 2020



View in ref guide.

Edit this option          Publish this option          Clear draft content


Published Option

referxferwaitnotify

Default Value: 1
Valid Values: Choose between: 0 or 1
Changes Take Effect: At start/restart


This parameter is applicable to REFER transfer. If this is set to Enable, LMSIP2 will wait for NOTIFY with a sipflag message with a final response after receiving a 2xx REFER response. If this is set to Disable, LMSIP will not wait for NOTIFY. After that, LMSIP2 will either be sending a BYE request or expecting a BYE request from the caller depending on the value of sip.referxferwaitbye.

Draft Option

No draft option

This page was last edited on June 29, 2020, at 15:38.
Comments or questions about this documentation? Contact us for support!