DNIS information doesn't survive SCN

[patrickpeters]

Hi folks,

I've got IP Office 500 "A" that's networked to IP Office 500 "B" using SCN. I've got a DID on "A" that has a destination of an extension that's connected to "B". When I get a call on "B" and look at the DNIS information for that call, I get the extension number on "B" instead of the DID that was dialed on "A". Any idea how I can get the DNIS information from "A" when the call arrives on "B"?

I'm running IP Office 8.1 on both "A" and "B".

[furrerm]

Is the trunk connecting the 2 together, set as SCN?

[patrickpeters]

The Supplementary Services setting is "IP Office SCN" on both ends. Is that the setting you're asking about or is there another one?

[pdgavin]

DNIS information doesn't survive SCN

Try adding a short code to the H.323 trunk that connects site a to site b and site b to site a.

The short code would be ? and the telephone number would be .SS and the outgoing line group is the outgoing line group for that trunk.

http://marketingtools.avaya.com/knowledgebase/businesspartner/ipoffice/mergedProjects/manager/short_codes_short_code_characters.htm

SS - Pass Through Calling Number
Pass through the Calling Party Number. For example, to provide the incoming ICLID at the far end of a VoIP connection, a short code ? with telephone number .SS should be added to the IP line.

Pete G.

[patrickpeters]

I think I understand the concept, but I want to pass through the *called* number (DNIS), not the calling number (ICLID). Do you know of a way to do that?

[pdgavin]

DNIS information doesn't survive SCN

I would add it as part of a call tag in the ICR. Example if the DNIS digits are 1234 make the call tag 1234 in the Incoming Call Route and this should be sent to the remote user in the SCN. Tagging is supprted across an SCN:

Call Tagging
Call tag text added to a call is retained by calls routed across the Small Community Network.


Pete G.