Disclaimer: These archives are mirrored from smsforum.net in 2007 before the forum got closed. Please only part of the forum is available here.
For any clarifications regarding these archives you can contact us at http://www.telecomspace.com/contact.

      TELECOMSPACE HOME PAGE         TELECOM DISCUSSION FORUM          CONTACT

+  SMS Forum Online Discussion
|-+  SMS Technologies
| |-+  ANSI-41 (CDMA & TDMA) Related (Moderator: SMS Forum Support)
| | |-+  SMSRequest Failes
« previous next »
Pages: [1] Go Down Print
Author Topic: SMSRequest Failes  (Read 2411 times)
man_shandy
Full Member
***
Offline Offline

Posts: 20


« on: April 24, 2006, 06:22:54 UTC »

Hi this is manish.....
                              can anyone tell that how can I send a sms request to the HLR.
Right now I am sending the sms-request to MSC(STP) which routs the message to HLR. but in the response I got error (0x86) Opearation Not Supported.

I also tried with direct link to HLR. but it does not give any response and timed out occurs. I need that urgently because I want SMS-ADDRESS and MIN for particular MDN.

                          Please let me know if anyone knows the solution.
Logged
shad
Sr. Member
****
Offline Offline

Posts: 54


« Reply #1 on: April 24, 2006, 16:45:32 UTC »

Hi Manish

Any chance you can post a trace?

Your HLR should handle this - are you sure it supports IS-841 (MDN in SMSREQ instead of MIN)? Are you addressing the correct HLR SSN?

:-)
Shad
Logged
man_shandy
Full Member
***
Offline Offline

Posts: 20


« Reply #2 on: May 16, 2006, 08:28:32 UTC »

hi shad,
             I have some dump for sms request.

S7L:I0000 T 00000000 M tc7b0 i0000 f2d d25 s00 p
   05                SMS Request 
     0e0101
     32090000210a4151005457
     210101
   00

But I didnt get any response for that.

Logged
itsnomihere
Sr. Member
****
Offline Offline

Posts: 44


« Reply #3 on: May 16, 2006, 10:09:34 UTC »

I think you should use the point code of your STP(MSC) and GT Address of HLR
and also route on GT
Are you using intel SS7 card?
if yes you may want to send the complete dump or run time configuration file for SCCP

Logged
itsnomihere
Sr. Member
****
Offline Offline

Posts: 44


« Reply #4 on: May 16, 2006, 10:12:29 UTC »

you may also want to use MIN of destination mdn in SMS Request message
Logged
man_shandy
Full Member
***
Offline Offline

Posts: 20


« Reply #5 on: May 16, 2006, 12:18:51 UTC »

no there is no GT based routing in our case. the routing is based on DPC+SSN.
and I have seperate link from my smsc to hlr and I am sending the sms request to HLR directly, though it is doubtfull. but our operator asked to do it in this manner only. I am sending SMDPP to MSC point code that is working fine. but problem is in sms request. and I want sms request working because in case of roaming I need SMS-Address.
Logged
shad
Sr. Member
****
Offline Offline

Posts: 54


« Reply #6 on: May 16, 2006, 18:45:08 UTC »

S7L:I0000 T 00000000 M tc7b0 i0000 f2d d25 s00 p
   05                SMS Request 
     0e0101
     32090000210a4151005457
     210101
   00

Great. You helpfully post a trace, and now I can't understand it  Undecided

What layer is the trace from? It doesn't look exactly like I would expect for ANSI-41: "090000210a4151005457" looks like the MDN for 1415004575 (with perhaps a Type of Number set incorrectly?), but the parameter ID for MDN is 9f 5d, not 32.
ServiceIndicator and SMS_NotificationIndicator can have a length of 1 and a value of 1, but  neither have an ID of 0e or 21!

But anyway, if the HLR does not respond at all, it's more likely that the problem is in a lower layer than ANSI-41

-shad
Logged
man_shandy
Full Member
***
Offline Offline

