Send cisco-voip mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://puck.nether.net/mailman/listinfo/cisco-voip
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of cisco-voip digest..."
Today's Topics:
1. SRST: re-routing autoattendant (Dave Wolgast)
2. Re: VG224 to RightFax communication error issue (Buchanan, James)
3. IPPA doesn't get custom layout data while ringing after
upgrade to ccx 8.5 (Ed Leatherman)
4. UCCX CSS ? (Countryman, Edward)
----------------------------------------------------------------------
Message: 1
Date: Mon, 21 Jan 2013 10:12:31 -0500
From: Dave Wolgast <[email protected]>
To: "Cisco VOIP Newsletter - puck.nether.net"
<[email protected]>
Subject: [cisco-voip] SRST: re-routing autoattendant
Message-ID:
<cahozw-1__ehbz6susqr8vhnozk4g+nw3scx3kt+agbxc2or...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
I have set up a branch site using IOS Telephony Service for SRST (rather
then call-manager-fallback) on an H.323 gateway. The branch has an
automated attendant on Unity Connection at a central site which is reached
via a CUCM CTI RP with CFA to UCxn.
In the event of a SRST activation, I would like all automated attendant
calls to go to the receptionist's DN, but I can't figure out how to
redirect the main number to her phone. I see that call-manager-fallback has
the alias command. Is there something similar in telephony-service?
--
Dave Wolgast
Livonia, NY
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130121/36a31a72/attachment-0001.html>
------------------------------
Message: 2
Date: Mon, 21 Jan 2013 15:30:54 +0000
From: "Buchanan, James" <[email protected]>
To: "Kalyan Iyer (AM)" <[email protected]>,
"[email protected]" <[email protected]>
Subject: Re: [cisco-voip] VG224 to RightFax communication error issue
Message-ID:
<12d6a6a157b44348974e5ed93738628c2536d...@hqexchmbx03.presidio.corp>
Content-Type: text/plain; charset="utf-8"
I had the same problems using MGCP recently and H323. I upgraded to 15.1(4)M4
(I think) AND changed to T.38 version 3. This fixed my issues.
James Buchanan | Sr. Network Engineer
Presidio | www.presidio.com<http://www.presidio.com>
12 Cadillac Drive Suite 130, Brentwood, TN 37027
D: 615.866.5729 | C: 931.797.2326 | F: 615.866.5781 |
[email protected]<mailto:[email protected]>
[Be Secure In The Knowledge]<http://www.presidio.com>
Follow us:
[Follow Presidio on Twitter]<http://www.twitter.com/presidio>
From: [email protected]
[mailto:[email protected]] On Behalf Of Kalyan Iyer (AM)
Sent: Friday, January 18, 2013 8:49 PM
To: [email protected]
Subject: [cisco-voip] VG224 to RightFax communication error issue
I have a customer that has the following setup
Analog Fax -- > VG224 ---SCCP--- > CUCM ---H323--- > RightFax (virtual server)
Or
Analog Fax --- > EVM card on router --- H323 --- > CUCM ---H323--- > RightFax
(virtual server)
When they try to fax in to the RightFax server in both the scenarios, they hear
the fax tone but get a communication error. I was told that when they were
using SIP between CUCM and RightFax, it worked well. They are however able to
fax out from the RightFax server to the fax machine.
The VG224 configuration is attached. Any help will be appreciated.
Thanks
This message w/attachments (message) is intended solely for the use of the
intended recipient(s) and may contain information that is privileged,
confidential or proprietary. If you are not an intended recipient, please
notify the sender, and then please delete and destroy all copies and
attachments. Please be advised that any review or dissemination of, or the
taking of any action in reliance on, the information contained in or attached
to this message is prohibited.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130121/b7639592/attachment-0001.html>
------------------------------
Message: 3
Date: Mon, 21 Jan 2013 11:13:33 -0500
From: Ed Leatherman <[email protected]>
To: Cisco VOIP <[email protected]>
Subject: [cisco-voip] IPPA doesn't get custom layout data while
ringing after upgrade to ccx 8.5
Message-ID:
<CAFC4dspZcscrgXbd4htk=tb370a72ms-c4qc+zockcvri9y...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Anyone run into a problem with IP Phone agent after upgrading to UCCX 8.5?
We just upgraded from 7.0 to 8.5.
We had one of our call centers configured to display the custom layout data
so the agent could see which CSQ the call came from. Worked fine in v7.
Now the data is still getting to the phone after the call begins but the
agent has to push cdata a softkey to see it. So I believe the layout is
configured correctly and in the script correctly, it just no longer pops
when the phone is ringing.
It seems like it could be a permissions issue where UCCX can't pop the data
to the phone anymore. I checked that telecaster was still associated to the
phones, and also looked in desktop admin to see if the telecaster user was
still specified. I explicitly set the password for that account to be sure
but haven't yet restarted the CAD services (will do that tonight after they
close).
Curious if anyone else had run into this problem before.
--
Ed Leatherman
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130121/2e0335c3/attachment-0001.html>
------------------------------
Message: 4
Date: Mon, 21 Jan 2013 10:14:00 -0600
From: "Countryman, Edward" <[email protected]>
To: <[email protected]>
Subject: [cisco-voip] UCCX CSS ?
Message-ID:
<3E508304295FC04988DFEEA1A2F177C3470B4B@AEXMV22.phnet.phroot.local>
Content-Type: text/plain; charset="utf-8"
Does anyone know if it?s possible to have a UCCX application use a different
CSS for redirecting a call then the one associated with the originating party?
(We are on version 7.0)
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130121/a092c3b9/attachment-0001.html>
------------------------------
_______________________________________________
cisco-voip mailing list
[email protected]
https://puck.nether.net/mailman/listinfo/cisco-voip
End of cisco-voip Digest, Vol 111, Issue 20
*******************************************
