Re: Should ASP send a DUPU?
Sandy <[email protected]>
| Newsgroups | gmane.ietf.sigtran |
|---|---|
| Message-ID | <[email protected]> |
Hi, Thanks for your response. Does the corresponding SS7 primitives holds good for the scenario explained in previous mail. So on receiving INACTIVE from ASP, the SGP sends MTP- PAUSE primitive is sent if the route is based on dpc. MTP- UPU primitive is sent if the route is based on dpc and SIO. Regards, Sandeep B S On Sat, Dec 5, 2009 at 5:37 AM, Brian F. G. Bidulock <[email protected]>wrote: > Sandy, > > The SG does not send M3UA messages to SS7 Signalling Points. > > --brian > > Sandy wrote: (Fri, 04 Dec 2009 19:22:23) > > > > Sorry, the second condition as to be : > > DUPU is sent if the route is based on DPC and SIO. > > Regards, > > Sandeep B S > > > > On Fri, Dec 4, 2009 at 7:14 PM, Sandy <[1][email protected]> wrote: > > > > Hi Brain, > > > > When the user part of ASP becomes unavailable then corresponding > > INACTIVE message for that AS is sent by ASP to SGP. At SGP side on > > receiving INACTIVE message from ASP, it searches for the > > corresponding routing key of the AS and sends DUNA/DUPU to SS7 > > point code based on the following conditions. > > > > DUNA is sent if the route is based on DPC only. > > > > DAVA is sent if the route is based on DPC and SIO > > Please confirm whether my understanding is on a right path. > > Regards, > > Sandeep B S > > > > On Fri, Dec 4, 2009 at 1:25 AM, Brian F. G. Bidulock > > <[2][email protected]> wrote: > > > > Deepak, > > ASP Inactive. > > -- brian > > Deepak Gunjal wrote: > > (Thu, 03 Dec 2009 19:57:53) > > > > > Hi, > > > > > > In case if my local SCCP user at ASP become unavailable, how does my > > local ASP will notify to SG without DUPU? > > > > > > > > > -----Original Message----- > > > From: [3][email protected] > > [mailto:[4][email protected]] On Behalf Of Brian F. G. > Bidulock > > > Sent: Thursday, December 03, 2009 7:00 PM > > > To: Sandy > > > Cc: [5][email protected] > > > Subject: Re: [Sigtran] Should ASP send a DUPU? > > > > > > Sandy, > > > > > > Invalid SIO should be screened by the SG. When an AS becomes > > > unavailable at an ASP it should deactivate for the AS. DUPU > > > is not permitted in the direction from ASP to SG. > > > > > > --brian > > > > > > Sandy wrote: (Thu, 03 Dec 2009 > > 14:57:31) > > > > > > > > Hi All, > > > > We generally know that DUPU message is sent from SGP to ASP to > > > > indicate that the remote peer MTP3-user part is unavailable at > > SS7 > > > > node. > > > > What if ASP receives message with invalid SIO or if the message > > > > destined to the particular user is not available.In this case > > should > > > > ASP send a DUPU message to remote? If not what action should > > ASP take? > > > > Please explain. Thanks in advance. > > > > Regards, > > > > Sandeep B S. > > > > > > > _______________________________________________ > > > > Sigtran mailing list > > > > [6][email protected] > > > > [7]https://www.ietf.org/mailman/listinfo/sigtran > > > > > > > > > -- > > > Brian F. G. Bidulock > > > [8][email protected] > > > [9]http://www.openss7.org/ > > > _______________________________________________ > > > Sigtran mailing list > > > [10][email protected] > > > [11]https://www.ietf.org/mailman/listinfo/sigtran > > > > > > "DISCLAIMER: This message is proprietary to Aricent and is intended > > solely for the use of the individual to whom it is addressed. It may > > contain privileged or confidential information and should not be > > circulated or used for any purpose other than for what it is intended. > > If you have received this message in error, please notify the > > originator immediately. If you are not the intended recipient, you are > > notified that you are strictly prohibited from using, copying, > > altering, or disclosing the contents of this message. Aricent accepts > > no responsibility for loss or damage arising from the use of the > > information transmitted by this email including damage from virus." > > > _______________________________________________ > > > Sigtran mailing list > > > [12][email protected] > > > [13]https://www.ietf.org/mailman/listinfo/sigtran > > -- > > Brian F. G. Bidulock > > [14][email protected] > > [15]http://www.openss7.org/ > > > > References > > > > 1. mailto:[email protected] > > 2. mailto:[email protected] > > 3. mailto:[email protected] > > 4. mailto:[email protected] > > 5. mailto:[email protected] > > 6. mailto:[email protected] > > 7. https://www.ietf.org/mailman/listinfo/sigtran > > 8. mailto:[email protected] > > 9. http://www.openss7.org/ > > 10. mailto:[email protected] > > 11. https://www.ietf.org/mailman/listinfo/sigtran > > 12. mailto:[email protected] > > 13. https://www.ietf.org/mailman/listinfo/sigtran > > 14. mailto:[email protected] > > 15. http://www.openss7.org/ > > > _______________________________________________ > > Sigtran mailing list > > [email protected] > > https://www.ietf.org/mailman/listinfo/sigtran > > > -- > Brian F. G. Bidulock > [email protected] > http://www.openss7.org/ > _______________________________________________ Sigtran mailing list [email protected] https://www.ietf.org/mailman/listinfo/sigtran