NEC SV8100 Configuration Note page 59

Configuration Note
Figure 4-35: Example of Configured SIP Message Manipulation Rules
The table displayed below includes SIP message manipulation rules, which are bound
together by commonality via the Manipulation Set ID 4, which are executed for
messages sent to the BroadCloud SIP Trunk IP Group. These rules are specifically
required to enable proper interworking between BroadCloud SIP Trunk and IP-PBX.
Refer to the User's Manual for further details concerning the full capabilities of header
manipulation.
Rule
Index
This rule applies to messages sent to the BroadCloud
SIP Trunk IP Group. This replaces the host part of the
0
SIP From Header with the value from the SIP To
Header.
This rule applies to messages sent to the BroadCloud
SIP Trunk IP Group. This replaces the host part of the
1
SIP P-Asserted-Identity Header with the value from the
SIP To Header.
This rule applies to response messages sent to the
BroadCloud SIP Trunk IP Group for Rejected Calls
2
initiated by the IP-PBX IP Group. This replaces the '502'
method type with the value '480'.
This rule is applied to forward messages sent to the
BroadCloud SIP Trunk IP Group with 00 prefix and the
3
IP-PBX IP address in the Contact initiated by the IP-
PBX. This remove the 00
Version 7.0
Rule Description
59
4. Configuring AudioCodes E-SBC
Reason for Introducing Rule
BroadCloud SIP Trunk requires
that all messages should be from
known hosts.
IP-PBX response with '502'
method type on DND and
BroadCloud SIP Trunk does not
recognize the '502' method type.
IP-PBX response with '00' in the
Contact and with the IP-PBX IP
address and BroadCloud SIP
Trunk does not recognize it.
AudioCodes Mediant E-SBC