Posts: 20


« Reply #7 on: May 18, 2006, 07:37:22 UTC »

S7L:I0000 T 00000000 M tc7b0 i0000 f2d d25 s00 p
   05                SMS Request 
     0e0101
     32090000210a4151005457
     210101
   00

Great. You helpfully post a trace, and now I can't understand it  Undecided

What layer is the trace from? It doesn't look exactly like I would expect for ANSI-41: "090000210a4151005457" looks like the MDN for 1415004575 (with perhaps a Type of Number set incorrectly?), but the parameter ID for MDN is 9f 5d, not 32.
ServiceIndicator and SMS_NotificationIndicator can have a length of 1 and a value of 1, but  neither have an ID of 0e or 21!

But anyway, if the HLR does not respond at all, it's more likely that the problem is in a lower layer than ANSI-41

-shad



Hi Shad,
             I am attaching the detailed traces of sms request and it's response. In request m sending MIN and expecting SMS-Address in response, at least it should work coz m not sending MDN for getting MIN. but it is also not working.

SMS -Request Trace:

+---------+---------------------------------------------+------------------------------------+
|BITMASK  |ID Name                                      |Comment or Value                    |
+---------+---------------------------------------------+------------------------------------+
|1:B (Tx):1  MTP-L2  MSU  SCCP  UDT  IS41  QRYP                                              |
|MTP Level 2 (MTP-L2)  MSU (= Message Signal Unit)                                           |
|Message Signal Unit                                                                         |
|-0010010 |Backward Sequence Number                     |18                                  |
|1------- |Backward Indicator Bit                       |1                                   |
|-0000110 |Forward Sequence Number                      |6                                   |
|1------- |Forward Indicator Bit                        |1                                   |
|--111010 |Length Indicator                             |58                                  |
|00------ |Spare                                        |0                                   |
|----0011 |Service Indicator                            |SCCP                                |
|--00---- |Sub-Service: Priority                        |Spare/priority 0 (U.S.A. only)      |
|10------ |Sub-Service: Network Ind                     |National message                    |
|**b14*** |Destination Point Code                       |MSC Point Code                                |
|**b14*** |Originating Point Code                       |SMSC Point Code                                |
|ITU-T WHITE BOOK SCCP (SCCP)  UDT (= Unitdata)                                              |
|Unitdata                                                                                    |
|0011---- |Signalling Link Selection                    |3                                   |
|00001001 |SCCP Message Type                            |9                                   |
|----0001 |Protocol Class                               |Class 1                             |
|0000---- |Message Handling                             |No special options                  |
|00000011 |Pointer to parameter                         |3                                   |
|00000111 |Pointer to parameter                         |7                                   |
|00001011 |Pointer to parameter                         |11                                  |
|Called address parameter                                                                    |
|00000100 |Parameter Length                             |4                                   |
|-------1 |Point Code Indicator                         |PC present                          |
|------1- |Subsystem No. Indicator                      |SSN present                         |
|--0000-- |Global Title Indicator                       |No global title included            |
|-1------ |Routing Indicator                            |Route on Subsystem No.              |
|1------- |For national use                             |1                                   |
|**b14*** |Called Party SPC                             |MSC Point Code                                |
|00------ |Spare                                        |0                                   |
|00000110 |Subsystem number                             |HLR                                 |
|Calling address parameter                                                                   |
|00000100 |Parameter Length                             |4                                   |
|-------1 |Point Code Indicator                         |PC present                          |
|------1- |Subsystem No. Indicator                      |SSN present                         |
|--0000-- |Global Title Indicator                       |No global title included            |
|-1------ |Routing Indicator                            |Route on Subsystem No.              |
|1------- |For national use                             |1                                   |
|**b14*** |Calling Party SPC                            |SMSC Point Code                                |
|00------ |Spare                                        |0                                   |
|00001011 |Subsystem number                             |ISDN supplementary services         |
|Data parameter                                                                              |
|00100101 |Parameter length                             |37                                  |
|**B37*** |Data                                         |e2 23 c7 04 06 d0 e4 11 e8 1b e9... |
|ANSI TCAP T1.114-1988 for EIA/TIA IS-41.5D Dec.97, IS-771 Jul.99 , IS-826 Aug.20, IS-764 Jun.98, IS-751 Feb.98 (IS41)  QRYP (= Query With Perm)  |
|Query With Perm                                                                             |
|11100010 |Tag                                          |(PRIV C [2])                        |
|00100011 |Length                                       |35                                  |
|1 Transaction ID                                                                            |
|11000111 |Tag                                          |(PRIV P [7])                        |
|00000100 |Length                                       |4                                   |
|***B4*** |Originating ID                               |06 d0 e4 11                         |
|2 Component Sequence                                                                        |
|11101000 |Tag                                          |(PRIV C [8])                        |
|00011011 |Length                                       |27                                  |
|2.1 Invoke Last                                                                             |
|11101001 |Tag                                          |(PRIV C [9])                        |
|00011001 |Length                                       |25                                  |
|2.1.1 Component ID                                                                          |
|11001111 |Tag                                          |(PRIV P [15])                       |
|00000001 |Length                                       |1                                   |
|00000001 |Component ID value                           |1                                   |
|2.1.2 Private Operation                                                                     |
|11010001 |Tag                                          |(PRIV P [17])                       |
|00000010 |Length                                       |2                                   |
|00001001 |Operation Family                             |IS-41 MAP                           |
|00110111 |Operation Specifier                          |SMS Request                         |
|2.1.3 Parameter Set                                                                         |
|11110010 |Tag                                          |(PRIV C [18])                       |
|00010000 |Length                                       |16                                  |
|2.1.3.1 Mobile Identification Number                                                        |
|10001000 |Tag                                          |(CONT P [8])                        |
|00000101 |Length                                       |5                                   |
|***B5*** |Mobile Id Number                             |`xxxxxxxxxx`                        |
|2.1.3.2 SMS_Notification Indicator                                                          |
|***B2*** |Tag                                          |(CONT P [109])                      |
|00000001 |Length                                       |1                                   |
|00000001 |SMS Notification Indicator                   |Notify when available               |
|2.1.3.3 SMS_Teleservice Identifier                                                          |
|***B2*** |Tag                                          |(CONT P [116])                      |
|00000010 |Length                                       |2                                   |
|***B2*** |SMS Teleservice Id                           |4098                                |


