A message was rejected by the SD.
The status code and reason given in
parenthesis will change based on
the type of malformation. Examples
given here include:
An INVITE received from a
forbidden endpoint. In this case,
allow-anonymous on the SIP
interface was set to agents-only, and
the INVITE was not from an agent.
An INVITE had a Max-Forwards
parameter that had decremented to
zero, and the SBC could not
forward it further
Four examples of malformed
messages that were generated from
a Protos attack (too large, missing
header, bad request URI,
unsupported URI).
Apr 1 11:26:27.603 sipd@CSE-4500-6: IDS[64]
[IDS_LOG]INVITE from source 172.41.0.3:5060 to
dest 172.41.0.2:5060[UDP] realm=access;
From=sipp
status=403 (Forbidden)
OR
Nov 28 19:52:40 172.41.3.41 CSE-4500-6
sipd[2dcc32a4] ERROR [IDS_LOG]INVITE from
source 192.168.66.54:5060 to dest
192.168.66.2:5060[UDP] realm=access;
status=483 (Too Many Hops); error=invalid
message
OR
IDS_LOG]INVITE from source 192.168.222.1:5060
to dest 192.168.222.50:5060[UDP] realm=access;
target=sip <omitted message> rejected!;
status=513 (Message Too Big)
OR
May 22 14:40:39.033 sipd@: IDS[64]
[IDS_LOG]INVITE from source 192.168.222.1:5060
to dest 192.168.222.50:5060[UDP] realm=access;
status=400 (Invalid/Missing Via Header)
OR
May 22 15:08:02.015 sipd@: IDS[64]
[IDS_LOG]INVITE from source 192.168.222.1:5060
to dest 192.168.222.50:5060[UDP] realm=access;
rejected!; status=400 (Bad Request-URI)
OR
May 22 15:08:01.088 sipd@: IDS[64]
[IDS_LOG]INVITE from source 192.168.222.1:5060
to dest 192.168.222.50:5060[UDP] realm=access;
target=aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa:noone@
sip.no.invalid rejected!; status=416
(Unsupported URI Scheme)
Kommentare zu diesen Handbüchern