[cisco-voip] SIP Trunks config in CCM in relation to Vail Systems SIP TIM

Tue Apr 18 11:42:51 EDT 2006

Hi Rob,

I am very interested in your experience of MS Speech Server integrated with
CCM thru SIP trunk. My environment is CCM 4.0(2) + MGCP gateway, and I tried
to configure the sip function working with Microsoft Office Communicator
(LCS server). Is there any special configuration needed in MS server &
gateway? I'm using SIP trunk pointing to LCS server, and the server
configure the SIP gateway too. But right now both the inbound call and
outbound call from/to Office Communicator is not working. I can see the
missed call log in IP Phone but I didn't hear it ringing. Below is my
gateway configuration, please kindly help to check is anything wrong. Thanks
a lot ~

voice-card 1
!
ip subnet-zero
ip tcp synwait-time 13
!
!
ip cef
!
!
!
isdn switch-type primary-qsig
!
!
voice call send-alert
voice rtp send-recv
!
voice service voip
 sip
  session transport tcp
!
!
ccm-manager fallback-mgcp
ccm-manager mgcp
ccm-manager music-on-hold
ccm-manager config server 10.1.254.250
ccm-manager config
!
!
controller T1 1/0
 framing esf
 crc-threshold 320
 clock source internal
 linecode b8zs
 pri-group timeslots 1-24 service mgcp
!
!
!
interface FastEthernet0/1
 ip address 10.8.128.250 255.255.255.0
 ip route-cache flow
 speed 100
 full-duplex
 no cdp enable
!
interface Serial1/0:23
 no ip address
 no logging event link-status
 isdn switch-type primary-qsig
 isdn protocol-emulate network
 isdn incoming-voice voice
 isdn bind-l3 ccm-manager
 no cdp enable
!
ip classless
ip route 10.0.0.0 255.0.0.0 10.8.128.1
!
!
voice-port 1/0:23
 cptone TW
!
voice-port 3/0/0
!
voice-port 3/0/1
!
voice-port 3/1/0
!
voice-port 3/1/1
!
mgcp
mgcp call-agent CM 2427 service-type mgcp version 0.1
mgcp rtp unreachable timeout 1000 action notify
mgcp package-capability rtp-package
mgcp package-capability sst-package
no mgcp package-capability fxr-package
no mgcp timer receive-rtcp
mgcp sdp simple
mgcp fax t38 inhibit
mgcp rtp payload-type g726r16 static
!
mgcp profile default
!
!
!
!
dial-peer voice 1 pots
 application session
 destination-pattern 1T
 port 1/0:23
!
dial-peer voice 9 pots
 application session
 destination-pattern 9T
 port 1/0:23
!
dial-peer voice 424 voip
 application session
 destination-pattern 2....
 session protocol sipv2
 session target ipv4:10.1.254.100
 session transport tcp
!
dial-peer voice 2 pots
 application mgcpapp
 direct-inward-dial
 port 1/0:23
!
sip-ua
 retry invite 2
 retry response 2
 retry bye 2
 retry cancel 2
 timers trying 100
 sip-server ipv4:10.1.254.100

Regards,

Alan

2006/4/18, Leetun, Rob <rleetun at co.boulder.co.us>:
>
>  Hi Wes,
>
> True.  I have a Microsoft Speech Server connected to our CM environment (
> 4.1.3) through a SIP trunk.  It works pretty nice.  We are looking at
> IPICS, which from what I understand we will be using the SIP trunking as
> well with this product.
>
> Rob
>
>  ------------------------------
> *From:* Wes Sisk [mailto:wsisk at cisco.com]
> *Sent:* Tuesday, April 18, 2006 7:44 AM
> *To:* Alan Su
> *Cc:* Leetun, Rob; cisco-voip at puck.nether.net
> *Subject:* Re: [cisco-voip] SIP Trunks config in CCM in relation to Vail
> Systems SIP TIM
>
>
>  Alan,
>
> SIP trunk will only work to a proxy server.  it will not work for
> endpoints.  CM5.0 adds SIP lineside support for to allow direct
> registration of SIP clients and adds the ability for CM to function as a SIP
> back to back user agent.
>
> /Wes
>
> Alan Su wrote:
>
> Hi Wes,
>
> I just have a question regarding CCM 4.0 intergrated with SIP, I see lots
> of document say that CCM5.0 is fully compatible with SIP, but can I do it
> in CCM 4.0 by using SIP trunk?
> My customer is looking for a soultion that some of the users in
> organization will use SIP phone and others will use Cisco IP Phone, is it
> possible to deploy this solution in CCM 4.0? I have tried to configure CCM
> working with MS Office Communicator (act like SIP softphone), not worked
> well, I can see incoming call from Office Communicator but can't answer it.
>
> Thanks so much.
>
>
> Regards,
>
> Alan
>
>
> 2006/4/3, Wes Sisk <wsisk at cisco.com>:
> >
> > I have not used the Vail Systems SIP TIM but the CM SIP trunk is pretty
> > basic.   Configure it with a destination address = IP address of your
> > destination device, set the port number (5060 by default), select TCP or
> > UDP, check the box for MTP required (note default CM MTP resources are
> > g711 only..  you will need hardware DSP resources for g729)
> >
> > then create a route pattern pointing to the SIP trunk. give it a
> > partition if desired. give your originating device a calling search
> > space that includes that partition.
> >
> > I have been testing the SIP trunk last few weeks and it seems to work
> > well.
> >
> > /Wes
> >
> >
> > Leetun, Rob wrote:
> > > Good afternoon,
> > >
> > > Anyone have experience in the configuration of Callmanager 4.1.3 for a
> > > SIP trunk to connect to a Vail Systems SIP TIM system?  I am trying to
> >
> > > figure out what are the requirements for the configuration of the
> > > CallManager environment.  I configured a SIP trunk, but wonder how it
> > is
> > > going to connect to the SIP TIM system through port 5060?
> > >
> > > Thanks.
> > >
> > > Rob
> > >
> > > _______________________________________________
> > > cisco-voip mailing list
> > > cisco-voip at puck.nether.net
> > > https://puck.nether.net/mailman/listinfo/cisco-voip<http://portal.mxlogic.com/redir/?atXKnsvshKrjLtYQsFIcTpdAVPmEBCbdSaY3ivNU6U9GX33VkDa3JsJaBGBPdpb6XZuZQrFTjLsTsSoFaxk5mBiRundI6zBVYSyyM-OUeupKr73zobZ8Qg6BKQGmGncRAIqnjh0c1Emd409yT0HgQgmH1Sh4Qgiwq818i6Ph1a1EwzV-PBm1EwDkQg1Dp7Cy0obkDWJ3h0c1Emd4093hITfM-u0USyrjdFTpopvjuvhdFkVV>
> > >
> >
> > _______________________________________________
> > cisco-voip mailing list
> > cisco-voip at puck.nether.net
> > https://puck.nether.net/mailman/listinfo/cisco-voip<http://portal.mxlogic.com/redir/?atXKnsvshKrjLtYQsFIcTpdAVPmEBCbdSaY3ivNU6U9GX33VkDa3JsJaBGBPdpb6XZuZQrFTjLsTsSoFaxk5mBiRundI6zBVYSyyM-OUeupKr73zobZ8Qg6BKQGmGncRAIqnjh0c1Emd409yT0HgQgmH1Sh4Qgiwq818i6Ph1a1EwzV-PBm1EwDkQg1Dp7Cy0obkDWJ3h0c1Emd4093hITfM-u0USCrjdFTpopvjuvhdFkVV>
> >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20060418/382c59bb/attachment.html 