Response:

1:B (Rx):1  MTP-L2  MSU  SCCP  UDT  IS41  RES                                               |
|MTP Level 2 (MTP-L2)  MSU (= Message Signal Unit)                                           |
|Message Signal Unit                                                                         |
|-0000110 |Backward Sequence Number                     |6                                   |
|1------- |Backward Indicator Bit                       |1                                   |
|-0010011 |Forward Sequence Number                      |19                                  |
|1------- |Forward Indicator Bit                        |1                                   |
|--101001 |Length Indicator                             |41                                  |
|00------ |Spare                                        |0                                   |
|----0011 |Service Indicator                            |SCCP                                |
|--00---- |Sub-Service: Priority                        |Spare/priority 0 (U.S.A. only)      |
|10------ |Sub-Service: Network Ind                     |National message                    |
|**b14*** |Destination Point Code                       |SMSC Point Code                                |
|**b14*** |Originating Point Code                       |MSC Point Code                                |
|ITU-T WHITE BOOK SCCP (SCCP)  UDT (= Unitdata)                                              |
|Unitdata                                                                                    |
|1111---- |Signalling Link Selection                    |15                                  |
|00001001 |SCCP Message Type                            |9                                   |
|----0000 |Protocol Class                               |Class 0                             |
|0000---- |Message Handling                             |No special options                  |
|00000011 |Pointer to parameter                         |3                                   |
|00000111 |Pointer to parameter                         |7                                   |
|00001011 |Pointer to parameter                         |11                                  |
|Called address parameter                                                                    |
|00000100 |Parameter Length                             |4                                   |
|-------1 |Point Code Indicator                         |PC present                          |
|------1- |Subsystem No. Indicator                      |SSN present                         |
|--0000-- |Global Title Indicator                       |No global title included            |
|-1------ |Routing Indicator                            |Route on Subsystem No.              |
|1------- |For national use                             |1                                   |
|**b14*** |Called Party SPC                             |SMSC Point Code                                |
|00------ |Spare                                        |0                                   |
|00001011 |Subsystem number                             |ISDN supplementary services         |
|Calling address parameter                                                                   |
|00000100 |Parameter Length                             |4                                   |
|-------1 |Point Code Indicator                         |PC present                          |
|------1- |Subsystem No. Indicator                      |SSN present                         |
|--0000-- |Global Title Indicator                       |No global title included            |
|-1------ |Routing Indicator                            |Route on Subsystem No.              |
|1------- |For national use                             |1                                   |
|**b14*** |Calling Party SPC                            |MSC Point Code                                |
|00------ |Spare                                        |0                                   |
|00000110 |Subsystem number                             |HLR                                 |
|Data parameter                                                                              |
|00010100 |Parameter length                             |20                                  |
|**B20*** |Data                                         |e4 12 c7 04 06 d0 e4 11 e8 0a eb... |
|ANSI TCAP T1.114-1988 for EIA/TIA IS-41.5D Dec.97, IS-771 Jul.99 , IS-826 Aug.20, IS-764 Jun.98, IS-751 Feb.98 (IS41)  RES (= Response)  |
|Response                                                                                    |
|11100100 |Tag                                          |(PRIV C [4])                        |
|00010010 |Length                                       |18                                  |
|1 Transaction ID                                                                            |
|11000111 |Tag                                          |(PRIV P [7])                        |
|00000100 |Length                                       |4                                   |
|***B4*** |Responding ID                                |06 d0 e4 11                         |
|2 Component Sequence                                                                        |
|11101000 |Tag                                          |(PRIV C [8])                        |
|00001010 |Length                                       |10                                  |
|2.1 Return Error                                                                            |
|11101011 |Tag                                          |(PRIV C [11])                       |
|00001000 |Length                                       |8                                   |
|2.1.1 Component ID                                                                          |
|11001111 |Tag                                          |(PRIV P [15])                       |
|00000001 |Length                                       |1                                   |
|00000001 |Component ID value                           |1                                   |
|2.1.2 Private Error                                                                         |
|11010100 |Tag                                          |(PRIV P [20])                       |
|00000001 |Length                                       |1                                   |
|10000110 |Private Error                                |Operation Not Supported             |
|2.1.3 Parameter Set                                                                         |
|11110010 |Tag                                          |(PRIV C [18])                       |
|00000000 |Length                                       |0                                   |
Logged
shad
Sr. Member
****
Offline Offline

