by Olivier | Aug 21, 2010 | CCME, CUCM, H.323, IOS, Lab, MGCP, Non classé, SRST |
Hi ,
Just as a reminder when you sit in the lab, try to not forget to put the correct Calling number , type and plan and this for all situation so it is true as well for SRST.
So a good vision of the call routing is important
by Olivier | Apr 15, 2010 | IOS, Lab, MGCP, Non classé, SRST |
Here is a basic stuff to implement the mgcp config
!
ccm-manager fallback-mgcp
ccm-manager redundant-host 172.17.123.201
ccm-manager mgcp
ccm-manager music-on-hold
ccm-manager config server 172.17.123.200
!
mgcp
mgcp call-agent 172.17.123.200 service-type mgcp version 0.1
mgcp bind control source-interface GigabitEthernet0/0.102
mgcp bind media source-interface GigabitEthernet0/0.102
!
mgcp profile default
!
by Olivier | Mar 8, 2010 | CCME, CUC, H.323, IOS, Lab, Non classé, SRST |
CUE is as the CME a small business voice mail solution that you can easily deploy on a router. Most of the time, CUE will reside on the same chassis than the CME but for some implementations, you can split both. The only backdraw is that you must have a LAN connectivity between your elements.
CUE is interesting because it doens’t provide only voice mail but can also provide a small Auto-Attendant (AA). The integration between CUE and CME is done via the SIP protocol, while the integration with a Call Manager will be done via JTAPI ( CTI-QBE). It can be the case for implementation where you need to provide Unity backup on SRST location).
CUE will be supported by Network Module (NM-CUE) or as an Advanced Integration Module (AIM-CUE).
by Olivier | Mar 8, 2010 | CCME, CUC, CUCM, H.323, IOS, Lab, Non classé, SRST, Written Theory |
CME is more or less the same as we have seen in the SRST implementation. But there is some other enhancements, so let’s see or recap the available mode:
by Olivier | Mar 7, 2010 | CCME, GNS3, H.323, IOS, Lab, Non classé, SRST |
Translation-rule are the best IOS tool that you can use to make digit manipulation. In order to execute them , here are the required steps:
- Build your translation-rules
- Build your translation profiles
- Apply your translation-profiles in incoming or outgoing or both mode
Here are where you can apply yoru translation profiles:
- All voip calls
- a particular dial-peer
- ephone-dn
- interface
- trunk-group
- …
by Olivier | Mar 7, 2010 | H.323, IOS, Lab, Non classé, SRST, Written Theory |
To match the local number with the external number during a SRST failover, you can use the command dialplan-pattern <<tag_pattern>> extension-length <<length>>. this command also ensures that a full E.164 address is sent as the ANI for outgoing calls. The dialplan-pattern command causes the SRST router to create an additional virtual dial peer for local extension corresponding to the pattern specified in the command.So, this command can be used to map the DNIS sent by the PSTN to a local extension.
Pay attention that if you play with translation rules on your voice-port, it may be a good choice also to continue with digit manipulation to conform your SRST dialplan as the translation rule are processed before.
Recent Comments