RE: DRN Label Issues - Issue #2
"Haresign Lincoln" <[email protected]>
| Newsgroups | gmane.ietf.sigtran |
|---|---|
| Message-ID | <849535E338E99741B7F7413F73253EDB04E8BC57@us-nj-mail1.comverse.com> |
Brian, I would think we would send with an Error Code of Zero. I agree with you that it is the best choice. Regards, Lincoln -----Original Message----- From: Brian F. G. Bidulock [mailto:[email protected]] Sent: Wednesday, October 11, 2006 3:34 PM To: Haresign Lincoln Cc: Barry Nagelberg; [email protected] Subject: DRN Label Issues - Issue #2 Lincoln, RFC 3868 says: 4.7.3.2. SCCP Connection Oriented traffic ... If an ASP is not available, the SG discards the message. SCCP does not discard connection-oriented messages, it sends an ERR message with an Error Cause: particularly when the messae is an Inativity Test message. Discarding an Inactivity Test message will break the SCCP protocol. The choices for error cause from Q.713 (07/96) Section 3.14 are: 0 0 0 0 0 0 0 0 Local Reference Number (LRN) mismatch - unassigned destination LRN 0 0 0 0 0 0 0 1 Local Reference Number (LRN) mismatch - inconsistent source LRN 0 0 0 0 0 0 1 0 pointcode mismatch 0 0 0 0 0 0 1 1 service class mismatch 0 0 0 0 0 1 0 0 unqualified 0 0 0 0 0 1 0 1 | to | spare 1 1 1 1 1 1 1 1 | The first one looks like a good choice; however, is an very bad idea to go telling an SG what it is supposed to do with SS7 messages. It is the responsibility of the SG to maintain a correctly functioning SS7 protocol towards the SS7 network. Do you thing the message should be discarded? --brian -- Brian F. G. Bidulock [email protected] http://www.openss7.org/