Why Modify Inbound Caller ID

[ralph]

I've been playing a bit with the form "SIP Peer Profile Calling Party Inward Dialing Modification".
This form allows you to modify the incoming caller ID to something else.

My question is:  Why would you want to do this?

I can't think of a reason to change the caller ID of someone calling into my office.
I'm sure there must be or the form wouldn't exist but I can't think of one.

Ralph

[Jockey]

Hi Ralph.
We had a problem where the incoming party had CLI Blocked and the SIP provider supplied "Anonymous"that was OK if answered by the extension, but if in our case the call was to a EHDU the SIP provider would drop the call because of the label Anonymous.
To overcome this we changed this in the URI/No transaltion form, now works.

Regards
Dave

[x-man]

http://www.tek-tips.com/viewthread.cfm?qid=1723275 might be interesting Ralph.

[ralph]

Doesn't appear to be the same thing.
It their case I'd name the DNIS and route it to a general hunt group.
The form I'm looking at is the form to modify the caller ID.

As it happens I talked to the Mitel Product manager yesterday.
I actually asked him about the form.
Turns out the only reason they had for creating these 2 forms was to block hackers. All because *proper* security wasn't set up.

Ralph

[Jockey]

Hi, dont understand, but it works so why break it.

[v2win]

The only thing I could think of is a location overseas the carrier putting a 011 in front of the CLI and the local site only wanting to see the country code

[martyn]

The way that I use it is to put a 0 (in your case 9) in front of the incoming number so that when a user dials from their call history it doesn't have to be modified for the call to go out.

The other use for it is to strip an extra digit off of the CLI display as when the call comes in via SIP it is delivered in the 881231234 format, where the extra 8 at the start isn't needed, so it gets stripped off and presented to the phone as 81231234 which is a local number. The other thing to do would be to get it to insert an extra 0 and leave the extra 8 then the number would be a full national number, but users would rather see the local number version for a local call.

[Jockey]

thanks for advice.
To explain more.
The site is a large hotel in New Zealand with a Mitel MXEIII MCD 5, Recently we changed over to SIP trunks via virtual MBG.
The Front office manager uses an application of Dynamic extension and the problem was that when a caller had their CLI blocked the SIP provider would send the call in with Anonymous in the header where you would expect to see the number, the problem then was that when the call progressed through the Mitel to call his cell phone the word Anonymous was being sent and not accepted by the network provider so the call was rejected.
To overcome this we made an entry in the URI/ Translation to change anonymous to be the Pilot No.
Regards
Dave

[sarond]

In Australia the caller id is 9 digits e.g. 732xxxxxx but it is not a dialable number and is inconsistent with how numbers are displayed normally through carrier networks.
We would modify the incoming CLID to prefix a 0, this is more user friendly and allows proper call backs through applications. i.e. it will now display 0732xxxxxx

It is more of a comfort thing to display what customers are expecting and a functional thing when applications are used.

[ralph]

Ah!  That makes sense to me. 
Thanks for letting me know.

Ralph

[boycey9]

For some reason our SIP carrier decided to prefix 44 in front of all numbers last week, the effect this had is that trusted numbers (ie EHDU) were no longer recognized, by using this I removed the 44 and got back to our mobiles being trusted when Dialling in