Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Caller ID outbound

Status
Not open for further replies.

auEric

Technical User
Jul 13, 2005
73
AU
I know I have read this before, I cant find it and dont remeber what to search for. I need to send my phone number when calling out. We use ISDN lines but are only sending first number of our indial range. I think it was something to do with S prefix some where.

Thanks
 
If you are only sending the first number i would suggest that you network/telco is governing that.

If a user has a ddi assigned, by default the IPO will send that as the cli.

If you run an isdn trace you will be able to see what each user is sending when they make a call.

If that is not what is being presented at the other end then your exchange/telco will be set to only present one number no matter what you present to it. Check with the isdn trace, you may find the IPO is sending each ddi as a cli but the nechange is blocking/normalising it to your main number.

You are correct about the short code, it is the S character, as an example

? .S123456 dial 0

Would send 123456 as a cli, this short code can be applied at a user level or system wide.

ACA - IP Office Implement
ACS - IP Office Implement
ACE - IP Office Implement
 
Thanks for the promt reply. We need to apply this to some users not everyone. To complicate matters we use least cost routes to select trunks depending on destination.
 
Do the isdn trace first, you may find your system is behaving as per the requirement which would mean you have to do nothing but phone the telco and request for the set up to be changed.

If you have an incoming call route pointed straight to a user, the info in that incoming number field should be passed as the cli by default.

So check the trace and also check that the numbers set in the incoming routes match the amount of digits the telco is sending you for ddi. If this all matches then it is the telco.

Are you in OZ?

Gis a job, go on its raining here in the UK.

ACA - IP Office Implement
ACS - IP Office Implement
ACE - IP Office Implement
 
It is caused becaus the extns we are having problems with dont have direct indial numbers. I put the shortcode on the user after the telephone number

Short Code 0N
Telephone Number N .S123456
Line Group ID 0
Feature Dial

We use zero to get a line

raining cats and dogs here.

 
That short code isnt right, lose the .

That above short code will insert N which is the number and then it will insert the 0N again because the . represents that.

I havent actually tried this but i am pretty sure that if you are using the S character in a user short codes, the number after that will still be present even after being processed by LCR.

Maybe somebody else can clarify that as i am at home today and not sat next to my rig?


ACA - IP Office Implement
ACS - IP Office Implement
ACE - IP Office Implement
 
Thanks for the help, it does seem to work with LCR
 
I was woulding how to STOP outbond clid, like when on a POTS line you dial *67 then number and the receiving caller get "PRIVATE" or "UNKNOWN" caller on callerid, I have tried the W shortcut, seems to work, but still sends the users extention number, caller id at receiving end shows '1512' which is the extention i am calling from


Thanks,

Jerry
 
The W character is the right way to do it.

? .W dial

is an example.

Maybe you have a user short code overiding this system short code?

ACA - IP Office Implement
ACS - IP Office Implement
ACE - IP Office Implement
ACI - IP Office Implement
 
@auEric

good to hear you got it working. i have a switch im building right now on 3.2 that requires non-DID users to send out the main number as their CLID and then the DID users to send out there number as normal.

in addition to this, there were all sorts of classes of service and set types, etc.

ultimately i ended up creating User right groups for each type and applying them so that the user level shortcodes were replicated to all the non-DID extensions for outbound CLID.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top