chich
08.06.2007, 07:37
Нужена расшифровка формата сообщения CPG. Нет ли у кого?

novak
11.06.2007, 13:19
Открой стандарт Q.763 Q.704 и почитай.
Или расскажи что конкретно интерисует. Непонятно какоето поле? Или ты целеком в ОКС7 не рубишь?
Давай дамп расшифрую.

novak
11.06.2007, 13:27
Table 23/Q.763
Message Type: Call progress
Parameter Reference (subclause) Type Length (octets)
Message type 2.1 F 1
Event information 3.21 F 1
Cause indicators 3.12 O 4-?
Call reference (national use) 3.8 O 7
Backward call indicators 3.5 O 4
Optional backward call indicators 3.37 O 3
Access transport 3.3 O 3-?
User-to-user indicators 3.60 O 3
Redirection number (Note 2) 3.46 O 5-?
User-to-user information 3.61 O 3-131
Generic notification indicator (Note 1) 3.25 O 3
Network specific facility (national use) 3.36 O 4-?
Remote operations (national use) 3.48 O 8-?
Transmission medium used 3.56 O 3
Access delivery information 3.2 O 3
Parameter compatibility Information 3.41 O 4-?
Call diversion information 3.6 O 3
Service activation 3.49 O 3-?
Redirection number restriction 3.47 O 3
Call transfer number (Note 2) 3.64 O 4-?
Echo control information 3.19 O 3
Connected number (Note 2) 3.16 O 4-?
Backward GVNS 3.62 O 3-?
Generic number (Notes 1 and 2) 3.26 O 5-?
Call history information 3.7 O 4
Conference treatment indicators 3.76 O 3-?
UID action indicators 3.78 O 3-?
Application transport parameter (Note 3) 3.82 O 5-?
CCNR possible indicator 3.83 O 3
Pivot routing backward information 3.95 O 3-?
Redirect status (national use) 3.98 O 3
End of optional parameters 3.20 O 1
NOTE 1 – This parameter may be repeated.
NOTE 2 – Peer-to-peer interworking with a pre-1997 version of ISUP may result in format errors and lead to the release of the call.
NOTE 3 – The message may contain one or more application transport parameters referring to different application context identifiers.