CUCM SNR /Mobility Connect RNIE Redirecting

[davesnow97_2]

I Have a CME v8.6 with users both forwarding calls (CFWD ALL) and using SNR / Mobility Connect.

We recently resolved an issue where the telco was expecting RNIE on forwarded calls and rejecting forwarded calls without RNIE where the Calling party was not a DID assigned to our PRI.  This was the case with both CFWD-ALL and SNR calls.  Forwarded calls are now working as expected with appropriate CLID on the recieving party side.

I am however still having an issue with the SNR / Mobility Connect calls.

Watching the q931 I can see the SNR calls do not have a RNIE / Redirecting number field being passed.  It is only the Calling and Called party.

I have temporarilly made the calls go through using the "SNR Calling-number local"

-This places the SNR users number in the Calling Party field and allows the calls to go through but the callerid on the SNR users cellphone shows their own desk phone number.  Not very helpfull in seeing who is calling.

Any thoughts on why the SNR calls are not using the RNIE / Redirecting number element on call setup?

[Mohammed al Baqari]

Hi,

SNR is different than CF. In CF, CME won't ring the local phone, instead it will initiate a separate call leg to the final destination. Hence, you see RNIE. You will have only call leg active at a time.

SNR on the other side will extend calls to both local and remote phones. It isn't redirecting the call to final destination. Incoming calls will trigger two call legs ringing. Therefore, you won't see RNIE.

I don't think, you have much options especially you are using PRI. If it has been SIP, then you could use SIP profiles to add diversion header.