CS1000:Incoming call to CS1k (Rls 7.6) via DASS , which is Call Forward to another CS

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • smaiyaur
    Guru
    .
    • Nov 2013
    • 107

    CS1000:Incoming call to CS1k (Rls 7.6) via DASS , which is Call Forward to another CS

    CS1000:Incoming call to CS1k (Rls 7.6) via DASS , which is Call Forward to another CS1k via SIP fails.



    Details

    CS1000M , Rls 7.65 ,SP4 and DPNSS Network Services" (DPNSS) package 231 is equipped.


    Problem Clarification

    DASS(PSTN) > CS1K(7.6) > SIP > Session Manager (6.3.6) > CS1K(7.5)
    Incoming call to CS1k (Rls 7.6) via DASS , which is Call Forward to another CS1k via SIP. And if you are doing Call forward using ACOD+Number , it is working fine, but with DSC configuration, it is not working.


    Cause

    Ref. doc. "DPNSS1 Fundamentals" (Release: 7.6, Number: NN43001-572, Issue: 06.01, Date: March 2013, Pages: 115-126):
    DPNSS "Diversion" feature:

    DPNSS1 Diversion is a British Telecom Network Requirement (BTNR) service that provides full DPNSS1 Diversion signaling on DPNSS1 links, when one of the redirection features listed below is invoked:
    - Call Forward All Calls
    - Call Forward No Answer
    - Call Forward by Call Type
    - Call Forward Busy
    - Hunting/Group Hunting
    - Intercept Computer Call Forward All Calls
    - Call Forward Internal Calls
    - Meridian Customer Defined Network Call Redirection
    - Call Party Name Display

    When a telephone activates a redirection feature such as Call Forward All Calls, DPNSS1 signaling informs the call originating node that the call is being forwarded to another telephone. If the forwarded party is located on another node, the call originating node is requested to initiate a new call. When the forwarded to party is reached by the call originator via DPNSS1, the forwarded to party is notified that the incoming call is forwarded.

    Diversion Immediate:
    With Diversion Immediate, the calling party, Telephone A, dials Telephone B that has activated Call Forward All Calls (CFAC) to Telephone C. Upon receipt of the call, Telephone B's node instructs Telephone A's node to Divert-Immediate to Telephone C. Use the prompt DDI in LD 86 to determine whether or not to send the Diverting Immediate string. This is done on an RLB basis.
    When instructed to divert, Telephone A's node clears the old call and initiates a new call to Telephone C. Telephone A's display is updated with diversion information, when the call is established with Telephone C.

    The problematic call diagram is as follows:
    PSTN -> DASS -> CS1000 7.6 -> CFW using DSC -> SIP -> CS1000

    This WILL work for sure. The point is that DDSL is DPNSS link not DASS (PRIV = YES in DDSL ). And channels are DPNSS (SIGL = DPN) in the corresponding RDC/VDC TN's.
    Also, "DPNSS Network Services" (DPNS) package 231 is equipped.

    DPI R 19 12 0 ISRM-C SIC=10, CLC-PSTN, OLI/CLI=07799644664,DA=4868
    DPO R 19 12 5 NAM DVT-I B=7722
    DPI R 19 12 5 CRM CC=CT 0
    DPO R 19 12 0 CIM CC=CT 0

    When incoming PSTN call (CLC-PSTN) is made to DN via DPNSS link the system sees that the call should be redirected to DSC DN , so "DPNSS Diversion" (DVT-I) is triggered. The corresponding message is sent back to PSTN side in order to make a new call to DN . Surely PSTN side does not understand this request and fails.



    Solution

    Solution:
    - Enable plugin 33 "Turn off DPNSS diversion Feature".
    - Else ,Correct DDSL configuration to make the link DASS not DPNSS and correct RDC/VDC channels to be DASS channels. DPNSS (private) link should be used to connect PBX's. DASS (public) link should be used to connect PSTN (CO) to PBX.
Loading