Posts: 54


« Reply #8 on: May 18, 2006, 21:41:26 UTC »

Now that's what I call a trace  Cool

So the question is: why are you sending this to the MSC DPC? If you want the MSC to act as an STP, you should set the DPC to the HLR point code, but just send the message on the link to the MSC.

The MSC may well have the HLR subsystem present (so that's why you don't get SSP message in response), but it's probably not configured to do anything.

-Shad
Logged
man_shandy
Full Member
***
Offline Offline

Posts: 20


« Reply #9 on: May 19, 2006, 06:17:06 UTC »

Now that's what I call a trace  Cool

So the question is: why are you sending this to the MSC DPC? If you want the MSC to act as an STP, you should set the DPC to the HLR point code, but just send the message on the link to the MSC.

The MSC may well have the HLR subsystem present (so that's why you don't get SSP message in response), but it's probably not configured to do anything.

-Shad

Hi Shad,
             Thanks for active cooperation Smiley

I have some points I want to discuss:

1.   Earlier I tried to send sms request with HLR point code to MSC Link, but didnt get response and got timed out error on TCAP layer.

2.   Our opearator has configured seperate link to HLR from SMSC for HLR point code, and requested to send sms request to that link, but its failed.

3.   When I try with MSC Point code to msc link, then operation not supported error comes.

