Twinning CallerID

[teletechman]

I am having an issue with Verizon SIP enabled PRI to an IP Office 406V2 5.0.26. We are trying to send the incoming callerID to the twinned mobile but Verizon is asking something I don't think the IPO can do. See Below from Verizon Tech;

The issue with the twinning is a bit more complex. As we’ve discussed previously we need to receive a number that can be authenticated on our network in either the From or diversion header field. To get this to work currently the number being called is used in the From field and that is the reason that the calls complete to the cell phones , but the original calling party number is not shown as the Caller ID.

This was adjusted last week or so to allow the original calling party number to be used as the FROM number , but this was not able to be authenticated unless a Valid VoIP number made the call from your location.

I’ve not heard back from Mike is regards to being able to use a redirected number in the ISDN messaging , that will be used as a VoiP diversion header and allow the call to both pass the authentication (in the diversion field) and also use the FROM number of the original calling party number to be used as caller id to the cell phone termination.

The use of the redirection header from the PBX should address this issue, I have not heard back from Mike since he was investigating this. If he is unable to complete this let me know. I can’t guarantee a work around but I may be able to implement some configurations in the router that may give some of the functionality you want.

This was working fine with a TDM PRI and stopped working when they switched to a SIP enabled PRI.
And yes I know tell the provider to fix it, just want to make sure I can't do what he is asking.
Mike

 

[nbfd731]

I think might help

The Send Caller ID parameter is set to “Diversion Header”. With this setting and the related configuration. IP Office will include the Diversion Header for calls that are directed via Mobile Twinning out the SIP Line to Verizon. The Diversion Header will contain the number associated with the Twinning user, allowing Verizon to admit the call, and the From Header will be populated with the true calling party identity, allowing the twinning destination (e.g., mobile phone) to see the true caller id. The Call Routing Method can retain the default “Request URI” setting, or may be changed to “To Header” as shown, to match Incoming Call Routes based on the contents of the “To Header”. In the sample configuration, both approaches were tested successfully



ACSS SME