Pass incoming CLI when forwarded to a Mobile 3

[mitelmania]

Hi All,

anyone come across this before, I have a 3300 ICP with MCD 4.1 and Embedded ISDN PRI Trunks in the UK, what the client would like to do is when they forward an extension to a mobile number is have the original incomming callers CLI pass out to the mobile instead of the 3300s default CPN, I have changed the step "Replace External CLID" in the ISDN protocol form but all this does is send the CPN Substitution instead of the default CPN, rather than allow the incoming callers CLI pass through the 3300 and out to the mobile number. I am thinking this may be a restriction of the Network Provider but any thoughts welcome !! I have verified there is incoming CLI.

Cheers

 

[wireman50]

Wont work in the uK; CLI must be a valid number on the ISDN circuit. There is a setting to substitute the number but it would just fail if you did it.

 

[amriddle01]

Not strictly true, you can sign an agreement with BT and they will allow Type 4 presentation (which this classes as). So it is achievable, however getting through to someone at BT who A) Knows what you're talking about and B) Is then able to set it up for you is more of a challenge

 

[Mitel999]

This might be worth a punt....

I kind of had this working with on a uc mobile on a MAS server. But it presented the number in a wired way

I had to ask BT to enable CLI Presentation​ number Type 5

Also had change some settings on the MCD ISDN Outgoing Numbers Type of Number National and Numbering Plan ID National

A typical scenario where type 5 is use would be is a call centre making calls on behalf of more than one client. Type 5 presentation numbers are generated by the user's equipment.



********************************************************************************

Eighty percent of success is showing up

 

[amriddle01]

It's technically Type 4, however Type 5 also includes those beneath it so that would also work:

Types of Presentation Number as defined by OFCOM

Type 1

A.4. A presentation number generated by the subscriber's network provider. The number is stored in the network and applied to an outgoing call at the local exchange by the provider. Because the number is applied by network equipment there is no need for it to be verified each time a call is made – instead the level of authenticity will depend on the checks made by a network provider that a subscriber is entitled to use a particular presentation number.

Type 2

A.5. A presentation number which identifies a caller's extension number behind a DDI switchboard. Although the number or partial number is generated by the user's own equipment, the network provider is able to check that it falls within the range and length allocated to a particular subscriber. In this way the authenticity of the number may be ensured. It should be noted that some network providers classify type 2 presentation numbers as network numbers (especially where the full number is constituted at the local exchange). This type of number is considered to carry sufficient authenticity to be classified as a network number and is carried as such by some networks.

Type 3

A.6. A presentation number limited to the far-end break out scenario where a call's ingress to the public network may be geographically remote from where it was originated. The number is generated by the user's equipment and is not capable of being subjected to network verification procedures. Verification is based on a contract between the subscriber and the network operator in which the subscriber gives an undertaking that only authentic calling party numbers will be generated.

Type 4

A.7. A presentation number available for the onward transmission of the originating number where a call breaks into a private network and breaks out again before termination, as in a DISA scenario. On the break out leg the number is generated by the user's equipment although it will have already been verified in consequence of having been delivered to the private network. To maintain the verification it is necessary to ensure that the number submitted by the private network is the number that was received.

A.8. Network providers wishing to offer a type 4 service will require a contractual commitment from customers that they will only submit CLIs that have been received from the public network. Unlike other types of presentation numbers, type 4 numbers may not always be diallable; this will depend on the nature of the number received from the public network.

Type 5

A.9. Presentation numbers that identify separate groups of callers behind a private network switch wishing to send different outgoing CLIs. A typical scenario is a call centre making calls on behalf of more than one client. Type 5 presentation numbers are generated by the user's equipment. Subscribers will need to enter into a similar contractual commitment with their network providers as for type 1 presentation numbers - that they are entitled to use the numbers they have selected.

 

[mitelmania]

Great info chaps, cheers for that !

 

[kwbMitel]

@amriddle01 - whoa, that is one hell of a quality post. Almost makes me wish I lived in the UK so that it would be useful to me.

Star for you

**********************************************
What's most important is that you realise ... There is no spoon.