Now could u please tell me that

a.   Is there any configuration to do on either side (SMSC or MSC side)

b.   Is IS41-D.5 compliance with IS41-C? because our operator is having IS41-C and we are using IS41-D (issue 5) for our SMSC.

c.    In issue 5 of IS41-D, there is one parameter in SMS-Request, QOS (Quality of service), when I set this parameter value as 01, then SCCP Class should come as 0 and message handling parameter should come as "No special option" defined.  Class 0 came but message handling parameter doesn't come as "No special option".

d.   Is there any problem in Intel SS7 stack?

Please answer, I've been stucking in this issue for a long time.

Thanks
Manish
     
Logged
shad
Sr. Member
****
Offline Offline

Posts: 54


« Reply #10 on: May 19, 2006, 19:07:56 UTC »

Quote
1.   Earlier I tried to send sms request with HLR point code to MSC Link, but didnt get response and got timed out error on TCAP layer.
Is there any chance of getting the operator to trace the MSC-HLR link to see if your message is being passed on to the HLR? Although since the response (nothing) is the same as the direct link this is probably not the issue.

Quote
2.   Our opearator has configured seperate link to HLR from SMSC for HLR point code, and requested to send sms request to that link, but its failed.
This seems like the best chance for success. From your earlier post you get no response at all, right? Is the link definitely "up"? IS-41-C says use SCCP class 0, but you are using class 1. I have seen both 0 and 1 used without any problems, but maybe the HLR doesn't want to receive class 1? You've tried a MIN-based SMSREQ on this link as well as a MDN-based one?

Quote
3.   When I try with MSC Point code to msc link, then operation not supported error comes.
Although this is the best result so far, I think this message is coming from the MSC, not the HLR. I wouldn't continue with the MSC point code (for no GT)...

Quote
a.   Is there any configuration to do on either side (SMSC or MSC side)
There shouldn't be much to do - so long as the basic SS7 routing is in place, this should be standard behavior. Maybe there is something required in the HLR to "authorize" the SMSC?

Quote
b.   Is IS41-D.5 compliance with IS41-C? because our operator is having IS41-C and we are using IS41-D (issue 5) for our SMSC.
The SMSREQ that you posted above is compliant with rev C at the MAP layer. I'm not quite sure what issue 5 is, I would use the latest published standard available on the 3GPP2 website - X.S0004-540 and -550, although they are a couple of years old now. If there's a later version available I'd be happy to learn of it.

Quote
c.    In issue 5 of IS41-D, there is one parameter in SMS-Request, QOS (Quality of service), when I set this parameter value as 01, then SCCP Class should come as 0 and message handling parameter should come as "No special option" defined.  Class 0 came but message handling parameter doesn't come as "No special option".
I can't see the QoS parameter in the MAP layer of ANSI-41-E for SMSREQ (the version on the 3GPP2 site as described above). But the ITU transport section says use class 0, and message handling can be either "no special option" or "return on error"

Quote
d.   Is there any problem in Intel SS7 stack?
I don't know anything about this product sorry.

hope this helps
-shad

Logged
itsnomihere
Sr. Member
****
Offline Offline

Posts: 44


« Reply #11 on: May 20, 2006, 15:43:21 UTC »

please post your intel configuration file
config.txt
system.txt and there will be a ms7 file


Are you sure that you have two MTP Routes in config.txt
one for HLR and one for MSC

Thanks
Logged
parasa
Sr. Member
****
Offline Offline

Posts: 142



« Reply #12 on: May 22, 2006, 05:37:14 UTC »

Hi Manish,

Problem related to timeout at stack layers are easier to track if you have protocol analyser.

