[cisco-voip] Edify Workforce and CCM 4.1.3

[Erick Bergquist]

Also, if you are testing with H.323 still and have a FXS port, you can try to see if it works fine or not with just the router (pots to pots). 
 
----- Original Message ----
From: Jonathan Charles <jonvoip at gmail.com>
To: "Wydra, Jason" <jason.wydra at berbee.com>
Cc: Erick Bergquist <erickbe at yahoo.com>; cisco voip <cisco-voip at puck.nether.net>
Sent: Friday, December 1, 2006 1:02:22 PM
Subject: Re: [cisco-voip] Edify Workforce and CCM 4.1.3

Do you see anything with a csim start on the gateway? Is CCM communicating with this gateway if you do a debug ccapi inout, do you see anything?

Yeah, I was working with Erick once for a customer and they were connecting to a legacy PBX (which we didn't support), but for some reason the thing was looking for a hook-flash on connect... dunno why.


Also not sure how to send it...

Does the box you are connecting to show anything (connect attempts, port status, etc... maybe the bloody thing isn't answering?)



Jonathan


On 12/1/06, Wydra, Jason <jason.wydra at berbee.com> wrote:




















Yeah, controller is set up correctly as
far as I can tell. But you're right; there are a ton of variables.


 


I set up a dial-peer like you said…
36XX (forward digits all). Hookflash?????


 


I did NOT see a CAS channel go off hook.
That was one of the notes I made. Obviously that draws a flag. Debugs prove
that the call gets to the gateway in H323 mode but I can't determine anything
from the debug. I'm going back there tomorrow to take another stab at it.


 


Thanks,


 




Jason Wydra


Berbee


Cisco Voice Engineer


8725 West Higgins Road,
  Suite 700


Chicago
, Il. 60631


IP phone 773.867.6084


Cell 630-209-9792


Jason.Wydra at berbee.com



www.berbee.com



 


















From: Jonathan Charles
[mailto:jonvoip at gmail.com] 

Sent: Friday, December 01, 2006
12:47 PM

To: Wydra, Jason

Cc: cisco-voip at puck.nether.net

Subject: Re: [cisco-voip] Edify
Workforce and CCM 4.1.3





 


No idea what it is, but
since they are T1-CAS wink-start, and I presume the controller is set up
correctly (right number of channels, right signaling etc.)...



I would definitely start this as H.323 and create a dial-peer that points to
the T1-CAS and the a destination pattern that people used to dial from the old
PBX... 



Next I would play with the number of digits being sent... is it possible that
this thing is waiting for digits, or maybe a hook-flash?



When you dial the number, do you see the T1-CAS go off-hook, or does it stay
idle? Are digits being sent down it? 



There are a lot of variables here...







Jonathan




On 12/1/06, Wydra,
Jason <jason.wydra at berbee.com
> wrote:






I'm
trying to integrate a 3845 T1-CAS (E&M-Wink-Start) with a legacy Edify IVR
system. I'm using CCM 4.1.3. I tried doing h323 and MGCP for the 3845 but can't
seem to get this to work. When I call the pilot numbers from an IP phone all I
get is a slow busy. The trace and debugs aren't telling me a whole lot. Does
anyone have any experience with this type of integration? I have no experience
with Edify. It runs on a Windows NT server with two T1 interface cards on the
back. The currently have it tied into a Fujitsu PBX.


 


Regards,


 


Jason
Wydra


Berbee


Cisco
Voice Engineer


8725 West Higgins Road, Suite 700


Chicago, Il
 . 60631


IP
phone 773.867.6084


Cell
630-209-9792


Jason.Wydra at berbee.com



www.berbee.com



 





 










_______________________________________________

cisco-voip mailing list

cisco-voip at puck.nether.net

https://puck.nether.net/mailman/listinfo/cisco-voip









 




















 
____________________________________________________________________________________
Do you Yahoo!?
Everyone is raving about the all-new Yahoo! Mail beta.
http://new.mail.yahoo.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20061201/1afc26ac/attachment.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.jpg
Type: image/jpeg
Size: 2615 bytes
Desc: not available
Url : https://puck.nether.net/pipermail/cisco-voip/attachments/20061201/1afc26ac/attachment.jpg 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.jpg
Type: image/jpeg
Size: 2615 bytes
Desc: not available
Url : https://puck.nether.net/pipermail/cisco-voip/attachments/20061201/1afc26ac/attachment-0001.jpg