Hi Chris: Thanks for your answer, actually in Unity call viewer I am seeing the call as a direct call instead of redirected call, if I erase the command "isdn outgoing ie redirecting-number" from the ISDN serial interface everything works fine for SRST but I have problems with the AAR and the voicemail.
Please let me know if you face the same problem when toy test it. Regards, Jose -----Original Message----- From: Chris Parker [mailto:[email protected]] Sent: Sábado, Marzo 21, 2009 12:56 PM To: Jose Gregorio Linero (jlinero) Cc: Cliff McGlamry; Wesley Lim; [email protected] Subject: Re: [OSL | CCIE_Voice] H323 GW SRST and AAR Voicemail Redirection I have indeed tested this and I understand the why H323 vs MGCP makes a difference. I trying to understand why the redirect would even matter since we arent relying in the presence of the redir number to accomplish anything. I will retest and get back to you Chris Jose Gregorio Linero (jlinero) wrote: > Hi Chris, Cliff: > > I tested with call-forward X commands and with the configuration you > suggested me and the same result, have you tested this configuration when > the Gateway in SiteB is H323?, have you tested this configuration and make > it work without breaking the VM functionality in AAR? > > If you have access to your own lab please add the command "isdn outgoing ie > redirect-number" to the ISDN serial interface, this will allow you to have > the voicemail working for AAR, then test the SRST with your configurations > and please let me know if it works, again, this is not an MGCP gateway in > SiteB, it is a H323 GW in Site B. > > Regards, > > Jose > > -----Original Message----- > From: Chris Parker [mailto:[email protected]] > Sent: Sábado, Marzo 21, 2009 12:25 PM > To: Jose Gregorio Linero (jlinero) > Cc: Cliff McGlamry; Wesley Lim; [email protected] > Subject: Re: [OSL | CCIE_Voice] H323 GW SRST and AAR Voicemail Redirection > > I think you can get around this if you don't use the alias command. > Heres the way I usually do SRST VM: > > voicemail 912122251600 > call-forward busy 91212225169. > call-forward noan 91212225169. timeout 12 > > I create alternate extensions for the full DID in Unity for the button > to work, and I create a CTI port with the number 169X with CFA to VM. > The CTI port has VM profile with a mask of 200X. > > Chris > > Jose Gregorio Linero (jlinero) wrote: > >> Hi Cliff: >> >> Thanks for the answer, this is my H323 configuration: >> >> voice service voip >> >> h323 >> >> no h225 timeout keepalive >> >> ! >> >> ! >> >> voice class codec 1 >> >> codec preference 1 g711ulaw >> >> codec preference 2 g711alaw >> >> codec preference 3 g729r8 >> >> ! >> >> ! >> >> ! >> >> voice class h323 1 >> >> h225 timeout tcp establish 3 >> >> ! >> >> ! >> >> ! >> >> ! >> >> ! >> >> ! >> >> voice translation-rule 1 >> >> rule 1 /\(3...$\)/ /972301\1/ >> >> rule 2 /^\(2...$\)/ /408201\1/ >> >> rule 3 /^\(4...$\)/ /8522433\1/ >> >> ! >> >> voice translation-rule 2 >> >> rule 1 /972301\(3...\)/ /\1/ >> >> ! >> >> ! >> >> voice translation-profile ANI >> >> translate calling 1 >> >> ! >> >> voice translation-profile DNIS >> >> translate called 2 >> >> ! >> >> controller E1 0/2/0 >> >> pri-group timeslots 1-6,16 >> >> ! >> >> interface Loopback0 >> >> ip address 172.1.101.1 255.255.255.0 >> >> h323-gateway voip interface >> >> h323-gateway voip bind srcaddr 172.1.101.1 >> >> ! >> >> interface Serial0/2/0:15 >> >> no ip address >> >> encapsulation hdlc >> >> isdn switch-type primary-net5 >> >> isdn incoming-voice voice >> >> isdn outgoing display-ie >> >> *isdn outgoing ie redirecting-number **à** We need this to make the >> voicemail work in AAR mode* >> >> no cdp enable >> >> ! >> >> voice-port 0/2/0:15 >> >> translation-profile incoming DNIS >> >> translation-profile outgoing ANI >> >> ! >> >> ccm-manager music-on-hold >> >> ! >> >> ! >> >> sccp local Vlan203 >> >> sccp ccm 10.1.200.21 identifier 1 >> >> sccp ccm 10.1.200.20 identifier 2 >> >> sccp >> >> ! >> >> sccp ccm group 1 >> >> associate ccm 1 priority 1 >> >> associate ccm 2 priority 2 >> >> associate profile 1 register MTP001360f1a3e8 >> >> associate profile 2 register CFB001360f1a3e8 >> >> keepalive retries 5 >> >> switchover method immediate >> >> switchback method immediate >> >> switchback interval 5 >> >> ! >> >> dspfarm profile 1 transcode >> >> codec g711ulaw >> >> codec g711alaw >> >> codec g729ar8 >> >> codec g729abr8 >> >> maximum sessions 4 >> >> associate application SCCP >> >> ! >> >> dspfarm profile 2 conference >> >> codec g711ulaw >> >> codec g711alaw >> >> codec g729ar8 >> >> codec g729abr8 >> >> codec g729r8 >> >> codec g729br8 >> >> maximum sessions 2 >> >> associate application SCCP >> >> ! >> >> dial-peer cor custom >> >> name Emergency >> >> name Local >> >> name LongDistance >> >> name International >> >> ! >> >> ! >> >> dial-peer cor list Emergency >> >> member Emergency >> >> ! >> >> dial-peer cor list Local >> >> member Local >> >> ! >> >> dial-peer cor list LongDistance >> >> member LongDistance >> >> ! >> >> dial-peer cor list International >> >> member International >> >> ! >> >> dial-peer cor list Allowed >> >> member Emergency >> >> member Local >> >> member LongDistance >> >> member International >> >> ! >> >> dial-peer cor list Restricted >> >> member Emergency >> >> member Local >> >> ! >> >> ! >> >> dial-peer voice 1 pots >> >> corlist outgoing Emergency >> >> destination-pattern 911 >> >> incoming called-number . >> >> direct-inward-dial >> >> port 0/2/0:15 >> >> forward-digits all >> >> ! >> >> dial-peer voice 2 voip >> >> destination-pattern 3... >> >> voice-class codec 1 >> >> voice-class h323 1 >> >> session target ipv4:10.1.200.21 >> >> dtmf-relay h245-alphanumeric >> >> ip qos dscp cs3 signaling >> >> ! >> >> dial-peer voice 3 voip >> >> preference 1 >> >> destination-pattern 3... >> >> voice-class codec 1 >> >> voice-class h323 1 >> >> session target ipv4:10.1.200.20 >> >> dtmf-relay h245-alphanumeric >> >> ip qos dscp cs3 signaling >> >> ! >> >> dial-peer voice 4 pots >> >> corlist outgoing Emergency >> >> destination-pattern 9911 >> >> port 0/2/0:15 >> >> forward-digits 3 >> >> ! >> >> dial-peer voice 5 pots >> >> corlist outgoing Local >> >> destination-pattern 9[2-9]...... >> >> port 0/2/0:15 >> >> forward-digits 7 >> >> ! >> >> dial-peer voice 6 pots >> >> corlist outgoing LongDistance >> >> destination-pattern 91[2-9]..[2-9]...... >> >> port 0/2/0:15 >> >> forward-digits 11 >> >> ! >> >> dial-peer voice 7 pots >> >> corlist outgoing International >> >> destination-pattern 9011T >> >> port 0/2/0:15 >> >> prefix 011 >> >> ! >> >> dial-peer voice 8 pots >> >> destination-pattern 4... >> >> port 0/2/0:15 >> >> prefix 01185224334 >> >> ! >> >> ! >> >> call-manager-fallback >> >> max-conferences 8 gain -6 >> >> ip source-address 142.203.65.1 port 2000 >> >> max-ephones 3 >> >> max-dn 4 preference 2 >> >> voicemail 914082012600 >> >> alias 1 3001 to 3001 cfw 914082012801 timeout 10 >> >> alias 2 3002 to 3002 cfw 93013333 timeout 10 >> >> moh music-on-hold.au >> >> multicast moh 239.1.1.3 port 16384 route 142.203.65.1 172.1.101.1 >> >> cor incoming Allowed 1 3001 >> >> cor incoming Restricted 2 3002,3021 >> >> The alias 1 is pointing to a 914082012801, and in CCM there is a TP >> with 2801 translating to 3001. >> >> This is the output from the debug: >> >> Mar 21 16:54:40.781: ISDN Se0/2/0:15 Q931: RX <- SETUP pd = 8 callref >> = 0x00C4 >> >> Bearer Capability i = 0x8090A3 >> >> Standard = CCITT >> >> Transfer Capability = Speech >> >> Transfer Mode = Circuit >> >> Transfer Rate = 64 kbit/s >> >> Channel ID i = 0xA98381 >> >> Exclusive, Channel 1 >> >> Display i = 'HQ-Phone1' >> >> Calling Party Number i = 0x0081, '4082012001' >> >> Plan:Unknown, Type:Unknown >> >> Called Party Number i = 0x80, '9723013001' >> >> Plan:Unknown, Type:Unknown >> >> Mar 21 16:54:40.801: ISDN Se0/2/0:15 Q931: TX -> CALL_PROC pd = 8 >> callref = 0x80C4 >> >> Channel ID i = 0xA98381 >> >> Exclusive, Channel 1 >> >> Mar 21 16:54:40.809: ISDN Se0/2/0:15 Q931: TX -> ALERTING pd = 8 >> callref = 0x80C4 >> >> Progress Ind i = 0x8188 - In-band info or appropriate now available >> >> Mar 21 16:54:50.810: ISDN Se0/2/0:15 Q931: Applying typeplan for >> sw-type 0x12 is 0x0 0x0, Calling num 4082012001 >> >> Mar 21 16:54:50.814: ISDN Se0/2/0:15 Q931: Applying typeplan for >> sw-type 0x12 is 0x0 0x0, Called num 14082012801 >> >> Mar 21 16:54:50.814: ISDN Se0/2/0:15 Q931: TX -> SETUP pd = 8 callref >> = 0x00B9 >> >> Bearer Capability i = 0x8090A3 >> >> Standard = CCITT >> >> Transfer Capability = Speech >> >> Transfer Mode = Circuit >> >> Transfer Rate = 64 kbit/s >> >> Channel ID i = 0xA98386 >> >> Exclusive, Channel 6 >> >> Display i = 'HQ-Phone1' >> >> Calling Party Number i = 0x0081, '4082012001' >> >> Plan:Unknown, Type:Unknown >> >> Called Party Number i = 0x80, '14082012801' >> >> Plan:Unknown, Type:Unknown >> >> * Redirecting Number i = 0xFF, '3001' **à** This is the bug causing >> the problem and due we need the redirect number for AAR, the TP is not >> working * >> >> * Plan:Reserved, Type:Reserved as expected* >> >> Mar 21 16:54:50.866: ISDN Se0/2/0:15 Q931: RX <- CALL_PROC pd = 8 >> callref = 0x80B9 >> >> Channel ID i = 0xA98386 >> >> Exclusive, Channel 6 >> >> Mar 21 16:54:51.238: ISDN Se0/2/0:15 Q931: RX <- ALERTING pd = 8 >> callref = 0x80B9 >> >> Progress Ind i = 0x8188 - In-band info or appropriate now available >> >> Mar 21 16:54:51.518: ISDN Se0/2/0:15 Q931: RX <- CONNECT pd = 8 >> callref = 0x80B9 >> >> Mar 21 16:54:51.522: %ISDN-6-CONNECT: Interface Serial0/2/0:5 is now >> connected to 14082012801 N/A >> >> Mar 21 16:54:51.522: ISDN Se0/2/0:15 Q931: TX -> CONNECT_ACK pd = 8 >> callref = 0x00B9 >> >> Mar 21 16:54:51.530: ISDN Se0/2/0:15 Q931: TX -> CONNECT pd = 8 >> callref = 0x80C4 >> >> Mar 21 16:54:51.550: ISDN Se0/2/0:15 Q931: RX <- CONNECT_ACK pd = 8 >> callref = 0x00C4 >> >> Mar 21 16:54:51.554: %ISDN-6-CONNECT: Interface Serial0/2/0:0 is now >> connected to 4082012001 N/A >> >> Mar 21 16:54:55.238: ISDN Se0/2/0:15 Q931: RX <- DISCONNECT pd = 8 >> callref = 0x00C4 >> >> Cause i = 0x8290 - Normal call clearing >> >> Mar 21 16:54:55.238: %ISDN-6-DISCONNECT: Interface Serial0/2/0:0 >> disconnected from 4082012001 , call lasted 3 seconds >> >> Mar 21 16:54:55.242: ISDN Se0/2/0:15 Q931: TX -> RELEASE pd = 8 >> callref = 0x80C4 >> >> Mar 21 16:54:55.246: %ISDN-6-DISCONNECT: Interface Serial0/2/0:5 >> disconnected from 14082012801 , call lasted 3 seconds >> >> Mar 21 16:54:55.246: ISDN Se0/2/0:15 Q931: TX -> DISCONNECT pd = 8 >> callref = 0x00B9 >> >> Cause i = 0x8090 - Normal call clearing >> >> Mar 21 16:54:55.258: ISDN Se0/2/0:15 Q931: RX <- RELEASE_COMP pd = 8 >> callref = 0x00C4 >> >> Mar 21 16:54:55.270: ISDN Se0/2/0:15 Q931: RX <- RELEASE pd = 8 >> callref = 0x80B9 >> >> Mar 21 16:54:55.274: ISDN Se0/2/0:15 Q931: TX -> RELEASE_COMP pd = 8 >> callref = 0x00B9 >> >> As you can see from the information I am sending, due to the fact this >> is an H323 GW we need the ie redirect number commando to have the >> voicemail working in AAR mode, but doing this we broke the integration >> of the VM in SRST mode because we are sending the redirecting number >> with the wrong reason. >> >> Regards, >> >> Jose >> >> *From:* Cliff McGlamry [mailto:[email protected]] >> *Sent:* Sábado, Marzo 21, 2009 11:46 AM >> *To:* Jose Gregorio Linero (jlinero); Wesley Lim >> *Cc:* [email protected] >> *Subject:* Re: [OSL | CCIE_Voice] H323 GW SRST and AAR Voicemail >> Redirection >> >> Why don't you post the H323 config, and the output of the q931 trace >> (along with the info on what was originally dialed so we know what's >> supposed to go to voicemail)? It would be easier to help you if we >> could see what you are doing. >> >> ----- Original Message ----- >> >> *From:* Jose Gregorio Linero (jlinero) <mailto:[email protected]> >> >> *To:* Wesley Lim <mailto:[email protected]> >> >> *Cc:* [email protected] >> <mailto:[email protected]> >> >> *Sent:* Saturday, March 21, 2009 12:08 PM >> >> *Subject:* Re: [OSL | CCIE_Voice] H323 GW SRST and AAR Voicemail >> Redirection >> >> Hi all: >> >> I am stuck on this, any thoughts?, points of view?, have anybody >> faced this issue? >> >> Any point of view would very helpful. >> >> Regards, >> >> Jose >> >> *From:* Jose Gregorio Linero (jlinero) >> *Sent:* Sábado, Marzo 21, 2009 6:31 AM >> *To:* 'Wesley Lim' >> *Cc:* [email protected] >> <mailto:[email protected]> >> *Subject:* RE: [OSL | CCIE_Voice] H323 GW SRST and AAR Voicemail >> Redirection >> >> Hi: >> >> Actually I have tested the TP and CTI RP method when the BR1 GW is >> MGCP and it works fine, the problem I have is when the BR1 GW is >> H323, due to the fact that you need the command isdn outgoing ie >> redirect to make the VM work in AAR, in SRST you have an issue >> because no matter you are using TP or CTI RP method the GW is >> sending the 0xFF redirect reason and after you translate the >> ficticious number to one of the SRST that is not registered, Unity >> can see the wrong reason and you have the general greeting instead >> of the voicemail greeting, that is why I am asking. >> >> Have anybody tested the VM integration with an H323 GW and found >> this issue, maybe I am asking an stupid question, but I am testing >> different things and using an H323 GW I found this issue. Again, I >> have tested the CTI RP and TP before with an MGCP GW but is >> different, with an MGCP GW you do not need the command isdn >> outgoing ie redirect-number because all the control is in CCM, >> and when you are using with MGCP GW the voicemail in AAR works >> fine without this command, but in H323 GW you need this command to >> make the VM work in AAR, but in SRST you have a problem. >> >> Thanks in advance. >> >> Regards, >> >> Jose >> >> *From:* Wesley Lim [mailto:[email protected]] >> *Sent:* Sábado, Marzo 21, 2009 2:11 AM >> *To:* Jose Gregorio Linero (jlinero) >> *Cc:* [email protected] >> *Subject:* Re: [OSL | CCIE_Voice] H323 GW SRST and AAR Voicemail >> Redirection >> >> 2 other methods besides vm-integration: >> >> 1. Translation pattern >> >> 2. CTI RP >> >> This topic have been discussed many times, would suggest you to >> search for the alternative methods. >> >> On Sat, Mar 21, 2009 at 10:58 AM, Jose Gregorio Linero (jlinero) >> <[email protected] <mailto:[email protected]>> wrote: >> >> Hi: >> >> Looks like Ive never tested this before, I have configured BR1 GW >> as H323 GW, I am aware of the 0xFF redirect problem and I am >> testing AAR and SRST, due to the fact this is an H323 GW I need >> the command isdn outgoing ie redirect in the ISDN serial >> interface in order to make the redirection of a call to the >> correct voicemail in AAR mode, but I realized that this command >> affect the integration to the voicemail in SRST mode, my question >> is, having this scenario the only option we have is >> vm-integration?, because using this command in serial interface >> the translation pattern workaround does not work. >> >> Thanks in advance. >> >> Regards, >> >> Jose >> >> > >
smime.p7s
Description: S/MIME cryptographic signature