Tap the link going to HLR using protocol anlyser and see if request is actuall ygoing out of your box to the network .....

I hope that way u will be able to track the problem.

Regards,


Logged

Thanks & regards,

Parasa kiran
India
man_shandy
Full Member
***
Offline Offline

Posts: 20


« Reply #13 on: May 22, 2006, 07:20:52 UTC »

hi nomi,
             these are the files:

system.txt

Essential modules running on host:

LOCAL                      0x20                        * ssd/ssds/ssdh - Board interface task
LOCAL      0x00      * tim_nt - Timer task

Optional modules running on the host:

LOCAL      0xcf      * s7_mgt - Management/config task
LOCAL                      0xef                         * s7_log - Display and logging utility 
LOCAL      0x2d      * upe - Example user part task

Modules that optionally run on the host:

LOCAL       0x33      * SCCP module
LOCAL       0x14      * TCAP module
LOCAL      0x22      * MTP3 module
LOCAL      0x25      * IS41 module
LOCAL      0x5d      * Application module
LOCAL      0x6d      * Application module
LOCAL      0x7d      * Application module
LOCAL      0x8d      * Application module
LOCAL      0x9d      * Application module

Essential modules running on the board (all redirected via ssd):

REDIRECT                    0x71   0x20   * MTP2 module (except SS7HD boards)
REDIRECT                 0x10        0x20        * CT bus/Clocking control module
REDIRECT                    0x8e   0x20   * On-board management module

Modules that optionally run on the board (all redirected via ssd):

Redirection of status indications:

REDIRECT    0xdf   0xef   * LIU/MTP2 status messages -> s7_log

FORK_PROCESS   ssds.exe -d
FORK_PROCESS   tim_nt.exe
FORK_PROCESS   tick_nt.exe
FORK_PROCESS   s7_mgt.exe -d
FORK_PROCESS   s7_log.exe -fgct.log -d
FORK_PROCESS   mtp_nt.exe -t
FORK_PROCESS   scpcl_nt.exe -t
FORK_PROCESS   tcp_nt.exe -t
FORK_PROCESS   is41_nt.exe -t


Config.txt

 For SPCI4 / SPCI2S boards:
* SEPTELPCI_BOARD <board_id> <flags> <code_file> <run_mode>
SEPTELPCI_BOARD  0  0x0043  ss7.dc3 MTP2

* Configure individual E1/T1 interfaces:
* LIU_CONFIG <board_id> <liu_id> <liu_type> <line_code> <frame_format>
*            <crc_mode>
LIU_CONFIG  0  0  5  1  1  1
LIU_CONFIG  0  1  5  1  1  1
*
*
* MTP parameters:
*
* MTP_CONFIG <reserved> <reserved> <options>
MTP_CONFIG  0  0  0x00000000
*
* Define linksets:
* MTP_LINKSET <linkset_id> <adjacent_spc> <num_links> <flags> <local_spc> <ssf>
MTP_LINKSET  0  xxxx  2  0x0000  zzzz 0x08
MTP_LINKSET  1  yyy   1  0x0000  zzzz 0x08

MTP_LINK  0  0  0  2  0  0    0   2  0x0006
MTP_LINK  1  1  0  0  0  1    1   1  0x0006
MTP_LINK  2  0  1  1  0  2    0   1  0x0006

* Define a route for each remote signaling point:
* MTP_ROUTE <dpc> <linkset_id> <user_part_mask>
MTP_ROUTE  xxxx  0  0x0028
MTP_ROUTE  yyy  1  0x0028
*
* Define any user provided Layer 4 protocol:
* MTP_USER_PART <service_ind> <module_id>
MTP_USER_PART  0x03  0x33
*

MS7 File:

SCCP Configuration.

M-t7740-i0000-fef-d33-r8000-p018303223322efef000026a7011000ef0000000000000000000000000000000000000000000000000000000200000000000000000000000000000000

