[cisco-voip] SIP and MGCP routing on the same gateway

[Wes Sisk]

you may be mixing apples and oranges here.

mgcp is a master/slave protocol.  when a TDM interface is under mgcp 
control the gateway reports all events for that interface to its mgcp 
call agent and the call agent determines what to do. essentially the 
MGCP call agent controls the TDM interface.

SIP is a peer to peer protocol more similar to h.323.  SIP is not used 
to control TDM interfaces.  however, for the router to send call out TDM 
interface the TDM interface would have to be under control of the local 
router.

You could possibly accomplish this with a slightly obfuscated call flow:

a SIP endpoint could send invite to a router running SIP
if the SIP router is configured for IP-IP gateway it could send the call 
over a SIP trunk to CM, the mgcp call agent
CM receives the call and routes out the router TDM interface via MGCP.

it would be simpler to send your original SIP invite to the MGCP call 
agent, assuming the call agent can perform internetworking between the 
protocols.



In your original scenario you could have a router doing SIP and H.323 
and you would be fine.  So long as only SIP and H323 are used the TDM 
interfaces on the router are under local call control.

/Wes

On Tuesday, February 10, 2009 9:21:46 AM, 
matthew.richards at nominet.org.uk wrote:
> Hi
>
> Does anyone know if it is possible to get SIP and MGCP to co-exist, on the
> same gateway ideally without forcing fixed numbers of channels to be
> allocated to one or other protocol.
>
> It appears that the configuration dedicates the whole ISDN interface to
> MGCP, and prevents any channels from being used for SIP.
>
> One way of doing this is to convert our entire system to SIP (which will
> happen but not for a while), and I would like to do this without this
> conversion.
>
> Can anyone help?
>
> Matt Richards
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>