Jump to: navigation, search

GVP MCP:sip:referxferwaitnotify
Line 2: Line 2:
 
|hidden=false
 
|hidden=false
 
|default=1
 
|default=1
−
|valid=
+
|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

Revision as of 20:17, November 23, 2017




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

Comments or questions about this documentation? Contact us for support!