[cisco-voip] Fwd: volume 1 section 4 of study guide. ICT / SIP trunk

[Michael Thompson]

I guess I better get used to the subtle verbiage like that. 

I read through it a couple times and for some reason I read it that the
IPIPGW would be in the middle of alls calls and the CME-IPIPGW would be SIP
and the IPIPGW-CCM would be H.323.

Now that I reread it, I see that all calls will start as H.323 (whether
sourced from CCM or CME) and will end up as SIP on the receiving side.

Thanks for the quick response.

-----Original Message-----
From: Jonathan Charles [mailto:jonvoip at gmail.com] 
Sent: Sunday, July 27, 2008 12:02 PM
To: Michael Thompson
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Fwd: volume 1 section 4 of study guide. ICT / SIP
trunk

The task states that calls will be coming from CME to the IPIPGW via
H323 and going to CCM via SIP... so, we need a SIP trunk from CCM to
the IPIPGW...

On Sun, Jul 27, 2008 at 10:51 AM, Michael Thompson
<mthompson729 at gmail.com> wrote:
> I'm looking through the proctors guide on the explanation of the IPIPGW
and
> there's one piece that doesn't make sense.
>
> Task 4.9 has you create both an H.323 (non-GK) ICT to the IPIPGW, that
part
> make sense.
>
> what confuses me is why we're creating  SIP trunk on CCM if traffic from
BR2
> should be coming via the IPIPGW.  shouldn't that IPIPGW be translating the
> traffic from SIP to H.323?  I could see if it was GK controlled ip calls,
> then the traffic comes across as native SIP, but this seems odd to me.
>
> anyone have any insight?
>
> Thanks,
> Mike
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>