CLI Modification

Forums › VoIP › CLI Modification

chevrolux

4962 posts

Uber Geek
Inactive user

#115329 22-Mar-2013 08:54

Hi All,
Not entirely a VoIP question but figure it fits in here anyway...
Having some trouble modifying CLI on ISDN lines. I know for sure our PABX's used to do it no problem, and still do. Just have one site in particular where we can't send out specific CLI's per extension. This is important as they have many many DDI's and want them to be the outgoing CLI when making a call out.

Is anyone aware of any recent changes that stops this happening? Telecom have asked us to send them information on what the phone system is actually sending out.. we have no idea how we can capture this information... wouldn't be a problem on SIP but just don't know how to go about it for ISDN.

Next part of the question is we have the same issue when running through VoIP. It seems when we use the 'old' 2Talk platform (202.176.....) there is no issue using whatever outgoing CLI we want but on the new (27.111.....) we can only send numbers that actually belong to the account. This is annoying... But I think it will be fairly set in stone and probably something to do with nuisance callers.

Any help much appreciated.

maverick

3594 posts

Uber Geek

Trusted

WorldxChange

#785310 22-Mar-2013 08:59

there is no issue using whatever outgoing CLI we want but on the new (27.111.....) we can only send numbers that actually belong to the account. This is annoying...

Seriously ... this is a huge pet hate of mine and one of the main reasons I have a go at other cowboy providers ... sending any number you like breaks all the Telco rules and breaks the integrity of the Telco environment , if you don't own a number you are not allowed to send it !!!! ... its spamming season otherwise

Yes I am a employee of WxC (My Profile) ... but I do have my own opinions as well

https://www.facebook.com/wxccommunications

old3eyes

9119 posts

Uber Geek

Subscriber

#785311 22-Mar-2013 09:00

ISDN CLi format on Telecom ISDN needs to be in a 7 digit number format. You will need to contact your service provider to see why this is not working.

Regards,

Old3eyes

fellaintga

195 posts

Master Geek

#785573 22-Mar-2013 17:03

maverick: there is no issue using whatever outgoing CLI we want but on the new (27.111.....) we can only send numbers that actually belong to the account. This is annoying...

Seriously ... this is a huge pet hate of mine and one of the main reasons I have a go at other cowboy providers ... sending any number you like breaks all the Telco rules and breaks the integrity of the Telco environment , if you don't own a number you are not allowed to send it !!!! ... its spamming season otherwise

No you have to own and verify if its not on your account its not like you can just spoof any number you choose.

sbiddle

30853 posts

Uber Geek

Retired Mod

Trusted

Biddle Corp

Lifetime subscriber

#785577 22-Mar-2013 17:16

fellaintga:
maverick: there is no issue using whatever outgoing CLI we want but on the new (27.111.....) we can only send numbers that actually belong to the account. This is annoying...

Seriously ... this is a huge pet hate of mine and one of the main reasons I have a go at other cowboy providers ... sending any number you like breaks all the Telco rules and breaks the integrity of the Telco environment , if you don't own a number you are not allowed to send it !!!! ... its spamming season otherwise

No you have to own and verify if its not on your account its not like you can just spoof any number you choose.

It still breaks some of the core fundamentals of the NAD.

A call originating from a different LICA to which it terminates should never present CID belonging to the LICA in which it terminates. This opens up many, many, many issues and also raises plenty of issues when calling emergency services.

chevrolux

4962 posts

Uber Geek
Inactive user

#785679 22-Mar-2013 20:46

old3eyes: ISDN CLi format on Telecom ISDN needs to be in a 7 digit number format. You will need to contact your service provider to see why this is not working.

Thanks. Yea we have them as just local 7 digit numbers but doesnt seem to get sent. Been working with gen-i/telecom trying to get it sorted.
Modifying when going out through SIP works fine (on the old platform) so we tend to think the system is doing its job and not the issue.
Thanks for the advice!

sbiddle

30853 posts

Uber Geek

Retired Mod

Trusted

Biddle Corp

Lifetime subscriber

#785688 22-Mar-2013 21:03

On a standard ISDN connection you typically won't be able to present CID that isn't assigned as the pilot or DDI attached to that connection.

If you're referring to be able to do it with Telecom's original SIP trunking platform it was probably because it was the worlds biggest kludge.

chevrolux

4962 posts

Uber Geek
Inactive user

#785717 22-Mar-2013 22:39

sbiddle: On a standard ISDN connection you typically won't be able to present CID that isn't assigned as the pilot or DDI attached to that connection.

If you're referring to be able to do it with Telecom's original SIP trunking platform it was probably because it was the worlds biggest kludge.

Iv done it before where there has been the standard block of 10 ddi's and am able to present them based on which extension is dialling out.
In this instance we have close to 60 ddi's and 5 isdn. But we just cant get them to present on outbound calls. I think at the end of the day it will all end up with 2talk so it will be fine. They just wanted to keep the isdn as they got a 'deal' from telecom. We just need to convince them voip will be solid.... real estate agents dont quite get it lol. Might just give them a sip trunk for outbound calls so they see there is absolutely no difference.

And no, havent been near telecoms sip platform. Didnt know it existed for the general public.

Will keep working with Telecom to resolve it.