MGCP Called ID on FXS ports
Caller ID is not supported on MGCP Controlled FXS ports.
So remind this if you need it 🙂
MIC,LSC, Security Endpoints
Regarding security endpoints, you have 2 opportunities :
- Newer phones are using more an existing Mafufacturing Installed Certificate , this is the MIC
- Meanwhile , old phones will use a Locally Significant Certificate ( LSC) which will be installed by the Certificate Authority Proxy Function (CAPF)
As LSC must be a transaction between the Ip phone and the CAPF , here is the process as it is issued :
- IP Phone generates a public/private key pair
- A TLS Session is established with the CAPF Service and the keys and identity are sent from the phone to CAPF
- The CAPF Service creates and sends an LSC to the phone
- The IP Phone installs the LSC
Also for info, the CAPF Service must be in the phone CTL file , which is downloaded from the TFTP when the phone boots .
StationInit , StationD Skinny Message
In the CUCM traces , you can find a lot of StationInit and StationD .
What are they corresponding ?
Pattern * and # reminder
As reminder , don’t forget that in pattern expression , * and # are valid expressions.
So in fact you have 0,1,2,3,4,5,6,7,8,9,*,#
PVID0 Specifications
As we have already seen it before , if the voice gateway is unable to match an inbound leg for the call , your call will take the properties of the PVID0 .
Don’t forget that you can’t update any properties if the PVID0 is hitted .
Let’s review then the specificities of this default dial-peer:
For POTS dial-peer
- No IVR applications possible
For VOIP dial-peer
- Any codec
- fax-rate voice
- ip precedence 0
- No Resource Reservation Protocol ( RSVP)
- VAD enabled
Outbound Dial Peer leg matching order
As seen with the inbound dial-peer matching , outbound matching is much easier as the dial-peer matches on the destination-pattern expression.
Then the outbound will be selected with the port if you have a POTS dial-peer or will take the session-target in you have a VOIP dial-peer