Hi Drake,
Regarding your 1st question, when you upload any audio source/prompt to call
manager it converts/translate to G711, G729 codecs by itself. So even if you
upload a g711 codec, it will be available for both g729 and g711 moh stream.
Regarding your 2nd question, ringback while user is in queue, i tried the CVL
sol (putting the ringback prompt in network on hold and using the script same
as of lab7) but it did not work for me. Then i tried below which worked for me.
1. upload the ringback prompt to CUCM.
2. Enabled g729 and g711 in IPVMA service parameters in call manager.
3. on UCCX, select G729 codec and restart node manager.
4. Assigned the prompt to "USER ON HOLD" in UCCX CTI/JTAPI Ports.
5. In the script, under queuing section, I added "call hold" after waiting in
queue prompt is played. And also after delay, I added "call unhold". Logic is-
i am manually putting the call on hold/unhold using script while in queue and
it uses "user on hold" prompt which is ringback.
Let me know if this works for you.
However i have come across several forums which says if you do as per CVL
solutions you will get 100% in uccx section however i don't feel this since its
solution didn't work for me.
Thanks and Regards,
Piyush Jain
Message: 3
Date: Sun, 19 May 2013 19:53:15 +0530
From: Drake J
To: ccie_voice@onlinestudylist.com
Subject: [OSL | CCIE_Voice] UCCX questions / G729 / ringback
Message-ID:
Content-Type: text/plain; charset="iso-8859-1"
hi All,
I have 2 questions here...
1) If UCCX was supposed to use g729 codec . Then if we are using
unity connection or uccx to record prompts it would record this prompts
in g711ulaw. Therefore the prompts played from the script will be in
g711ulaw when the uccx is setup for g729 .What is the way around?
2) How do we make callers hear ringback with they wait in a UCCX queue
for their call to be answered by agents?
Please assist.
Regards,
Drake
-- next part --
An HTML attachment was scrubbed...
URL:
--
Message: 4
Date: Sun, 19 May 2013 09:30:25 -0500
From: Bill
To: Ravindra Lakpriya
Cc: "ccie_voice@onlinestudylist.com"
Subject: Re: [OSL | CCIE_Voice] Voice translation issue
Message-ID: <4c0778d6-2497-4e32-bbd7-57f3e4d30...@gmail.com>
Content-Type: text/plain; charset="us-ascii"
dial-peer voice 9911 pots
translation-profile outgoing 9911
destination-pattern 9911$
port 0/0/0:23
forward-digits 3
Sent from my iPad
On May 19, 2013, at 9:07 AM, Ravindra Lakpriya wrote:
> dial-peer voice 9911 pots
> translation-profile outgoing 9911
> destination-pattern 9911$
> port 0/0/0:23
-- next part --
An HTML attachment was scrubbed...
URL:
--
Message: 5
Date: Sun, 19 May 2013 09:33:02 -0500
From: Bill
To: Ravindra Lakpriya
Cc: "ccie_voice@onlinestudylist.com"
Subject: Re: [OSL | CCIE_Voice] Voice translation issue
Message-ID: <9ae17c84-7792-49b3-952d-b18632a6e...@gmail.com>
Content-Type: text/plain; charset="us-ascii"
voice translation-rule 8
rule 1 // // type any unknown plan any isdn
rule 2 /^1...$/ /617394\0/ type any subscriber plan any isdn
Sent from
my iPad
On May 19, 2013, at 9:07 AM, Ravindra Lakpriya wrote:
> In the dial peer configure no digit strip. :)
>
> On Sun, May 19, 2013 at 5:47 PM, Martin Sloan wrote:
>> I have a voice translation rule in place for '9911' calls on BR1 during
>> SRST. I'm running into some odd behavior (from my perspective) and I'm
>> hoping it's a config issue I'm just not spotting. I have the translation
>> profile applied to the dial peer and the only other translation that would
>> be in the calling path is on the voice port but even that one is applied to
>> inbound calls for stripping down to 4 digits. Here's the config related to
>> this dial-peer:
>>
>> voice translation-rule 8
>> rule
1 /^9911$/ /911/ type any unknown plan any isdn
>> rule 2 /^1...$/ /617394\0/ type any subscriber plan any isdn
>>
>> voice translation-profile 9911
>> translate calling 8
>> translate called 8
>>
>> dial-peer voice 9911 pots
>> translation-profile outgoing 9911
>> destination-pattern 9911$
>> port 0/0/0:23
>>
>> BR1-RTR#test voice translation-rule 8 9911
>> Matched with rule 1
>> Original number: 9911 Translated number: 911
>> Original number type: none Translated number type: unknown
>> Original number plan: none Translated number plan: isdn
>>
>> -Debug ISDN q931-
>>
>> Calling Party Number i = 0x4181, '6173941002'
>>
Plan:ISDN, Type:Sub