[cisco-voip] SIP Caller ID issue

[Hodgeman, Samuel]

The RDNIS fix is only really applicable to redirected calls… the OP seems to be concerned with calls that are originating from CM… he want to use the caller id of the main number of his company which is configured on ISDN PRI somewhere…

From: Ryan Ratliff (rratliff) [mailto:rratliff at cisco.com]
Sent: Friday, January 16, 2015 12:36 PM
To: Hodgeman, Samuel
Cc: Charles Goldsmith; Mike; cisco-voip voyp list
Subject: Re: [cisco-voip] SIP Caller ID issue

The UCM feature to workaround this is to enable RDNIS delivery outbound on the trunk.  The most common call flow that this can fix is SNR calls where the call outbound to the mobile will use the original calling party number, and we'll set the redirecting number to the desk phone so the SIP provider can bill it appropriately (and let the call go out).

-Ryan

On Jan 16, 2015, at 12:47 PM, Hodgeman, Samuel <shodgeman at xo.com<mailto:shodgeman at xo.com>> wrote:

Well the SIP modification can certainly be done but I tell ya it is a royal pain in the buttockskis.

There is possibly a lower-complexity fix, not to the TECHNICAL issue but for the BUSINESS requirement.

Typically when customers have this issue, and I ask them WHY they truly need to send out that “main number” from another circuit (or even another carrier) as the caller id the answer is something like this:
“When we call somebody, and they decide to call us back at the number they see on their caller id (or with *67) we want the calls to go to our main number and NOT to the individual DID of the person who originally made the outbound call.”

One lower-complexity solution to this business requirement would be to designate one of the “allowed” numbers on the SIP service for use as the caller id, and simply call-forward-always that number back to your main number that resides on the PRI. If you want to avoid hairpinning issues, you can simply ask XO to do the forwarding in their Broadwords server so it never hits your system.

Another solution would be to again designate one of the “allowed” numbers on the SIP service for use as the caller id, and ask XO to set up “Configurable Calling Line ID” feature on that number. As I recall, that is a standard offer on the XO retail SIP trunks product. With this feature, the outbound call is SCREENED for access based on, for example, the “allowed” SIP number of the originating number sent from the ipPBX, but when that number hits the XO Broadworks server, the caller id can be configured to be automatically changed to ANY number that you own (you may need to prove that you own it) before it is forwarded back out to the greater PSTN.


-          Sam H

From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Charles Goldsmith
Sent: Friday, January 16, 2015 11:27 AM
To: Mike
Cc: voip puck
Subject: Re: [cisco-voip] SIP Caller ID issue

We see this a lot with carriers, it prevents scammers from changing caller-id info.  Some carriers will make an exception for things like main numbers, just have to prove you own that number, which isn't hard.

I've never went through the excercise of modifying the SIP header to resolve this.

On Fri, Jan 16, 2015 at 10:09 AM, Mike <mikeeo at msn.com<mailto:mikeeo at msn.com>> wrote:
Hi all , I have a situation where the carrier (XO) is not allowing the call manager to send caller ID if it’s not a number assigned to the trunk. In this situation the main number is not on the sip trunk its on a PRI. The XO tech said you can get around this by modify the SIP header in the from field. Anyone ever ran into this?

Thanks,
Mike



_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20150116/8d2ca530/attachment.html>