IETF Logo Mail Archive

Re: [Sigtran] M3UA error "No Configured AS for ASP”

David Laight <David.Laight@ACULAB.COM> Mon, 03 October 2016 09:17 UTC

Return-Path: <David.Laight@ACULAB.COM>
X-Original-To: sigtran@ietfa.amsl.com
Delivered-To: sigtran@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 253A312B204 for <sigtran@ietfa.amsl.com>; Mon, 3 Oct 2016 02:17:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.955
X-Spam-Level:
X-Spam-Status: No, score=-1.955 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qScvd2TPVNvx for <sigtran@ietfa.amsl.com>; Mon, 3 Oct 2016 02:17:34 -0700 (PDT)
Received: from smtp-out4.electric.net (smtp-out4.electric.net [192.162.216.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0C95912B1F5 for <sigtran@ietf.org>; Mon, 3 Oct 2016 02:17:33 -0700 (PDT)
Received: from 1bqzNL-0004fq-Ug by out4a.electric.net with emc1-ok (Exim 4.87) (envelope-from <David.Laight@ACULAB.COM>) id 1bqzNL-0004iN-WE; Mon, 03 Oct 2016 02:17:31 -0700
Received: by emcmailer; Mon, 03 Oct 2016 02:17:31 -0700
Received: from [213.249.233.130] (helo=AcuExch.aculab.com) by out4a.electric.net with esmtps (TLSv1:AES128-SHA:128) (Exim 4.87) (envelope-from <David.Laight@ACULAB.COM>) id 1bqzNL-0004fq-Ug; Mon, 03 Oct 2016 02:17:31 -0700
Received: from ACUEXCH.Aculab.com ([::1]) by AcuExch.aculab.com ([::1]) with mapi id 14.03.0123.003; Mon, 3 Oct 2016 10:15:15 +0100
From: David Laight <David.Laight@ACULAB.COM>
To: 'Suchetha P' <suchethap@yahoo.com>, "sigtran@ietf.org" <sigtran@ietf.org>
Thread-Topic: [Sigtran] M3UA error "No Configured AS for ASP”
Thread-Index: AQHSHNnO3wyhTlKASEmEYbWr1ySSdKCWc3Dw
Date: Mon, 03 Oct 2016 09:15:14 +0000
Message-ID: <063D6719AE5E284EB5DD2968C1650D6DB01DEDBE@AcuExch.aculab.com>
References: <341246518.3283333.1475256874619.ref@mail.yahoo.com> <341246518.3283333.1475256874619@mail.yahoo.com>
In-Reply-To: <341246518.3283333.1475256874619@mail.yahoo.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.202.99.200]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Outbound-IP: 213.249.233.130
X-Env-From: David.Laight@ACULAB.COM
X-Proto: esmtps
X-Revdns:
X-HELO: AcuExch.aculab.com
X-TLS: TLSv1:AES128-SHA:128
X-Authenticated_ID:
X-PolicySMART: 3396946, 3397078
X-Virus-Status: Scanned by VirusSMART (c)
X-Virus-Status: Scanned by VirusSMART (s)
Archived-At: <https://mailarchive.ietf.org/arch/msg/sigtran/Tx9oumm1ZOox-DgIlrrPwPTAtLA>
Subject: Re: [Sigtran] M3UA error "No Configured AS for ASP”
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Signaling Transport <sigtran.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sigtran>, <mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sigtran/>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sigtran>, <mailto:sigtran-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Oct 2016 09:17:35 -0000

From: Suchetha P
> Sent: 30 September 2016 18:35
> Hi,
> 
> IuPS interface(Packet switching/data interface) between the nodes  Signalling Gateway and SGSN is down
> after the Trillium SIGTRAN Stack Upgrade.
> This is because of the M3UA error "No o Configured AS for ASP.
> 
> 1)    The asExhangeMode is set to singleExchange at Signalling Gateway while at SGSN side
> asExhangeMode is set to doubleExchange.
> 2)    Both the nodes are sending ASPUP & ASPUPACK. SG(Signalling Gateway) then sends ASPAC and SGSN
> responds with ASPAC Ack. SGSN sends ASPAC but SG doesnt respond with ASPAC Ack and instead it sends
> error message  No Configured AS for ASP.
> 
> We need to investigate why SG is not responding with ASPAC Ack message and instead sending Error
> message towards  SGSN.
> Can this be a configuration issue ?Or a bug ?The same configuration was working before the Trillium
> upgrade.
> Is it proper to have one node in single exchange mode while the other as double exchange ?
> Is the error being thrown for no routing context in the ASP AC message ?

You need to ask your software supplier.

	David

v2.23.0 | Report a Bug | By Email