Re: [cisco-ttl] Voice çağrı gecikmesi!

From: ceyhun çatalbaş (ccatalbas@teknotel.net)
Date: Thu Mar 27 2003 - 10:09:18 GMT

  • Next message: ZaferP@koc.net: "RE: [cisco-ttl] Voice çağrı gecikmesi!"

    MessageHocam, call rsvp-sync resv-timer 1 komutuyla hallettim.
    Ama şöyle bir durum varki bunu ubr ile birlikte ubr la konuşan tüm routerlarda girmem gerekti.
    Yorumun nedir?

    Hocam conflar aşağıdaki gibi,

    924

    voice-port 0
     input gain -2
     output attenuation 0
     
    !
    voice-port 1
     input gain -2
     output attenuation 0
     

    dial-peer voice 1 pots
     destination-pattern 80
     port 0
    !
    dial-peer voice 2 pots
     destination-pattern 81
     port 1

    interface Ethernet0
     ip address ************ 255.255.255.248
     ip nat inside
     no ip route-cache
     no ip mroute-cache

    dial-peer voice 6 voip
     destination-pattern 3848761
     session target ipv4:*************
     dtmf-relay cisco-rtp h245-signal
     req-qos controlled-load
    !
    dial-peer voice 5 voip
     destination-pattern 3848760
     session target ipv4:**************
     dtmf-relay cisco-rtp h245-signal
     req-qos controlled-load

    3660

    interface FastEthernet0/0
     ip address ************ 255.255.252.0
     load-interval 60
     duplex auto
     speed auto
    !
    voice-port 6/0/0
     cptone TR

    !
    voice-port 6/0/1
     cptone TR
     
    !
    dial-peer cor custom
    !
    !
    !
    dial-peer voice 1 pots
     destination-pattern 3885547
     port 6/0/0
    !
    dial-peer voice 2 pots
     destination-pattern 3885591
     port 6/0/1
    !
    dial-peer voice 3 voip
     destination-pattern 3848760
     voice-class codec 99
     session target ipv4:***********
     dtmf-relay cisco-rtp h245-signal
     req-qos controlled-load
    !
    dial-peer voice 4 voip
     destination-pattern 3848761
     voice-class codec 99
     session target ipv4:*****************
     dtmf-relay cisco-rtp h245-signal
     req-qos controlled-load
    !
    dial-peer voice 5 voip
     destination-pattern 80
     voice-class codec 99
     session target ipv4:***************
     req-qos controlled-load
    !
    dial-peer voice 6 voip
     destination-pattern 81
     voice-class codec 99
     session target ipv4:****************
     req-qos controlled-load
    !
      ----- Original Message -----
      From: ZaferP@koc.net
      To: cisco-ttl@yahoogroups.com
      Sent: Thursday, March 27, 2003 1:18 PM
      Subject: RE: [cisco-ttl] Voice çağrı gecikmesi!

      Selam,

      Burda RSVP ile ilgili bir sorun var sanırım. RSVP reserveation yapamıyor gibi. Dial-peer ve interface tanımlarını ekleyebilir misin?

        -----Original Message-----
        From: ceyhun çatalbaş [mailto:ccatalbas@teknotel.net]
        Sent: Thursday, March 27, 2003 1:06 PM
        To: cisco-ttl@yahoogroups.com
        Subject: Re: [cisco-ttl] Voice çağrı gecikmesi!

        Hocam,
         debug sonucu aşağıdaki gibi,
        gecikmenin olduğu yeri görmüşsündür.
        Yalnız şöyle bir durum var, aynı porta(3660 daki) diğer bir noktadan(1760) ulaştığınızda gecikme olmuyor!

        20:21:00: QoSpcb : 0x80D2DC3C
        20:21:00: Response Status : 0
        20:21:00: calc_ip_overhead: ipPayLoadSpec is PAYLOAD_SIZE
        20:21:00: calc_ip_overhead:packetization period 20, ip overhead 16
        20:21:00: Starting timer for call with CallId 0x61 for 10000 secs
        20:21:00: Handling QoS Primitive QoS Listen
        20:21:00: Establishing RSVP RESV state:
        20:21:00: For streams from ************* to ****************:16834
        20:21:00: ----- average_bit rate 24 burst_byte 120
        20:21:00: RSVP Confirmation required
        20:21:00: Lookup to be done on hashkey 0x61 in hash table 0x80D2BF54
        20:21:00: Hashed entry 0x61 in call table 0x80D2BF54
        20:21:00: Handling QoS Primitive QoS Resv
        20:21:00: Initiating RVSP PATH messages to be Sent :
        20:21:00: Advertizing for streams to ***************:17294 from *****************:16834
        20:21:00: ----- average_bit rate 24 burst_byte 120
        20:21:10: Reservation Timeout occured for CallId 0x61
        20:21:10: cc_api_forward_setup_ind (vdbPtr=0x80CD71B4, callInfo={called=80,called_oct3=0x81,calling=3885591,calling_oct3=0x80,calling_oct3a=0x0,calling_xlated=false,subscriber_type_str=Unknown,fdest=1,peer_tag=4, prog_ind=3},callID=0x61)

        20:21:10: cc_process_call_setup_ind (event=0x80D3FDF4)
        20:21:10: >>>>CCAPI handed cid 97 with tag 4 to app "DEFAULT"
        20:21:10: sess_appl: ev(24=CC_EV_CALL_SETUP_IND), cid(97), disp(0)
        20:21:10: sess_appl: ev(SSA_EV_CALL_SETUP_IND), cid(97), disp(0)
        20:21:10: ssaCallSetupInd
        20:21:10: ccCallSetContext (callID=0x61, context=0x80DF0E3C)
        20:21:10: ssaCallSetupInd cid(97), st(SSA_CS_MAPPING),oldst(0), ev(24)ev->e.evCallSetupInd.nCallInfo.finalDestFlag = 1
        20:21:10: ssaCallSetupInd finalDest cllng(3885591), clled(80)
        20:21:10: ssaCallSetupInd cid(97), st(SSA_CS_CALL_SETTING),oldst(0), ev(24)dpMatchPeersMoreArg result= 0
        20:21:10: ssaSetupPeer cid(97) peer list: tag(1) called number (80)
        20:21:10: ssaSetupPeer cid(97), destPat(80), matched(2), prefix(), peer(80E0544C), peer->encapType (1)
        20:21:10: ccCallProceeding (callID=0x61, prog_ind=0x0)
        20:21:10: ccCallSetupRequest (Inbound call = 0x61, outbound peer =1, dest=, params=0x80D46C58 mode=0, *callID=0x80D46FC8, prog_ind = 3) callingIE_present 1
        20:21:10: ccCallSetupRequest numbering_type 0x81
        20:21:10: ccCallSetupRequest encapType 1 clid_restrict_disable 1 null_orig_clg 0 clid_transparent 0 callingNumber 3885591

        20:21:10: dest pattern 80, called 80, digit_strip 1
        20:21:10: callingNumber=3885591, calledNumber=80, redirectNumber= display_info= calling_oct3a=0
        20:21:10: accountNumber=, finalDestFlag=1,
        guid=1633.b358.1ad6.11cc.872c.ee67.fc12.e3d9
        20:21:10: peer_tag=1
        20:21:10: ccIFCallSetupRequestPrivate: (vdbPtr=0x80D21C80, dest=, callParams={called=80,called_oct3=0x81, calling=3885591,calling_oct3=0x80, calling_xlated=false, subscriber_type_str=Unknown, fdest=1, voice_peer_tag=1},mode=0x0) vdbPtr type = 6
        20:21:10: ccIFCallSetupRequestPrivate: (vdbPtr=0x80D21C80, dest=, callParams={called=80, called_oct3 0x81, calling=3885591,calling_oct3 0x80, calling_xlated=false, fdest=1, voice_peer_tag=1}, mode=0x0, xltrc=-5)
        20:21:10: ccSaveDialpeerTag (callID=0x61, dialpeer_tag=0x1)
        20:21:10: ccCallSetContext (callID=0x62, context=0x80E75CC8)
        20:21:10: ccCallReportDigits (callID=0x61, enable=0x0)
        20:21:10: cc_api_call_report_digits_done (vdbPtr=0x80CD71B4, callID=0x61, disp=0)
        20:21:10: sess_appl: ev(53=CC_EV_CALL_REPORT_DIGITS_DONE), cid(97), disp(0)
        20:21:10: cid(97)st(SSA_CS_CALL_SETTING)ev(SSA_EV_CALL_REPORT_DIGITS_DONE)
        oldst(SSA_CS_MAPPING)cfid(-1)csize(0)in(1)fDest(1)
        20:21:10: -cid2(98)st2(SSA_CS_CALL_SETTING)oldst2(SSA_CS_MAPPING)
        20:21:10: ssaReportDigitsDone cid(97) peer list: (empty)
        20:21:10: ssaReportDigitsDone callid=97 Reporting disabled.
        20:21:10: cc_api_call_proceeding(vdbPtr=0x80D21C80, callID=0x62,
              prog_ind=0x0)
        20:21:10: cc_api_call_alert(vdbPtr=0x80D21C80, callID=0x62, prog_ind=0x8, sig_ind=0x1)
        20:21:10: sess_appl: ev(21=CC_EV_CALL_PROCEEDING), cid(98), disp(0)
        20:21:10: cid(98)st(SSA_CS_CALL_SETTING)ev(SSA_EV_CALL_PROCEEDING)
        oldst(SSA_CS_MAPPING)cfid(-1)csize(0)in(0)fDest(0)
        20:21:10: -cid2(97)st2(SSA_CS_CALL_SETTING)oldst2(SSA_CS_CALL_SETTING)
        20:21:10: ssaCallProc
        20:21:10: ccGetDialpeerTag (callID=0x61)
        20:21:10: ssaIgnore cid(98), st(SSA_CS_CALL_SETTING),oldst(1), ev(21)
        20:21:10: sess_appl: ev(7=CC_EV_CALL_ALERT), cid(98), disp(0)
        20:21:10: cid(98)st(SSA_CS_CALL_SETTING)ev(SSA_EV_CALL_ALERT)
        oldst(SSA_CS_CALL_SETTING)cfid(-1)csize(0)in(0)fDest(0)
        20:21:10: -cid2(97)st2(SSA_CS_CALL_SETTING)oldst2(SSA_CS_CALL_SETTING)
        20:21:10: ssaAlert
        20:21:10: ccGetDialpeerTag (callID=0x61)
        20:21:10: ccCallAlert (callID=0x61, prog_ind=0x8, sig_ind=0x1)
        20:21:10: ccConferenceCreate (confID=0x80D4702C, callID1=0x61, callID2=0x62, tag=0x0)
        20:21:10: cc_api_bridge_done (confID=0x17, srcIF=0x80CD71B4, srcCallID=0x61, dstCallID=0x62, disposition=0, tag=0x0)
        20:21:10: cc_api_bridge_done (confID=0x17, srcIF=0x80D21C80, srcCallID=0x62, dstCallID=0x61, disposition=0, tag=0x0)
        20:21:10: cc_api_caps_ind (dstVdbPtr=0x80CD71B4, dstCallId=0x61, srcCallId=0x62,
             caps={codec=0xEBF7, fax_rate=0x7F, vad=0x3, modem=0x2
                   codec_bytes=0, signal_type=3})
        20:21:10: cc_api_caps_ind (Playout: mode 1, initial 60,min 40, max 200)
        20:21:10: cc_api_caps_ind (dstVdbPtr=0x80D21C80, dstCallId=0x62, srcCallId=0x61,
             caps={codec=0x4, fax_rate=0x2, vad=0x2, modem=0x0
                   codec_bytes=20, signal_type=1})
        20:21:10: cc_api_caps_ind (Playout: mode 1, initial 60,min 40, max 200)
        20:21:10: cc_api_caps_ack (dstVdbPtr=0x80D21C80, dstCallId=0x62, srcCallId=0x61,
             caps={codec=0x4, fax_rate=0x2, vad=0x2, modem=0x0
                   codec_bytes=20, signal_type=1, seq_num_start=6648})
        20:21:10: cc_api_caps_ack (dstVdbPtr=0x80CD71B4, dstCallId=0x61, srcCallId=0x62,
             caps={codec=0x4, fax_rate=0x2, vad=0x2, modem=0x0
                   codec_bytes=40, signal_type=1, seq_num_start=6648})
        20:21:10: cc_api_voice_mode_event , callID=0x62
        20:21:10: Call Pointer =80E75CC8
        Hex representation of the ALERTING TPKT to send.0300003E0802818E011E0280883401017E002B052380060008914A00022800B5000012400138048011001633B3581AD611CC872DEE67FC12E3D906800100
        20:21:10: h225AlertRequest: Q.931 ALERTING sent from socket [1]. Call state changed to [Call Received].
        20:21:10: sess_appl: ev(29=CC_EV_CONF_CREATE_DONE), cid(97), disp(0)
        20:21:10: cid(97)st(SSA_CS_CONFERENCING_ALERT)ev(SSA_EV_CONF_CREATE_DONE)
        oldst(SSA_CS_CALL_SETTING)cfid(23)csize(0)in(1)fDest(1)
        20:21:10: -cid2(98)st2(SSA_CS_CONFERENCING_ALERT)oldst2(SSA_CS_CALL_SETTING)
        20:21:10: ssaConfCreateDoneAlert
        20:21:10: sess_appl: ev(51=CC_EV_VOICE_MODE_DONE), cid(98), disp(0)
        20:21:10: cid(98)st(SSA_CS_CONFERENCED_ALERT)ev(SSA_EV_VOICE_MODE_DONE)
        oldst(SSA_CS_CALL_SETTING)cfid(23)csize(0)in(0)fDest(0)
        20:21:10: -cid2(97)st2(SSA_CS_CONFERENCED_ALERT)oldst2(SSA_CS_CONFERENCING_ALERT)
        20:21:10: ssaIgnore cid(98), st(SSA_CS_CONFERENCED_ALERT),oldst(4), ev(51)
        20:21:10: cc_process_notify_bridge_done (event=0x80D38220
          ----- Original Message -----
          From: ZaferP@koc.net
          To: cisco-ttl@yahoogroups.com
          Sent: Thursday, March 27, 2003 11:53 AM
          Subject: RE: [cisco-ttl] Voice çağrı gecikmesi!

          Selam

          her iki tarafta şu debegları açıp deneyin. Gecikme sebebi ile ilgili ipucu elde edebilirsiniz sanırım..

          debug voice ccapi inout
          debug call-mgmt
          debug h225 events

            -----Original Message-----
            From: ceyhun çatalbaş [mailto:ccatalbas@teknotel.net]
            Sent: Thursday, March 27, 2003 11:51 AM
            To: cisco-ttl@yahoogroups.com
            Subject: Re: [cisco-ttl] Voice çağrı gecikmesi!

            merkez tarafı fxo ofis tarafında direk telefon bağlı,
            ancak ben aramayı yapıp karşı tafataki porta baktığımda portunda çalma sesi ile aynı anda (10 sn sonra) up olduğunu görüyorum.
            Yani gecikme arada oluyo gibi ama pingim sedece 40 ms
            ios ver ile ilgili olabilir mi?
              ----- Original Message -----
              From: Devrim Yener KUCUK
              To: cisco-ttl@yahoogroups.com
              Sent: Thursday, March 27, 2003 11:35 AM
              Subject: Re: [cisco-ttl] Voice çağrı gecikmesi!

              Voice gateway kullaniyo musun?

              Ayrici telefonu direk routera balayip test ettiginde de ayni gecikme var mi ?

              yani:
              tel1--fxs--router1---ethernet--router1--fxs-tel2 gibi bir test yapma sansin var mi?

                ----- Original Message -----
                From: ceyhun çatalbaş
                To: cisco-ttl@yahoogroups.com
                Sent: Thursday, March 27, 2003 10:26 AM
                Subject: [cisco-ttl] Voice çağrı gecikmesi!

                Voice yaptığım iki cihaz arasında ,
                ubr924(ethernet) ve 3660 ios lar 12.2.16 çağrı başlattığımda
                10 sn lik bekleme süresinden(her iki yöndede) sonra voice portlara a çağrı ulaşıyor ping ve trace de ise bir gariplik görünmüyor.
                Buna ne sebep oluyor olabilir?

                Bu listden çıkmak için cisco-ttl-unsubscribe@yahoogroups.com adresine bir e-posta göndermeniz yeterlidir.

                Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.

              Bu listden çıkmak için cisco-ttl-unsubscribe@yahoogroups.com adresine bir e-posta göndermeniz yeterlidir.

              Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.

            Bu listden çıkmak için cisco-ttl-unsubscribe@yahoogroups.com adresine bir e-posta göndermeniz yeterlidir.

            Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.

          Bu listden çıkmak için cisco-ttl-unsubscribe@yahoogroups.com adresine bir e-posta göndermeniz yeterlidir.

          Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.

        Bu listden çıkmak için cisco-ttl-unsubscribe@yahoogroups.com adresine bir e-posta göndermeniz yeterlidir.

        Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.

            Yahoo! Groups Sponsor
                  ADVERTISEMENT
                    
           
           

      Bu listden çıkmak için cisco-ttl-unsubscribe@yahoogroups.com adresine bir e-posta göndermeniz yeterlidir.

      Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.



    This archive was generated by hypermail 2.1.5 : Thu Mar 27 2003 - 14:10:28 GMT