0 Replies Latest reply on May 13, 2015 2:48 PM by bradh8148

    Forwarding originating caller ID and Redirecting Number Information Element (RNIE)

    bradh8148 New Member

      I have a customer who would like to forward the originating caller ID when a call is forwarded back out of the PRI. The customer's Telco is requesting the RNIE (Redirecting Number Information Element) to allow us to pass Originating caller ID out of the PRI. We use an Adtran TA924e to connect to a Telco's PRI then the Adtran talks SIP to our PBX. I have already done some research on this and found another post mentioning RNIE  "Configuring SIP PRI to allow CallerID on Call Forward" Below is a copy of the example Config posted in that thread:

       

       

      voice ani-list DIDs

        ani <inbound DID pattern 1>

        ani <inbound DID pattern 2>

      !

      voice trunk-list SIP_Trunks

        trunk T01

        trunk T02

      !

      voice trunk-list PBX_Trunks

        trunk T03

      !

      voice trunk T01 type sip

        sip-server primary <SIP server IP/Hostname>

      !

      voice trunk T02 type sip

        sip-server primary <SIP server IP/Hostname>

        match ani $ add diversion <Customer's main number>

      !

      voice trunk T03 type isdn

        <normal PRI config>

        caller-id-override number-inbound <Customer's main number> if-no-cpn

      !

      voice grouped-trunk SIP

        trunk T01

        accept $

        deny list SIP_Trunks

        permit list DIDs

      !

      voice grouped-trunk SIP_Diversion

        trunk T02

        accept $

        deny list DIDs

        permit list PBX_Trunks

      !

      voice grouped-trunk PRI

        trunk T03

        accept $

        permit list SIP_Trunks

       

      I have some questions about the above config.

      1. How many DIDs can be added to "voice ani-list DIDs".
      2. The current config (Config before adding SIP_Diversion trunk) I am using for the customer in question looks a little different.
        1. In my Voice grouped-trunk SIP I am Permitting the voice trunk-list SIP_Trunks
        2. I also have  list fxs denied on the "voice grouped-trunk SIP"  This is used to prevent fax DIDs from being directed to the PBX instead of the FXS ports.  

       

      Below is part of my config:

       

      !

      voice codec-list PBX_DEFAULT

        default

        codec g711ulaw

      !

      !

      voice ani-list all

        ani $

        ani X$

      !

      voice ani-list fxs

        ani 214xxxxx87

        ani 214xxxxx29

        ani 214xxxxx31

        ani 214xxxxx60

        ani 214xxxxxx2

        ani 214xxxxx02

      !

      voice trunk-list SIP_Trunks

        trunk T01

      !

      !

      voice trunk T01 type sip

        description "PBX to Adtran"

        sip-server primary 172.16.1.2

        dial-string source to

      !

      voice trunk T02 type isdn

        description "PRI to Adtran"

        resource-selection linear ascending

        connect isdn-group 1

        t38

        t38 redundancy high-speed 1

        t38 redundancy low-speed 1

        t38 max-buffer 800

        t38 max-datagram 300

        t38 generate-cng

        rtp delay-mode adaptive

      !

      !

      voice grouped-trunk SIP

        trunk T01

        accept $ cost 0

        deny list fxs

        permit list all

        permit list SIP_Trunks

        !deny all other trunks

        !deny all other ani

      !

      !

      voice grouped-trunk PRI

        trunk T02

        accept $ cost 0

      !

      !

      voice user 214xxxxx87

        connect fxs 0/5

        password encrypted "24209cc96b444d215061178c14ab5e607014"

        sip-authentication password encrypted "2f2b67a85fc7fe507f6c2215dd4664bfcfd8"

        t38

        codec-list PBX_DEFAULT

      !

      !

      voice user 214xxxxx29

        connect fxs 0/1

        password encrypted "4642275d03ad2627cea13e3b8fe320bf9b29"

        did "214xxxxx29"

        sip-authentication password encrypted "343092ec99d76d94b286649962d193cb80ee"

        t38

        codec-list PBX_DEFAULT

      !

      !

      voice user 214xxxxx31

        connect fxs 0/6

        password encrypted "292d291c308f6d66d48be17ad71b507967cd"

        did "214xxxxx31"

        sip-authentication password encrypted "1e1aa742c2891bd23ae4dfcabae276c7347e"

        t38

        codec-list PBX_DEFAULT

      !

      !

      voice user 214xxxxx37

        connect fxs 0/4

        password encrypted "3632c4555bae3c30d946651decec5e91b7ef"

        did "214xxxxx37"

        sip-authentication password encrypted "4642275d03ad2627cea13e3b8fe320bf9b29"

        t38

        codec-list PBX_DEFAULT

      !

      !

      voice user 214xxxxx60

        connect fxs 0/7

        password encrypted "3d39879abc1d03f78fa1b48a8a1f24e4a871"

        did "214xxxxx60"

        sip-authentication password encrypted "1a1e5b71ee92b5ed6304ce4748ac1c824558"

        t38

        codec-list PBX_DEFAULT

      !

      !

      voice user 214xxxxx02

        connect fxs 0/3

        password encrypted "161214f02c7d3ea8b41ff99f9d434ab7057c"

        did "214xxxxx02"

        sip-authentication password encrypted "292d291c308f6d66d48be17ad71b507967cd"

        modem-passthrough

        t38

      !

      !

       

      If I was to implement the SIP_Deversion trunk would I have to deny list SIP_Trunks on the voice grouped-trunk SIP?

       

      Will there be any other issues with my config compaired to the example config?