How to Add Redirection Information in IAM Message on PGW 2200

[erol.turkeri]

Hi All ,

I can't specify redirection information for diversion calls  on PGW. Redirection information likes below for egress side. Could you help me ?

    Redirection Information

        Optional Parameter: 19 (Redirection information)

        Parameter length: 2

        .... .011 .... .... = Redirection indicator: call diverted (3)

        0000 .... .... .... = Original redirection reason: unknown/not available (0)

        .... .... .... .001 = Redirection counter: 1

        .... .... 0000 .... = Redirection reason: unknown/not available (0)

 Thanks

[Daniele Giordano]

If you are using PGW as SS7-SIP PSTN gateway and you can add SIP Diversion header in your incoming SIP signalling to PGW, you will get the ISUP Redirection information in your outgoing IAM.

e.g. Diversion: <sip:123@1.1.1.1>;reason=unknown

Regards.

[erol.turkeri]

Thank you for the answer, but I've already added the sip diversion header in  sip incoming trunk. By doing that, I have accomplished to inject the redirecting number in the ss7 messages. However, redirection information field is still empty. Is there any way to create redirection information message from sip to ss7 calls.

[Daniele Giordano]

What's the version of your PGW?

Check these parameters:

*.rnInclude    Indicates whether or not to include the Redirecting Number in an IAM. Values:
0 or 1. Default:0

*.redirCapInclude    Indicates whether or not to include the Redirect Capability in an IAM. Values: 0
or 1. Default: 0

*.redirCounterInclude    Indicates whether or not to include the Redirect Counter in an IAM. Values: 0 or
1. Default: 0

*.redirInfoInclude    Indicates whether or not to include the Redirection Info in an IAM. Values: 0 or
1. Default: 0

Let me know your results.

Regards.

[erol.turkeri]

Hi ,

Our pgw's version is 9.7 .

*.rnInclude = 0

*.redirCapInclude = 1
*.redirCounterInclude = 1
*.redirInfoInclude = 1

[Daniele Giordano]

What happen if you set rnInclude = 1?

Regards.

[erol.turkeri]

Actually, I can't set rninclude = 1. I service stop to PGW and then change to RnInclude parameter with 1. After that, star to PGW again, but  RnInclude value was set to 0.

[Daniele Giordano]

Why this procedure?

You must use Provisioning commands:

e.g.

1) open mml console

2) start a provisioning session changing source versione and destination version according to your scenario

prov-sta::srcver="20120831_1615",dstver="20120831_1800",confirm

3) edit your config changing the name of the signalling path according to your scenario

prov-ed:sigsvcprop:name="ss7path1",rnInclude="1"

4) deploy the config

prov-dply

If you have doubt you can study this document: http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/pgw/9/command/reference/mmlref_1.html

and use prov-rtrv command to get the current config.

Regards.

[erol.turkeri]

Thanks for information, we soleved the problem. Our variant vaule(Q767_TURKISH) doesn't support  this header. We changed it wtih ISUPV3 and problem has been resolved.

Have nice day.

prov-add:SS7PATH:NAME="ss7-tg-1234",DESC="SS7 MCTR t to Test",MDO="Q767_TURKISH",CUSTGRPID="plAB",SIDE="network",DPC="dpc-tg-1234",OPC="opc-mctr-nat-2",M3UAKEY="",ORIGLABEL="",TERMLABEL=""