Preserving DNIS/ANI on inbound SIP calls received via Session Manager

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • bdailey01
    Aspiring Member
    • Jun 2012
    • 2

    Preserving DNIS/ANI on inbound SIP calls received via Session Manager

    I'm looking for alternative ways to preserve DNIS and ANI for inbound calls received from Verizon over SIP trunks. I've got a CS1K (7.5) and Session Manager 6.1 with 2 signaling servers. I'm able to receive calls to my desk via SIP trunking through Session Manager. However, I'm using an SM adaptation to target my office extension when the inbound DNIS matches a configured pattern.

    Unfortunately, when I use an adaptation the inbound DNIS ends up getting translated to the CDN I am targeting. Because this occurs I'm not able to drive a screen pop on original the DNIS because DNIS becomes the targeted CDN, not the original dialed number.

    I could use IDC tables, however I have such a large quantity of DIDs and they change so often that administering them one number at a time at the IDC table level would be a huge burden.

    Is there a way to target a CDN in Session Manager and preserve the DNIS and ANI of the original call when the call reaches the PBX? Anyone have any ideas?
  • gsgleaso
    Member
    .
    • Feb 2010
    • 6

    #2
    I know nothing about CS1K, nor what a CDN is, but ASM should only be adapting the request URI and the P-Asserted-Identity, leaving the To and From headers as they were.

    If your application can read those headers, you should know the original dialed number.

    Comment

    Loading