Reference12r2:Gateway/Interfaces/SIP

From innovaphone-wiki

Jump to: navigation, search
There are other versions of this article: Reference | Reference7 | Reference9 | Reference10 | Reference11r1 | Reference12r1 | Reference12r2 (this version)

Contents

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.
Transport
  • UDP: SIP signaling using UDP as transport protocol (RFC 3261).
  • TCP: SIP signaling using TCP as transport protocol (RFC 3261).
  • TLS: SIP signaling using TLS as transport protocol (RFC 3261).
  • Without registration: By default sip trunks are using with registration. Can be disabled here.
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 or 8111111e0@x.x.x.x:5080 if you need to use the IP-address and a different Port number).
Local Hostname The Local Domain for SIP Federation enables to select the TLS Certificate according to the Domain Name. On the incoming SIP calls the host part of the URI is removed if equals with the Local Domain configured here, and the user part is used as Name (H323-ID) or Number (E164).
Local Port The Local Port that differs from default port 5060 (or 5061 for SIP over TLS) can be configured here for SIP signalling.
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. (append ":<port>" if you need a different destination Port)
STUN Server The STUN servers to use. See STUN for details regarding the format.

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 Video Removes Video Capabilities from outgoing media offer.
To Header when Sending INVITE Affects only outgoing diverted calls . Called Party: If set we write CDPN into To header of outgoing INVITE (and DGPN into History-Info header). Original Called Party: If set we write the DGPN into To header of outgoing INVITE (and CDPN into Request-URI).
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) sent on outgoing calls
  • CGPN in user part of URI: Variable Identity-URI with actual calling party number
  • Fixed AOR: Fixed AOR is used as Identity-URI regardless of the actual calling party number
  • UUI: the relayed call must include user-to-user-info (UUI). This UUI is used as Identity-URI. In the UUI, the string {initiator} is replaced by the the call's diversion-info (a.k.a. leg-2-info) if available or the calling party number otherwise
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.
Advanced Allows the configuration of additional, not further documented, interop tweaks(e.g. /pai on). The same tweaks can be configured also globally(i.e. not for this SIP-Interface) at the SIP(or TSIP/SIPS)-module. Any tweaks configured at the SIP-Interface will overwrite globally configured tweaks.


More frequently used Advanced Parameters

There are some options which influence the stack behaviour to handle ambiguities in the SIP standard:

/pai on  
send identity URI in P-Asserted-Identity header. By default, it is sent in the P-Asserted-Identity header for calls from the PBX to the endpoint, in the P-Preferred-Identity header otherwise
/ppi on 
send identity URI in P-Preferred-Identity header

Other options are available which instruct the stack to use non-standard or deprecated behaviour. Note that this should only be used in rare cases. Better have the vendor of your 3rd party SIP equipment fix its stack implementation:

/send-deprecated-diversion-header on 
send call history information in the deprecated Diversion header in addition to the History-Info header
/single-audio-description 
don't send SAVP+AVP, but SAVP or AVP media description in SDP
/disable-digest-replay-check on 
disables safeguard against replay attacks
/no-authentication-info 
don't send Authentication-Info header in REGISTER response
/take-sendonly-as-inactive on 
some endpoints use sendonly instead of inactive
/take-zero-addr-for-hold  
some endpoints use a null IP address (such as in c=IN IP4 0.0.0.0) as request for hold in SDP
/send-no-historyinfo 
don't send call history information (i.e. call forward) in outgoing Invite

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 Media Properties

Personal tools