Reference9:Gateway/Interfaces/SIP

From innovaphone wiki
Revision as of 10:32, 26 August 2013 by Afi (talk | contribs) (→‎SIP Registration section)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
There are also other versions of this article available: Reference | Reference7 | Reference9 (this version) | Reference10 | Reference11r1 | Reference12r1 | Reference12r2 | Reference13r2

SIP Registration section

The entry fields for a SIP registration are:

Name Descriptive name for this registration.
Disable A switch to temporarily disable this interface without deleting the configuration.
Type
  • Provider: Creates a registration at a remote SIP server (of a SIP provider)
  • Open Federation: SIP/TLS interface without registration used to send and receive calls to federation partners.
  • Closed Federation: Like 'Open Federation' but even more restricted to pre-configured set of federation partners. In the 'Closed Federation' mode, the DNS queries for resolving the domain name of the federation partner are made without the Recursion Desired (RD) Flag. This means only DNS entries configured on the local DNS server are resolved, so the list of the partners for 'Closed Federation' must be maintained on the local DNS server.
AOR Address of Record: SIP-URI used to register. Enter the registration ID followed by the SIP provider domain name (for example 8111111e0@sipgate.de).
Proxy DNS name or IP address of the SIP proxy where SIP messages (REGISTER,INVITE,etc) are to be sent to. Proxy can be omitted if domain part of AOR can be used as remote signaling destination.
STUN Server The STUN server name or IP address must be configured if this device has no public IP address while the SIP server is accessible under a public IP address. The value is given by the SIP provider or administrator (for example, stun.xten.com or 64.69.76.23). You can choose any STUN server; it does not necessarily have to correspond to the one of the SIP provider.

Authorization

Username and password for authorization. Username can be omitted if equal to userpart of AOR.

SIP Interop Tweaks

Proposed Registration Interval Set in seconds, default is 120 seconds
Accept INVITE's from Anywhere If disabled, registered interfaces will reject INVITE's not coming from the SIP server with "305 Use Proxy".
Enforce Sending Complete Affects handling of "484 Address Incomplete" responses. If enabled and "484 Address Incomplete" is received, the call is cleared. If not enabled and "484 Address Incomplete" is received, the call is retained and re-initiated in case of new dialing digits.
No Early Media Ignore any SDP answer received before final connect response.
No Inband Information on Error Controls interworking of Q.931 DISC message. If this option is set, DISC message is always interworked into BYE request.
From Header when Sending INVITE Controls the local URI (From header) of outgoing calls. Applys to registered interfaces only. Fixed AOR: Fixed AOR is used as From-URI regardless of the actual calling party number. AOR with CGPN as Display: Fixed AOR is used as From-URI and calling party number is added as display string. CGPN in user part of URI: Variable From-URI with actual calling party number.
Identity Header when Sending INVITE Controls the identity header (P-Preferred-Identity, P-Asserted-Identity and Remote-Party-Id). CGPN in user part of URI: Variable From-URI with actual calling party number. Fixed AOR: Fixed AOR is used as Identity-URI regardless of the actual calling party number.
Reliability of Provisional Responses Controls the support of PRACK (RFC-3262). Supported: Supported as optional extension. Required: Required as mandatory extension. Disabled: Hide support for PRACK extension.

Media Properties

The configuration of the media properties is evaluated for calls from/to this interface to/from a physical (ISDN, analog, TEST, ...) only. If media relay is active for a call using this interface an 'exclusive' coder config is used to prohibit the use of any other coder. This 'exclusive code media-relay' config can be used to solve interop problems with other equipment which does not support media renegotiation, because with this config no media renegotiation will be performed.

For more information see Reference:Administration/Gateway/Interfaces#Coder_Preferences_section: