[cisco-voip] Cisco-Acme T.38

[Tommy Schlotterer]

What protocol are you using on the VG 204?


Tommy Schlotterer | Systems Engineer
CCNA, CCNA Voice
48325 Alpha Dr. Ste. 150
Wixom, MI 48393
p 248.468.0710
e tschlotterer at netechcorp.com<mailto:tschlotterer at netechcorp.com>
w netechcorp.com<http://netechcorp.com/>
 [cid:image005.png at 01CFA5A1.CE2FF1C0]
[cid:image006.png at 01CFA5A1.CE2FF1C0]<https://www.linkedin.com/company/75843?trk=tyah&trkInfo=tarId%3A1397760375508%2Ctas%3Anetech%2Cidx%3A3-1-5> [cid:image007.png at 01CFA5A1.CE2FF1C0] <https://www.facebook.com/NetechCorporation>  [cid:image008.png at 01CFA5A1.CE2FF1C0] <https://twitter.com/netechcorp>  [cid:image009.png at 01CFA5A1.CE2FF1C0] <https://www.youtube.com/user/NetechCorporation>

From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Heim, Dennis
Sent: Tuesday, July 22, 2014 11:17 AM
To: cisco-voip at puck.nether.net
Subject: [cisco-voip] Cisco-Acme T.38

We have the call flow like this;

Fax Machine->VG202->CUCM->SIP Trunk->ACME->Verizon SIP Trunk->PSTN

We are trying to get T.38 to work in this mess, but we keep getting G.711. Normally, I am used to have a CUBE router instead of going through a SIP trunk to CUCM. Thoughts?

Dennis Heim | Collaboration Solutions Architect
World Wide Technology, Inc. | +1 314-212-1814
[cid:image010.png at 01CFA5A1.CE2FF1C0]<https://twitter.com/CollabSensei>
[cid:image011.png at 01CFA5A1.CE2FF1C0]<xmpp:dennis.heim at wwt.com>[cid:image012.png at 01CFA5A1.CE2FF1C0]<tel:+13142121814>[cid:image013.png at 01CFA5A1.CE2FF1C0]<sip:dennis.heim at wwt.com>


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20140722/b8fa6644/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.png
Type: image/png
Size: 42291 bytes
Desc: image005.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20140722/b8fa6644/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image006.png
Type: image/png
Size: 1012 bytes
Desc: image006.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20140722/b8fa6644/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image007.png
Type: image/png
Size: 804 bytes
Desc: image007.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20140722/b8fa6644/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image008.png
Type: image/png
Size: 1152 bytes
Desc: image008.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20140722/b8fa6644/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image009.png
Type: image/png
Size: 1485 bytes
Desc: image009.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20140722/b8fa6644/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image010.png
Type: image/png
Size: 3876 bytes
Desc: image010.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20140722/b8fa6644/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image011.png
Type: image/png
Size: 1389 bytes
Desc: image011.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20140722/b8fa6644/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image012.png
Type: image/png
Size: 1292 bytes
Desc: image012.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20140722/b8fa6644/attachment-0007.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image013.png
Type: image/png
Size: 1391 bytes
Desc: image013.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20140722/b8fa6644/attachment-0008.png>