<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal>Cats & Dogs living together, it’s the apocalypse as we know it…<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>So I’m working with a 311 center and someone had the brilliant idea, “why can’t I just text my problem instead of calling?”. Seems logical, I have both options on a cell phone. Why not on a PRI or land based phone?<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Obviously the technology isn’t there to do it natively since I believe most cells are doing it via IP and PRIs are still old-school. But with the advent of things like Google talk and IP/SIP Trunks it looks like the functionality to work around the Telco’s shortcomings is actually within the realm of possibilities.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Has anyone gotten this to work, and better yet, gotten it to work on a med-high volume number? We’re averaging about 10k calls a month on the line we want to use and I feel like porting that number through Google Voice first and then forwarding to our PRI just brings up more potentials for single points of failure. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>The alternative is just to use a different number, but we were trying to keep it simple.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I’m guessing while UCCX/CUCM has the capability to handle e-mails, it doesn’t have the ability to handle texts as well.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Any other ideas I might have missed?<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>JM<o:p></o:p></p></div></body></html>