Exactly what problems are you experiencing? One way audio? No ringback? DTMF issues etc?
Have you tried voice rtp send-recv? This is used for cut Through Two-Way Audio Early. Not sure it will help though. http://www.cisco.com/en/US/docs/ios/12_2/voice/command/reference/vrf_t.html#wp1076026 /Roger On Mon, Nov 15, 2010 at 10:36 AM, Marco Marzetti <[email protected]> wrote: > > Hello, > > I have a problem with SIP to ISDN internetworking on Cisco IOS. > I'm unable to receive early-media messages from the ISDN side of the call. > Hardware and software versions are: Cisco 2800 Software > (C2800NM-ENTSERVICES-M), Version 12.4(20)T6, RELEASE SOFTWARE (fc2). > > # debug isdn q931 int Se0/1/0:15 > Nov 15 10:06:54.437 CET: ISDN Se0/1/0:15 Q931: Applying typeplan for > sw-type 0x12 is 0x0 0x1, Calling num 03631970XXX > Nov 15 10:06:54.441 CET: ISDN Se0/1/0:15 Q931: Sending SETUP callref = > 0x0D0D callID = 0x980D switch = primary-net5 interface = User > Nov 15 10:06:54.441 CET: ISDN Se0/1/0:15 Q931: TX -> SETUP pd = 8 callref > = 0x0D0D > Bearer Capability i = 0x8090A3 > Standard = CCITT > Transfer Capability = Speech > Transfer Mode = Circuit > Transfer Rate = 64 kbit/s > Channel ID i = 0xA9839F > Exclusive, Channel 31 > Calling Party Number i = 0x0180, '03631970XXX' > Plan:ISDN, Type:Unknown > Called Party Number i = 0x81, '199151119' > Plan:ISDN, Type:UnknownsipSPIUpdateRtcpSession: sx79861: > started RTP > timer in state STATE_SENT_ALERTING > > Nov 15 10:06:54.457 CET: ISDN Se0/1/0:15 Q931: RX <- SETUP_ACK pd = 8 > callref = 0x8D0D > Channel ID i = 0xA9839F > Exclusive, Channel 31 > > > Nov 15 10:06:56.745 CET: ISDN Se0/1/0:15 Q931: RX <- CALL_PROC pd = 8 > callref = 0x8D0D > Nov 15 10:07:18.206 CET: ISDN Se0/1/0:15 Q931: RX <- ALERTING pd = 8 > callref = 0x8D0D > Nov 15 10:07:18.302 CET: ISDN Se0/1/0:15 Q931: RX <- CONNECT pd = 8 > callref = 0x8D0D > Nov 15 10:07:18.302 CET: %ISDN-6-CONNECT: Interface Serial0/1/0:30 is now > connected to 199151119 N/A > Nov 15 10:07:18.302 CET: %ISDN-6-CONNECT: Interface Serial0/1/0:30 is now > connected to 199151119 N/A > Nov 15 10:07:18.302 CET: %ISDN-6-CONNECT: Interface Serial0/1/0:30 is now > connected to 199151119 N/A > Nov 15 10:07:18.302 CET: ISDN Se0/1/0:15 Q931: TX -> CONNECT_ACK pd = 8 > callref = 0x0D0DsipSPIUpdateRtcpSession: sx79861: started RTP timer in > state STATE_SENT_ALERTING > > Nov 15 10:07:21.294 CET: %ISDN-6-CONNECT: Interface Serial0/1/0:30 is now > connected to 199151119 N/A > Nov 15 10:07:21.294 CET: %ISDN-6-DISCONNECT: Interface Serial0/1/0:30 > disconnected from 199151119 , call lasted 2 seconds > Nov 15 10:07:21.294 CET: ISDN Se0/1/0:15 Q931: TX -> DISCONNECT pd = 8 > callref = 0x0D0D > Cause i = 0x8090 - Normal call clearing > Nov 15 10:07:21.306 CET: ISDN Se0/1/0:15 Q931: RX <- RELEASE pd = 8 > callref = 0x8D0D > Nov 15 10:07:21.306 CET: ISDN Se0/1/0:15 Q931: TX -> RELEASE_COMP pd = 8 > callref = 0x0D0D > > The router places the call to our public switch and cut-through the voice > path only after the CONNECT message ignoring the CALL_PROC messages and the > relative early-audio > stream. > Looking at the SIP side of the call no "SIP 183 Progress" is sent by the > router between the "Trying" and the "Ringing" messages. > > I would expect the router to generate proper SIP signaling and cut-through > in the backward direction the voice path after the CALL_PROC message has > been received. > > Any help? > > Thank you > _______________________________________________ > cisco-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ > _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
