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

"Brian F. G. Bidulock" <bidulock@openss7.com> Mon, 03 October 2016 17:48 UTC

Return-Path: <bidulock@openss7.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 C329B129447 for <sigtran@ietfa.amsl.com>; Mon, 3 Oct 2016 10:48:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.196
X-Spam-Level:
X-Spam-Status: No, score=-7.196 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-2.996] autolearn=ham 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 7RPx7tZLTXBo for <sigtran@ietfa.amsl.com>; Mon, 3 Oct 2016 10:48:41 -0700 (PDT)
Received: from gw.openss7.com (gw.openss7.com [142.59.210.7]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2CB7B129443 for <sigtran@ietf.org>; Mon, 3 Oct 2016 10:48:39 -0700 (PDT)
Received: from wilbur.pigworks.openss7.net (ns5.evil.openss7.net [192.168.9.5]) by gw.openss7.com (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id u93HmcvQ003753; Mon, 3 Oct 2016 11:48:38 -0600
Received: from wilbur.pigworks.openss7.net (localhost [127.0.0.1]) by wilbur.pigworks.openss7.net (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id u9243uNQ010064; Sat, 1 Oct 2016 22:03:56 -0600
Received: (from brian@localhost) by wilbur.pigworks.openss7.net (8.14.3/8.14.3/Submit) id u9243uBV010063; Sat, 1 Oct 2016 22:03:56 -0600
Date: Sat, 01 Oct 2016 22:03:56 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.com>
To: Suchetha P <suchethap@yahoo.com>
Message-ID: <20161002040356.GA9944@openss7.com>
Mail-Followup-To: Suchetha P <suchethap@yahoo.com>, sigtran@ietf.org
References: <559085221.3494300.1475301585181.ref@mail.yahoo.com> <559085221.3494300.1475301585181@mail.yahoo.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <559085221.3494300.1475301585181@mail.yahoo.com>
Organization: http://www.openss7.com/
Dsn-Notification-To: <bidulock@openss7.com>
X-Spam-To: <blockme@openss7.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
Archived-At: <https://mailarchive.ietf.org/arch/msg/sigtran/6kfqMIKJTpajizvUDz-g0zMprG8>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] M3UA error "No Configured AS for ASP”
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: bidulock@openss7.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: Mon, 03 Oct 2016 17:48:43 -0000

Suchetha,

Please see comments inline.

Suchetha P wrote:                        (Sat, 01 Oct 2016 05:59:45)
> 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?

No, definitely not.

> Is the error being thrown for no routing context in the ASP AC message?

Yes, the error is only returned when no RC in ASPAC and no default RC
is configured for the ASP at the SG.

> Best Regards,
> Suchetha
> 
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www.ietf.org/mailman/listinfo/sigtran

-- 
Brian F. G. Bidulock
bidulock@openss7.com
http://www.openss7.com/