60 SBC session border controllers
Accept:
application/SDP,applicatio
n/ISUP
[sipheader:accept=-(application/SDP,)$]
Remove,
starting from
the specified
text
Accept:
application/SDP,text/plain
[sipheader:accept=-(,text)!]
Replace the text
completely
[sipheader:accept=+(application/ISUP)!]
Accept:
application/SDP,text/plain
[sipheader:accept=-(SDP)+(ISUP)$]
Accept:
application/ISUP,text/plain
Replace the text
by discarding
the data at the
end
Accept:
application/SDP,text/plain
[sipheader:accept=-(SDP)+(ISUP)!]
Complex
modification
example
From:
<sip:who@host>;tag=aBc
[sipheader:from=+(DISPLAY )-
(who)+(12345)-
(>)+(;user=phone>)$+(;line=abc)]
From: DISPLAY
<sip:12345@host;user=phone
>;tag=aBc;line=abc
Example
[sipheader:Accept=disable],[sipheader:user-agent=disable]
In this example all SIP messages sent via this SIP interface will not have the fieldsAccept and user-
agent.
List of mandatory SIP message fields that cannot be modified: via, from, to, call-id, cseq, con-
tact, content-type, content-length.
4.1.3.3 SIP Users
This menu configures destinations for receiving and routing calls for SIP users who will send calls and
registrations via SBC. Up to 256 users can be created.
To create, edit or remove interfaces, use 'Objects' — 'Add an object', 'Objects' — 'Edit an object' and 'Objects'
— 'Remove an object' and the following buttons:
– «Add»;
– «Edit»;
– «Delete».
SBC Configuration –> SIP Users