Manual Chapter :
Common Elements for SIP message routing Tasks
Applies To:
Show VersionsBIG-IP LTM
- 15.0.1, 15.0.0, 14.1.3, 14.1.2, 14.1.0
Common Elements for SIP message routing Tasks
- On the Main tab, click.The SIP session profiles list screen opens.
- On the Main tab, click.The Application Service List screen opens.
- On the Main tab, click.The Package Management LX screen opens.
- ClickImport.
- For theFile Namesetting, clickBrowseto navigate to the SIP Configuration Wizard RPM package, and then clickOpento upload the package.The SIP Configuration Wizard RPM package is namedsipConfigurationWizard-xx.x.x-x.xx.x.xxx.noarch.rpm.
- ClickUpload.The SIP Configuration Wizard RPM package uploads to the Applications Service List screen.
- ClickCreate.The new SIP Session profile screen opens.
- Click the name of a SIP application.The default iApps LX SIP application isSIP Configuration.
- In the SIP Configuration Wizard, click the General Configuration tab.The General Configuration screen opens.
- In theApplication Namefield, type a unique name for the SIP application.
- For the inbound, outbound, and wildcard virtual servers, complete the following steps.
- In theVirtual Server Namefield, type a unique name for the virtual server.A virtual server name cannot include special characters.
- In theVirtual Server IPfield, type the IP address for the virtual server.
- In theNetmaskfield, type a value for the netmask.
- In thePortfield, type a value for the ingress port for the virtual server.
- From theTypelist, select a type of virtual server:SIPorRTP (forward).RTP (forward)uses fastL4 functionality and requires no pool.
- From theClient Protocollist, select a client-side protocol:UDPorTCP.
- In theEgress Portfield, type the egress port for the virtual server.
- From theDestinationlist, select a destination:DestinationDescriptionPoolLoad balances traffic across pool members.When configuring a SIP ALG, do not configure a Port Block Allocation (PBA) translation LSN pool with a zombie timeout. Configuring a SIP ALG with an LSN pool that uses PBA mode with a zombie timeout can stop media translations.Route by URIRoutes messages based on the URI (forwards messages to the IP address of the domain SIP proxy server associated with the Request-URI) in the SIP header. Resolves Name Authority Pointer (NAPTR) resource records.ForwardFor a wildcard virtual server using RTP, routes messages using the Transport Destination IP Address of the message. No pool is required.
- ClickMore Options.
- In theVlan Listlist, select a VLAN for the virtual server, for example, internal, external, or HA.
- For a Route by URI destination, in the DNS Pool Members area, type an IP address and port number.You cannot configure a wildcard DNS pool member.
- Click the plus (+) button to add another DNS pool member.You must configure a DNS pool member IP address and port number before you can add another DNS pool member.
- Select theSession Persistencecheck box to enable session persistence.
- Select theInsert Via Headercheck box to insert a top Via Header at the egress side of the flow, after the SIP_REQUEST_SEND event.
- Select theHonor Via Headercheck box to honor a Via header that was inserted by a system other than the BIG-IP system.
- Select theInsert Record-Route Headercheck box to insert a record-route header, that is, the local-IP address and port of the flow the system uses to forward the message.
- Select theHonor Route Headercheck box to honor a Route header that was inserted by a system other than the BIG-IP system.
- From theSNATlist, select the one of the options:
- none.
- automap.
- snatpool.
- In the IP address field, type an IP address.
- Click the plus (+) button to add an IP address, as necessary.
- For a Pool destination, in the Destination Pool Members area, type an IP address and port number.You cannot configure a wildcard destination pool member.
- Click the plus (+) button to add another destination pool member.You must configure a destination pool member IP address and port number before you can add another destination pool member.
- ClickAdd Applicationto configure an additional SIP application, as necessary.
- In the SIP Configuration Wizard, click the Transformation tab.The Transformation screen opens.
- On the Transformation tab, click the Templates tab.The Templates screen opens.
- ClickAdd Template.
- In thetemplatexfield, type a name for the template.
- ClickAddto open Conditions and Actions fields and controls.The Conditions and Actions fields and controls open.
- In the Conditions areas, from theHeaderlist, select a header.
- From theExpressionlist, select an expression.
- In theValuefield, type a value.
- To configure an additional header, click the plus (+) button.
- In the Actions area, from theOperationlist, select an operation.
- From theHeaderlist, select a header.
- In theValuefield, type a value.
- To configure an additional operation, click the plus (+) button.
- ClickMore Options.
- In theDescriptionfield, type a description for the template.
- ClickAddto configure additional Conditions and Actions, as necessary.
- On the Transformation tab, click the Transformations tab.The Transformations screen opens.
- ClickAdd Templateto configure an additional SIP template, as necessary.
- On the Transformation tab, click the Transformation tab.The Transformation screen opens.
- ClickAdd Application.
- If multiple applications are configured, select an application name from the application list.
- ClickAdd.
- From theVirtual Serverlist, select a virtual server.
- In theSelect Template(s)field, select one or more templates to assign to the virtual server.
- Select the check box for each configured virtual server that you want to enable.
- ClickEnable.
- In the SIP Configuration Wizard, click the Logging tab.The Logging screen opens.
- In the Messages to Log area, select the check box for each request to log.Select theAll Requestscheck box to log all of the requests in the requests list.
- In the Messages to Log area, select the check box for each response to log.Select theAll Responsescheck box to log all of the responses in the responses list.
- In theApply logging to following Virtual Serverssetting, click the arrow to select the virtual servers to which you want to apply logging.
- In the Headers to log area, select the headers to log.Select theLog all Headerscheck box to log all headers in the headers list.
- To log additional headers excluded from the Headers to log area, in the Custom Headers area, click the arrow in theSelect Headersfield, and then click each header that you want to log.
- In the Log Destination area, click the arrow to select a log destination.
- In the SIP Configuration Wizard, click the Headers tab.The Headers screen opens.
- To create a header, either:
- ClickAdd, and type the header value in the field.
- Select the check box for a header, clickDuplicate, and modify the copied header value.
- To modify a header, type a modified header value in the applicable header field.
- To delete a header, select the check box for the header, and clickDelete.
- On the Main tab, click.The SIP Session profiles list screen opens.
- From theParent Profilelist, selectsipsession-alg.The SIP Session profile screen refreshes, showing default SIP session ALG profile settings.
- ClickCreate.The New SIP Session Profile screen opens.
- In theNamefield, type a unique name for the SIP session profile.
- Select theCustomcheck box.
- In theMaximum Message Size (bytes)field, type the maximum SIP message size that the system accepts.
- In theMaximum Message Header Countfield, type the maximum number of header fields that the system allows in a SIP message.
- In theMaximum Message Header Size (bytes)field, type the maximum size in bytes that the system allows for a SIP message header.
- Select theGenerate Response on Failurecheck box to send failure response messages when the system drops a SIP request.
- Select theMaximum Forwards Checkcheck box to check themax-forwardheader field.
- Clear theMaximum Forwards Checkcheck box.
- Select theHonor Viacheck box to honor a Via header that was inserted by a system other than the BIG-IP system.
- Clear theHonor Viacheck box.
- Select theInsert Via Headercheck box to insert a top Via Header at the egress side of the flow, after theSIP_REQUEST_SENDevent.
- Clear theInsert Via Headercheck box.
- Select theDo Not Connect Backcheck box to establish a connection to a request originator, to deliver a response when the connection no longer exists.
- In theCustom Viafield, type a value to use, when theInsert Via Headercheck box is selected, in thesent-byfield of the Via header.
- Select theLoop Detectioncheck box to check for request loops.If you select theLoop Detectioncheck box, you must also select theInsert Via Headercheck box, and provide a value for theCustom Viasetting.
- Select theInsert Record Route Headercheck box to insert arecord-routeheader, specifically the local IP address and port of the flow that the system uses to forward the message.
- Select theSIP Firewallcheck box to enable the SIP Security settings, configured in the DoS Profile of Advanced Firewall Manager (AFM), to apply to the virtual servers that use this profile.
- In the Persistence area, select theCustomcheck box.
- From thePersist Keylist, select a persistence key to use. The options are:Call-IDPersistence is based on the value in the Call-ID header field in the SIP message.Src-AddrPersistence is based on a custom key specified in an iRule.CustomPersistence is based on the originating IP Address in the SIP message.
- From thePersist Typelist, select the type of the persistence that the system uses. The options are:SessionThe system uses the SIP session database to store persistence data. No hash is applied.NonePersistence is disabled.
- In thePersist Timeout (seconds)field, type the number of seconds that a persistence entry lasts.
- On the menu bar, clickTransport Config.The New Transport Config screen opens.
- ClickCreate.
- In theNamefield, type a unique name for the transport config.
- For theProfilessetting, select a profile from theAvailablelist, and move it to theSelectedlist.
- For theProfilessetting, move both a transport protocol profile (TCP, UDP, or SCTP) and a SIP session profile from theAvailablelist to theSelectedlist.You can associate only one protocol profile and one SIP session profile with each transport config.
- For theiRulessetting, select an iRule from theAvailablelist, and move it to theSelectedlist.
- In theSource Portfield, type the number of the port this transport config uses to connect to the servers on your network.
- From theSource Address Translationlist, select an option to define how this transport config implements selective and intelligent source address translation. The default isNone.OptionDescriptionAuto MapThe system uses the self IP addresses of BIG-IP devices as the translation addresses.SNATThe system uses the specified SNAT pool for source address translation.NoneThe system does not translate source addresses.
- On the menu bar, clickPeers.The Peers list screen opens.
- ClickCreate.The New Peers screen opens.
- In theNamefield, type a unique name for the peer.
- In theDescriptionfield, type a description of the peer.
- From theConnection Modelist, specify how connections are limited for this peer. The options are:OptionDescriptionPer BladeThe number of connections to this peer is per blade on a VIPRION system.Per PeerThe number of connections to this peer is per peer.Per TMMThe number of connections to this peer is per TMM on the BIG-IP system.Per ClientThe number of connections to a remote host is per client connection.
- From thePoollist, select the pool of servers to which the system load balances SIP messages.If you configure only one peer on this BIG-IP system, ensure that you select a pool with only one member.
- From theTransport Configlist, select the transport config that defines how the BIG-IP system communicates with the servers on your network.
- In theNumber of Connectionsfield, type the number of allowed connections between the BIG-IP system and the servers in the selected pool.
- In theRatiofield, type the ratio assigned to this peer for use within a static route.
- On the menu bar, clickStatic Routes.The Static Routes list screen opens.
- ClickCreate.The New Route screen opens.
- In theNamefield, type a unique name for the static route.
- In theRequest URIfield, type the value found in the request-uri of a SIP message that the system matches when routing a message.
- In theFrom URIfield, type the value found in theFromfield of a SIP message that the system matches when routing a message.
- In theTo URIfield, type the value found in theTofield of a SIP message that the system matches when routing a message.
- From theVirtual Serverlist, select the virtual server from which the system receives client requests for this static route.If you do not select a virtual server, the system uses this static route to route SIP messages originating from any client.
- From thePeer Selection Modefield, select how the system selects the Peer to route a SIP message to:OptionDescriptionRatioPeer selection is based on the ratio that is set for each peer in theSelectedlist.SequentialPeer selection is based on the order of the peers in theSelectedlist.
- For thePeerssetting, move the peers that define the servers to which the system load balances SIP messages from theAvailablelist to theSelectedlist.
- On the Main tab, click.The SIP Router profiles list screen opens.
- From theParent Profilelist, selectsiprouter-alg.The SIP Router profile screen refreshes, showing default SIP router ALG profile settings, including theOperation Modeset toApplication Level Gateway.
- On the menu bar, clickRouter Profiles.The Router Profiles list screen opens.
- ClickCreate.The New Router Profiles screen opens.
- In theNamefield, type a unique name for the router profile.
- In the Settings area, select theCustomcheck box.
- From theOperation Modelist, selectLoad Balancing.
- From theOperation Modelist, selectApplication Level Gateway.
- To use connection mirroring, configure theTraffic Groupsetting.
- Clear theInherit traffic group from current partition / pathcheck box.
- From the list, select a traffic group, such as,traffic-group-1.
Changing traffic groups, with Connection Mirroring enabled, drops all mirrored connections and loses all persistence data. If you change traffic groups, mirroring must restart.The traffic group for the virtual address and mirrored attribute are overwritten by the attached router profile. - Select theConnection Mirroringcheck box.For connection mirroring to properly function, this device must be a member of a device group.
- In theMirrored Message Sweeper Intervalfield, type the milliseconds for the frequency of the mirrored message sweeper.
- In the Session Timeout (seconds) area, select theCustomcheck box.
- In theTransaction Timeoutfield, type the maximum number of seconds the system allows for a transaction, that is, the time between a request and response.
- In theMaximum Session Timeoutfield, type the maximum duration (in seconds) that a call remains active.
- In theDialog Establishment Timeoutfield, type a value for the INVITE transaction timeout.
- In the Media Proxy area, select theCustomcheck box.
- In theMaximum Media Sessionsfield, type the maximum number of media sessions allowed per call.
- In theMedia Inactivity Timeout (seconds)field, type the maximum duration (in seconds) that a media flow is active with no RTP packets.
- In the Registration area, select theCustomcheck box.
- In theMaximum Registrationsfield, type the maximum number of registrations allowed.
- In theMaximum Registrations Per Subscriberfield, type the maximum number of registrations per subscriber.
- In theConcurrent Sessions Per Subscriberfield, type the maximum number of concurrent outgoing calls allowed per subscriber.
- In theRegistrations Timeout (seconds)field, type the maximum duration (in seconds) that a registration entry remains active.
- Clear theNon Register Subscriber Calloutcheck box to prevent non-registered subscribers from making calls without a prior REGISTER message.
- In the Log Settings area, select theCustomcheck box.
- From theLog Publisherlist, select the log publisher that the BIG-IP system uses to send log messages to a specified destination.If you configure a log publisher, you must also configure a Logging Profile.If you configure a log publisher to use multiple logging destinations, then, by default, all logging destinations must be available in order to log to each destination. Unless all logging destinations are available, no logging can occur. If you want to log to the available logging destinations when one or more destinations become unavailable, you must set thelogpublisher.atomicdb variable tofalse.
- From theLogging Profilelist, select the logging profile that the BIG-IP system uses to configure logging options for various ALG events.If you configure a Logging Profile, you must also configure a Log Publisher.
- On the Main tab, click.The Virtual Server List screen opens.
- ClickCreate.The New Virtual Server screen opens.
- In theNamefield, type a unique name for the virtual server.
- In theDescriptionfield, type a description for the virtual server.
- From theTypelist, selectMessage Routing.
- From theConfigurationlist, selectAdvanced.
- From theApplication Protocollist, selectSIP.
- From theSession Profilelist, select a SIP session ALG profile.
- From theRouter Profilelist, select a SIP router ALG profile.
- From theSource Address Translationlist, selectLSN.
- From theLSN Poollist, select an LSN pool.
- ClickFinished.