IETF Logo Mail Archive

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

Suchetha P <suchethap@yahoo.com> Fri, 30 September 2016 17:34 UTC

Return-Path: <suchethap@yahoo.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 78F2C12B1A5 for <sigtran@ietfa.amsl.com>; Fri, 30 Sep 2016 10:34:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.137
X-Spam-Level:
X-Spam-Status: No, score=-3.137 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-2.316, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yahoo.com
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 UisxurH1drpm for <sigtran@ietfa.amsl.com>; Fri, 30 Sep 2016 10:34:39 -0700 (PDT)
Received: from omp1001.mail.ne1.yahoo.com (omp1001.mail.ne1.yahoo.com [98.138.87.1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ABBF412B0A8 for <sigtran@ietf.org>; Fri, 30 Sep 2016 10:34:38 -0700 (PDT)
Received: (qmail 46439 invoked by uid 1000); 30 Sep 2016 17:34:38 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1475256877; bh=461rB+zqscs60dfG1iwDkRePGZYwV1FYPc5z9AVXr/Q=; h=Date:From:Reply-To:To:Message-ID:Subject:MIME-Version:Content-Type:References; b=gOoZiUePO2BHCJGg9+dKITq7qqyYjvUKZKLa1RIEeaHtXihKjkq8ZCheG8Ejz4wUQ9+Ybgj0rKcaAGQkOrKj8jN+NBYzstwzvKzRsjxOlTJMlfBkW1VEwtNU8mRraW+Zs8DEZ0rdRiOXvIAhC+suoOQuCcvPZxCTA1ENSc4G9vVfm3UmjyWeoaXaLLM+OsL0fJRnbTl6SRMIBVPMrhpobkhD+t3XND+9fit5w5vsC6vGAt9s7Jxth0tEtzqc/jrMJZIxF8401rPJS26kGZbCwEJoBtfL59xXY14Jp6JaUkySVst/WI0b1+KYIclqcLcmSO9TFIF6fRL/EhX22ZRKfg==
X-YMail-OSG: cXzMhPYVM1ltrD16tluMbrm5YQ061LGpSQJQGCAzBNSEtM1yPXAV9G2StiY6mk9 4ZOBmrgQDQFeN2fryQQUB2I9Om.pY_cusGXNKpJ.26iXjhKOK6lCCL1wtzGFscP9_dz43qJ27u7I xp2eQGWQcPVm8.xiQx8Mh5d4yyFou7tGWM66aIh5dxSuiWy8qbojJmCk41Ga34l9rNQNBbqyokHf rGV_iAh8OZuDis3OUKPA7IyDOwb9qoGLoUQoUy83d7Bb1SWjwJOiLJEp1Z33ZQNffl4YR4gFTaL_ DIme4vryHpXLcWypMHjwpxd00uXhBbdCN0iurfq7z_E4yfEgsU4IF36KW.A5Vm.7gECJwobhTNvs 0qXnvRB3.SNdJReeWqzsnJkeAlGS3mAFLRnGCIdHcsPJOA6bJGXP2r7_HUaM93qO7velri9Gn5UZ m6jf51D6vEESM_jkIcTfqw3E.VQSrGDIiERUNxctxoyOIXkYbb7IN7a.vvczHOfNQzgfr6.ykuX7 QWhCQ9H.M4uBx9Cy0kzJafVLZrQ--
Received: from jws10026.mail.ne1.yahoo.com by sendmailws150.mail.ne1.yahoo.com; Fri, 30 Sep 2016 17:34:35 +0000; 1475256875.651
Date: Fri, 30 Sep 2016 17:34:33 +0000
From: Suchetha P <suchethap@yahoo.com>
To: "sigtran@ietf.org" <sigtran@ietf.org>
Message-ID: <341246518.3283333.1475256874619@mail.yahoo.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----=_Part_3283332_1572259637.1475256874619"
References: <341246518.3283333.1475256874619.ref@mail.yahoo.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/sigtran/4CKRSfac0EReusl82rSg4tKoL5k>
X-Mailman-Approved-At: Sun, 02 Oct 2016 11:23:22 -0700
Subject: [Sigtran] M3UA error "No Configured AS for ASP”
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: Suchetha P <suchethap@yahoo.com>
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: Fri, 30 Sep 2016 17:34:42 -0000

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 doesn’t 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 ?

Best Regards,
Suchetha

v2.23.0 | Report a Bug | By Email