Under SRST, you can still benefit of the voicemail system integration at the central site but this time instead to have an internal call to Unity, you need to make an outside calls to Unity when SRST is enbale.
So under the call-manager-fallback command, enable the voicemail <<VM_number_to_dial>> and your end-users will still have the opportunity to press the message button in SRST
If we want to have SRST on MGCP gateways, ensure that you have the two following commands:
!
service alternate
call-manager fallback-mgcp
!
This will ensure that the MGCP gateway can provide Call Processing with SRST. Don’t forget also to have an H323 config to take over in SRST as MGCP hasn’t any Call Control.
E&M stands for a lot of Acronym like
- Ear an Mouth
- Earth and Magneto
- Receive and Transmit
E&m uses an RJ48 interface and is often used to provide tie-line connectivity to PBX. there are 5 types of E&M Interfaces ( I, II , III , IV, V) which are all supported by Cisco except the Type IV.
On this line , we can find the following signaling :
- Wink-start
- delay -start
- immediate-start
- tone-start
Need to more explanations about the different modes !
FXS is an RJ11 interface which is connecting a phone, a fax,… In contrast with FXO, FXS provides dial tone and ring voltage.
FXS can use also the same signaling ( loop-start and ground-start) but loop-start signaling is preferred on FXS line.
FXO is an RJ11 interface which is providing a connection to a PSTN Central Office (CO) or to a PBX interface.
A FXO is considered as a telephony line. We can then find 2 types of signaling :
- Loop-start signaling : this is a type of supervisory signaling that allows indication of on-hook and off-hook states. But this signaling is vulnerable to a condition knows as glare that involves 2 endpoints seizing a trunk a the same time.
- Ground-start signaling : Same as loop-start signaling but this time we suppress the glare effect on these lines.
When you are working with H323 configurations, you can experience teh following ringtones issues , let’s see these issues and how to fix it quickly:
- No Ringback tone on an IP Phone when calling a destination in the PSTN : This comes from a mistmatch between the Call Manager and the PSTN. It can be fixed with the following command progress_ind alert enable 8 under the POTS dial-peer.
- No Ringback tone on a phone in the PSTN when calling an IP Phone: The problem is more similar with the previous one but it differs because it is coming from the other side as this time , the setup message received from the PSTN did not include a progress indicator (PI=0). Indeed, the gateway assumes the network is an ISDN end-to-end network so normally the tone must be handled by the PSTN but it is not an end-to-end call , this is why you have to update again the progress-indicator with the command progress_ind setup enable 3 which is setting the tone in-band.
- No Ringback tone from the PSTN Phone which is forwarded from an IP Phone to another IP Phone : in this case, the issue is caused by the fact that the voice gateway is tearing down logical channel when you are transferring the call , so Audio is not sent. To fix this , you need then to change a parameter under the Call Manager setting ToSendH225UserInfoMsg and put it to True
Recent Comments