by Olivier | Feb 25, 2010 | H.323, IOS, Lab, Non classé, Written Theory |
In H.323 , you can play with the caller id (not the case with MGCP , see previous post).
By default,Caller ID is disabled on all FXS ports.
So in order to enable it , you must go under the voice-port and activate it as it is shown in the below config
!
voice-port 2/0
caller-id enable
!
by Olivier | Feb 25, 2010 | CUCM, IOS, Lab, MGCP, Non classé, Written Theory |
Caller ID is not supported on MGCP Controlled FXS ports.
So remind this if you need it 🙂
by Olivier | Feb 23, 2010 | CCME, CUCM, IOS, Lab, Non classé, Written Theory |
In order to your DHCP to give the TFTP address to your phones , the common configuration is to use the option 150 which is the main and the more expanded concept used for providing your TFTP. It can provide an IP Address as well an array of IP Address.
This is also the code which you are using under IOS configurations.
But in some old implementation , you can find also the option 66 to give the TFTP to the phones . Option 66 is different in the meaning that you must provide a server name so you need to have DNS enabled . Also you can only pass one parameter!!!
So don’t be too disturbed if you see this option 🙂
by Olivier | Feb 20, 2010 | H.323, IOS, Lab, Non classé, Written Theory |
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,*,#
by Olivier | Feb 20, 2010 | H.323, IOS, Lab, Non classé, Written Theory |
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
by Olivier | Feb 20, 2010 | H.323, IOS, Non classé, Written Theory |
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
Recent Comments