SS7 Message

SS7 Message

NewsGroups | Search | Tools
 comp.dcom.telecom.tech  Post an article  get this group's latest topics as an RSS feed add this group's latest topics to your My MSN content add this group's latest topics to your My Yahoo content  add this group's latest topics to your Google content  YahooMyWeb Yahoo!  Google Google  Windows Live Favorites Windows Live  del.icio.us del.icio.us  digg digg  Add to Netscape Netscape
Subject Author Date
SS7 Message Scott 12-21-2005
Posted by Scott on December 21, 2005, 10:20 pm
If you were  Registered and logged in, you could reply and use other advanced thread options


We recently established an Access Tandem we will call ULT. We are
processing TRS calls between an SS7 Trunk Group from a customer who can
manipulate the TNS field in the message to establish carrier of choice.
When the call is sent to ULT it is being rejected for no circuit
available. Decoding the message received form the customer we see all
the correct features such as CIC and Network Circuit ID that the local
provider is requesting.This is being presented in the 48th Octet.
HOWEVER the Local provider of this AT is stating they are not receiving
the Circuit ID. When we examine the ISUP message we only see half of
the message. I believe that this is caused by the call Originating and
Terminating to the same OPC. Does anyone have an opinion on any of
this? We are "sending" the appropriate OZZ/Circuit ID. Do we need to
reserve? Calls terminating into the same switch and TF calls work just
fine.


Posted by Al Gillis on December 23, 2005, 4:20 pm
If you were  Registered and logged in, you could reply and use other advanced thread options


Gees! What an alphabet soup message! (And no offense meant, Scott)
Remember when you could be successful in the telephone business if you knew
Battery, Ground & Payday?


> We recently established an Access Tandem we will call ULT. We are
> processing TRS calls between an SS7 Trunk Group from a customer who can
> manipulate the TNS field in the message to establish carrier of choice.
> When the call is sent to ULT it is being rejected for no circuit
> available. Decoding the message received form the customer we see all
> the correct features such as CIC and Network Circuit ID that the local
> provider is requesting.This is being presented in the 48th Octet.
> HOWEVER the Local provider of this AT is stating they are not receiving
> the Circuit ID. When we examine the ISUP message we only see half of
> the message. I believe that this is caused by the call Originating and
> Terminating to the same OPC. Does anyone have an opinion on any of
> this? We are "sending" the appropriate OZZ/Circuit ID. Do we need to
> reserve? Calls terminating into the same switch and TF calls work just
> fine.
>



Posted by on January 6, 2006, 5:55 pm
If you were  Registered and logged in, you could reply and use other advanced thread options



Scott wrote:
> We recently established an Access Tandem we will call ULT. We are
> processing TRS calls between an SS7 Trunk Group from a customer who can
> manipulate the TNS field in the message to establish carrier of choice.

Confirm that all trunks are idle. Run trunk query on the group.

> When the call is sent to ULT it is being rejected for no circuit
> available. Decoding the message received form the customer we see all
> the correct features such as CIC and Network Circuit ID that the local
> provider is requesting.This is being presented in the 48th Octet.
> HOWEVER the Local provider of this AT is stating they are not receiving
> the Circuit ID. When we examine the ISUP message we only see half of
> the message. I believe that this is caused by the call Originating and
> Terminating to the same OPC. Does anyone have an opinion on any of
> this? We are "sending" the appropriate OZZ/Circuit ID. Do we need to
> reserve? Calls terminating into the same switch and TF calls work just
> fine.

Why are you only seeing half of the message? And what message? The
Release?
The IAM?

Exactly what type of call are you making that originates and terminates
to the
same OPC? A test call? Should the AT be routing the call right back to
you?
And what do you mean by "reserve"?

What you need to do is monitor the call in both directions, trap the
messages and
post them here. Of course if you have fixed your problem, posting the
resolution
could be educational.....

Ray


Posted by Scott on January 9, 2006, 1:02 pm
If you were  Registered and logged in, you could reply and use other advanced thread options


After investigating this further we have discovered both parts of the
IAM message. The TNS field is being presented as an Optional PArameter.
Basically what we need is a way to get the DMS 250 to present the TNS
250 as an actual parameter. Currently only the CIP field is going
across.
I cannot put eh screen prints of the traps in here


Posted by on January 11, 2006, 5:59 pm
If you were  Registered and logged in, you could reply and use other advanced thread options


Well, the TNS parameter is an optional parameter and the fact that it
is
optional should not cause problems in the AT. I thought the AT is the
250?
Your end office should be presenting the IAM to the AT.

You should see the Carrier Code and the Circuit Identification Code in
the TNS
parameter. (0ZZ / 1N/N'X in the MF world). Are these values correct?
Actually, confirm that all fields of the TNS parameter are correct and
get back to us...

Ray


Similar ThreadsPosted
Answering Message on MLS-12D? July 6, 2005, 11:14 am
Audix Message Deletion March 7, 2006, 1:16 pm
New SunRocket Message Board January 17, 2007, 4:18 pm
KX-TD1232 Message Button issue January 3, 2006, 2:33 pm
Audix Command to Re-Record Message May 31, 2006, 2:33 pm
2-line; 2 message Answering machines June 25, 2006, 9:02 pm
Need some help in MGTS scripting How to send a message July 26, 2006, 12:50 am
Google talk status message help July 30, 2006, 4:32 pm
Comdial FXS and Interchange 12.0 Message Lamp Problem September 1, 2005, 7:13 pm
Merlin Legend Mail Message Lights July 13, 2007, 10:41 am

other useful resources:
The Federal Communications Commission (FCC)
Telecommunications Industry Association
Electronic and Software Security Products and Services
International Telecommunication Union

Custom CGI Perl and PHP programming by 1-Script.com

Contact Us | Privacy Policy
The site map in XML format XML site map