Configure Local sub-systems:
M-t7741-i0000-fef-d33-r8000-p00031401000000000500000000000000000000000000000000000000000000000000000000000000
M-t7741-i0000-fef-d33-r8000-p00031401000000000600000000000000000000000000000000000000000000000000000000000000
M-t7741-i0000-fef-d33-r8000-p00031401000000000800000000000000000000000000000000000000000000000000000000000000
M-t7741-i0000-fef-d33-r8000-p00031401000000000b00000000000000000000000000000000000000000000000000000000000000

Configure Remote SP's:
M-t7741-i0000-fef-d33-r8000-p00010000000015f70000000000000000000000000000000000000000000000000000000000000000
M-t7741-i0000-fef-d33-r8000-p00010000000000640000000000000000000000000000000000000000000000000000000000000000

Configure Remote sub-systems:
M-t7741-i0000-fef-d33-r8000-p00020000000015f70500000000000000000000000000000000000000000000000000000000000000
M-t7741-i0000-fef-d33-r8000-p00020000000015f70600000000000000000000000000000000000000000000000000000000000000
M-t7741-i0000-fef-d33-r8000-p00020000000015f70800000000000000000000000000000000000000000000000000000000000000
M-t7741-i0000-fef-d33-r8000-p00020000000015f70b00000000000000000000000000000000000000000000000000000000000000

M-t7741-i0000-fef-d33-r8000-p00020000000000640600000000000000000000000000000000000000000000000000000000000000
M-t7741-i0000-fef-d33-r8000-p00020000000000640800000000000000000000000000000000000000000000000000000000000000
M-t7741-i0000-fef-d33-r8000-p00020000000000640b00000000000000000000000000000000000000000000000000000000000000

M-tc744-i0005-fef-d33-r8000-p0101000000000000
M-tc744-i0006-fef-d33-r8000-p0101000000000000
M-tc744-i0008-fef-d33-r8000-p0101000000000000
M-tc744-i000b-fef-d33-r8000-p0101000000000000

TCAP Configuration:

M-t7780-i0000-fef-d14-r8000-p00142533efef00020800080008000100000080000410080100ff0001000000000000000000000000

IS41 Configuration:

M-t77b4-i0000-fef-d25-r8000-p2d14efefef0000008000000080000800080008000000000000000000000000000000000000000000

Hope I can get the solution of my problem in ur next reply.

Thanks
Manish

Logged
itsnomihere
Sr. Member
****
Offline Offline

Posts: 44


« Reply #14 on: May 23, 2006, 10:41:21 UTC »


Please take a look at my SCCP configuration (other than my GT configuration)

M-t7740-i0000-fef-d33-r8000-p018340823322efef00001261011000ef0000000000000000000000000000000000000000000000000000000d00000000000000000000000000000000
*
*       Configure Local sub-systems
M-t7741-i0000-fef-d33-r8000-p0003140100000000ee00000000000000000000000000000000000000000000000000000000000000
*
*       Configure Remote SP's
M-t7741-i0000-fef-d33-r8000-p00010000000012540000000000000000000000000000000000000000000000000000000000000000
*
*       Configure Remote sub-systems MSC
M-t7741-i0000-fef-d33-r8000-p00020000000012540800000000000000000000000000000000000000000000000000000000000000
*       Configure Remote Sub-System HLR
M-t7741-i0000-fef-d33-r8000-p00020000000012540600000000000000000000000000000000000000000000000000000000000000

M-tc744-i00ee-fef-d33-r8000-p0101000000000000
M-tc744-i0006-fef-d33-r8000-p0101000000000000
M-tc744-i0008-fef-d33-r8000-p0101000000000000
Logged
man_shandy
Full Member
***
Offline Offline

Posts: 20


« Reply #15 on: May 23, 2006, 12:31:15 UTC »

Thanks nomi,
                    I will compare with ur configuration and check it.                     
Logged
Pages: [1] Go Up Print 
« previous next »
Jump to:  


Login with username, password and session length