Demystify Lync Enterprise Voice Phone Numbers and Extension
Download the article as PDF:
With this, we know what the goals are we need to fulfill, in a short sentence, we need to get all numbers translated to an E.164 format. Simply said, E.164 represent an international number format, including the “+” sign at beginning.
- tel:+4980619089123;ext=123 : the extension is part of the phone number.
- tel:+60383830160;ext=123 : the extension is not part of the phone number.
- tel:123;phone-context=HeadQuater. Never put a “+” in front!! (internal “extension” only)
- We have to call an Auto Attendant/ Receptionist because a Called Party has no DID. He mostly has an EXTENSION, the AA or Receptionist is able to forward this call
The Exchange Auto Attendant has some specialties when you are configuring an Enterprise Voice Setup without DID’s. Since the AA has need for any internal extension, we need to identify an EXT attribute.
- Classic DID based deployment
- DID based deployment in conjunction with extensions
- Deployment with internal extensions only
Set-CsPinSendCAWelcomeMail -UserUri firstname.lastname@example.org -From email@example.com
How it’s called and seen on the PSTN Gateways:
callp: mux_isdn:0 (1) ISDN(1756): APP : 11 calling_name ="P�Thomas"-->"Pött Thomas"
Caller ID (caller identification, CID) = calling line identification (CLID)
- UC Phone
- Lync Client
- A prefix can be specified that signals an external number is being dialed
- This prefix will not need to be in the normalization rules
- Internal Extension check box in the normalization rule works with the External Access Prefix to make the below client logic work
- In Lync, user typically dials all desired digits then presses “call”
- Normalization rules are then processed in order to find a match.
- When dialing from a device “off-hook,” an inter-digit dialing delay is used to determine when to place the call
- 1.5 second inter-digit dialing delay
- If a matching rule is found, the number will be dialed
- 10 second final time-out
- If no matching rule is found, the dialstring is sent to the FE
- Excluding patterns from the device is not supported
- User associated Call Placing to Gateways
- Generic Call Routing (Session Management)
- Ports: TCP 5060 (TLS 5061) and UDP 60.000-64.000
- Valid Certificate if TLS is used
- G.711 a-law (used primarily outside North America)
- G.711 µ-law (used in North America)
*) Early Dialogs: RFC 3261: A dialog contains certain pieces of state needed for further message transmissions within the dialog. This state consists of the dialog ID, a local sequence number (used to order requests from the UA to its peer), a remote sequence number (used to order requests from its peer to the UA), a local URI, a remote URI, remote target, a boolean flag called "secure", and a route set, which is an ordered list of URIs. The route set is the list of servers that need to be traversed to send a request to the peer. A dialog can also be in the "early" state, which occurs when it is created with a provisional response, and then transition to the "confirmed" state when a 2xx final response arrives. For other responses, or if no response arrives at all on that dialog, the early dialog terminates.
Author: Thomas Pött Managing Consultant Microsoft UC