Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
New Member

Problem:Outbound calls disconnected after 19 sec

Dear All,

we have provided outbound calls from our application that is registered to a sip proxy server ,the sip proxy route the call to the cisco as5350 xm ,

and the call is connected successfully , the sip server send the 200 ok and the gateway send ack , but this process is continuing until the call is disconnected after 19 sec, in this duration we have seen 7 200 OK and ack send and recieves.

the configuration of as5350 XM is as the below :

!

   25     resource-pool disable

   26     no aaa new-model

   27     !

   28     resource policy

   29     !

   30     spe default-firmware spe-firmware-1

   31     !

   32     !

   33     ip cef

   34     !

   35     !

   36     isdn switch-type primary-net5

   37     !

   38     voice call send-alert

   39     voice call disc-pi-off

   40     !

   41     voice service voip

   42      fax protocol t38 ls-redundancy 0 hs-redundancy 0 fallback cisco

   43      modem passthrough nse codec g711alaw

   44      sip

   45       bind control source-interface GigabitEthernet0/0

   46       bind media source-interface GigabitEthernet0/0

   47       ds0-num

   48       header-passing

   49       registrar server

   50       no call service stop

   51     !

   52     !

   53     !

   54     !

   55     !

   56     !

   57     !

   58     !

   59     !

   60     voice translation-rule 1

   61      rule 1 /^199/ //

   62     !

   63     !

   64     voice translation-profile OUT

   65      translate calling 1

   66      translate called 1

   67     !

   68     voice translation-profile call

   69     !

   70     !

   71     !

   72     !

   73     username pendar privilege 15 secret 5 $1$fGxh$0hiSg//QgvwKyXvFyqefA1

   74     !

   75     !

   76     controller E1 3/0

   77      pri-group timeslots 1-31

   78     !

   79     controller E1 3/1

   80      pri-group timeslots 1-31

   81     !

   82     controller E1 3/2

   83      pri-group timeslots 1-31

   84     !

   85     controller E1 3/3

   86      pri-group timeslots 1-31

   87     !

   88     !

   89     interface GigabitEthernet0/0

   90      ip address 10.121.43.201 255.255.255.248

   91      duplex auto

   92      speed auto

   93      negotiation auto

   94     !

   95     interface GigabitEthernet0/1

   96      ip address 217.219.184.82 255.255.255.252

   97      duplex auto

   98      speed auto

   99      negotiation auto

  100     !

  101     interface Serial0/0

  102      no ip address

  103      shutdown

  104      clock rate 2000000

  105      no dce-terminal-timing-enable

  106      no fair-queue

  107     !

  108     interface Serial0/1

  109      no ip address

  110      shutdown

  111      clock rate 2000000

  112      no dce-terminal-timing-enable

  113     !

  114     interface Serial3/0:15

  115      no ip address

  116      encapsulation hdlc

  117      isdn switch-type primary-net5

  118      isdn incoming-voice modem 64

  119      isdn T306 400000

  120      isdn T310 400000

  121      isdn bchan-number-order ascending

  122      no cdp enable

  123     !

  124     interface Serial3/1:15

  125      no ip address

  126      encapsulation hdlc

  127      isdn switch-type primary-net5

  128      isdn incoming-voice modem 64

  129      isdn bchan-number-order ascending

  130      no cdp enable

  131     !

  132     interface Serial3/2:15

  133      no ip address

  134      encapsulation hdlc

  135      isdn switch-type primary-net5

  136      isdn incoming-voice modem 64

  137      isdn T306 40000

  138      isdn send-alerting

  139      isdn bchan-number-order ascending

  140      isdn sending-complete

  141      no cdp enable

  142     !

  143     interface Serial3/3:15

  144      no ip address

  145      encapsulation hdlc

  146      isdn switch-type primary-net5

  147      isdn incoming-voice modem 64

  148      isdn bchan-number-order ascending

  149      no cdp enable

  150     !

  151     interface Group-Async0

  152      no ip address

  153      encapsulation slip

  154      group-range 1/00 2/59

  155     !

  156     interface Group-Async1

  157      physical-layer async

  158      no ip address

  159      encapsulation slip

  160      async mode interactive

  161      no peer default ip address

  162     !

  163     router rip

  164      redistribute connected

  165      network 192.168.0.0

  166     !

  167     ip local pool dialin_pool 10.1.2.1 10.1.2.96

  168     ip default-gateway 192.168.10.1

  169     !

  170     ip route 0.0.0.0 0.0.0.0 217.219.184.81

  171     ip route 0.0.0.0 0.0.0.0 192.168.10.1

  172     ip route 192.168.75.0 255.255.255.0 192.168.10.1

  173     no ip http server

  174     !

  175     !

  176     access-list 101 permit ip any any

  177     dialer-list 1 protocol ip permit

  178     snmp-server community public RO

  179     !

  180     !

  181     !

  182     control-plane

  183     !

  184     call treatment on

  185     call threshold global cpu-5sec low 50 high 80 treatment

  186     call threshold global cpu-avg low 50 high 80 treatment

  187     !

  188     !

  189     voice-port 3/0:D

  190      disc_pi_off

  191      input gain 3

  192      output attenuation -3

  193      echo-cancel coverage 32

  194      no non-linear

  195      playout-delay mode fixed

  196      no comfort-noise

  197      cptone DE

  198      timeouts call-disconnect infinity

  199      timeouts wait-release 180

  200      bearer-cap Speech

  201     !

  202     voice-port 3/1:D

  203      disc_pi_off

  204      input gain 3

  205      output attenuation -3

  206      echo-cancel coverage 32

  207      no non-linear

  208      playout-delay mode fixed

  209      no comfort-noise

  210      cptone DE

  211     !

  212     voice-port 3/2:D

  213      disc_pi_off

  214      input gain 3

  215      output attenuation -3

  216      echo-cancel coverage 32

  217      no non-linear

  218      playout-delay mode fixed

  219      no comfort-noise

  220      cptone DE

  221      bearer-cap Speech

  222     !

  223     voice-port 3/3:D

  224      disc_pi_off

  225      input gain 6

  226      output attenuation -3

  227      echo-cancel coverage 32

  228      no non-linear

  229      playout-delay mode fixed

  230      no comfort-noise

  231      cptone DE

  232     !

  233     !

  234     !

  235     dial-peer voice 20 voip

  236      service session

  237      destination-pattern 2268T

  238      session protocol sipv2

  239      session target sip-server

  240      dtmf-relay rtp-nte

  241      codec g711alaw

  242      no vad

  243     !

  244     dial-peer voice 10 pots

  245      translation-profile outgoing OUT

  246      service session

  247      destination-pattern .+

  248      no digit-strip

  249      direct-inward-dial

  250      port 3/0:D

  251      forward-digits all

  297     !

  298     sip-ua

  299      credentials username 1111 password 1315121C0F0D16 realm ipv4:10.121.43.202

  300      credentials username 1111 password 014255550E5A545E021C68593D5441 realm pendar

  301      credentials username 1113 password 051B0301254D5C realm pendar

  302      authentication username 1111 password 105E0C17011600

  303      no remote-party-id

  304      no redirection

  305      srv version 1

  306      retry invite 2

  307      retry bye 1

  308      retry refer 3

  309      retry register 10

  310      timers notify 400

  311      timers refer 567

  312      timers register 100

  313      registrar ipv4:10.x.x.xexpires 60

  314      sip-server ipv4:10.x.x.x

  315     !

  316     ss7 mtp2-variant Bellcore 0

  317     ss7 mtp2-variant Bellcore 1

  318     ss7 mtp2-variant Bellcore 2

  319     ss7 mtp2-variant Bellcore 3

  320     !

  321     line con 0

  322      logging synchronous

  323      stopbits 1

  324     line aux 0

  325      stopbits 1

  326     line vty 0 4

  327      login local

  328     line 1/00 1/59

  329      modem InOut

  330     line 2/00 2/59

  331      modem InOut

  332     !

  333     scheduler allocate 10000 400

  334     ntp broadcastdelay 10

  335     ntp clock-period 17180080

  336     ntp update-calendar

  337     ntp server 217.218.158.42

  338     ntp server 195.146.63.100

  339     end

debug ccsip messages for one outbound call :

Telconi Terminal 1.01

direct TELNET to 10.121.43.201 [10.121.43.201] from 10.121.43.202

Default to IOS device.

ACCESS-118#

Sep 14 07:22:22: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Received:

INVITE sip:19909126131721@10.121.43.201:5060 SIP/2.0

Via: SIP/2.0/UDP 10.121.43.202:5060;branch=z9hG4bK-57fa4f40-11a3-4247-ba33-5abdfb3ce731-ppco

Max-Forwards: 10

Contact: <sip:100@10.121.43.202:5060>

To: "bd030c0f-0f0e-4c53-a71d-02df901aa822@10.121.43.202"<sip:19909126131721@10.121.43.202>

From: "100"<sip:100@10.121.43.202>;tag=400231974

Call-ID: bd030c0f-0f0e-4c53-a71d-02df901aa822@10.121.43.202

CSeq: 1 INVITE

Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, REGISTER, SUBSCRIBE, INFO

Supported: replaces

User-Agent: UMSV

Graph-Track: #1:1>

Content-Type: application/sdp

Content-Length: 198

v=0

o=- 88211 88211 IN IP4 10.121.43.202

s=UMSV

c=IN IP4 10.121.43.202

t=0 0

m=audio 6936 RTP/AVP 8 101

a=rtpmap:8 PCMA/8000

a=ptime:20

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-15

Sep 14 07:22:22: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

SIP/2.0 100 Trying

Via: SIP/2.0/UDP 10.121.43.202:5060;branch=z9hG4bK-57fa4f40-11a3-4247-ba33-5abdfb3ce731-ppco

From: "100"<sip:100@10.121.43.202>;tag=400231974

To: "bd030c0f-0f0e-4c53-a71d-02df901aa822@10.121.43.202"<sip:19909126131721@10.121.43.202>;tag=F2EB328-1553

Date: Sat, 14 Sep 2013 07:22:22 GMT

Call-ID: bd030c0f-0f0e-4c53-a71d-02df901aa822@10.121.43.202

Server: Cisco-SIPGateway/IOS-12.x

CSeq: 1 INVITE

Allow-Events: telephone-event

Content-Length: 0

Sep 14 07:22:23: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

REGISTER sip:10.121.43.202:5060 SIP/2.0

Via: SIP/2.0/UDP  10.121.43.201:5060;branch=z9hG4bK54801998

From: ".+" <sip:.+@10.121.43.202>;tag=F2EB8C4-D8A

To: ".+" <sip:.+@10.121.43.202>

Date: Sat, 14 Sep 2013 07:22:23 GMT

Call-ID: E7F05D17-19F611E3-80068889-D18125B9

User-Agent: Cisco-SIPGateway/IOS-12.x

Max-Forwards: 70

Timestamp: 1379143343

CSeq: 1818 REGISTER

Contact: <sip:.+@10.121.43.201:5060>

Expires: 60

Content-Length: 0

Sep 14 07:22:23: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Received:

SIP/2.0 200 Ok

Via: SIP/2.0/UDP 10.121.43.201:5060;branch=z9hG4bK54801998;rport=5060

From: ".+"<sip:.+@10.121.43.202>;tag=F2EB8C4-D8A

To: ".+"<sip:.+@10.121.43.202>

Date: Sat, 14 Sep 2013 07:22:23 GMT

Call-ID: E7F05D17-19F611E3-80068889-D18125B9

User-Agent: Cisco-SIPGateway/IOS-12.x

Max-Forwards: 70

Timestamp: 1379143343

CSeq: 1818 REGISTER

Contact: <sip:.+@10.121.43.201:5060>

Expires: 60

Content-Length: 0

Sep 14 07:22:27: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

SIP/2.0 180 Ringing

Via: SIP/2.0/UDP 10.121.43.202:5060;branch=z9hG4bK-57fa4f40-11a3-4247-ba33-5abdfb3ce731-ppco

From: "100"<sip:100@10.121.43.202>;tag=400231974

To: "bd030c0f-0f0e-4c53-a71d-02df901aa822@10.121.43.202"<sip:19909126131721@10.121.43.202>;tag=F2EB328-1553

Date: Sat, 14 Sep 2013 07:22:22 GMT

Call-ID: bd030c0f-0f0e-4c53-a71d-02df901aa822@10.121.43.202

Server: Cisco-SIPGateway/IOS-12.x

CSeq: 1 INVITE

Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, COMET, REFER, SUBSCRIBE, NOTIFY, INFO, UPDATE, REGISTER

Allow-Events: telephone-event

Contact: <sip:19909126131721@10.121.43.201:5060>

Content-Length: 0

Sep 14 07:22:28: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

SIP/2.0 200 OK

Via: SIP/2.0/UDP 10.121.43.202:5060;branch=z9hG4bK-57fa4f40-11a3-4247-ba33-5abdfb3ce731-ppco

From: "100"<sip:100@10.121.43.202>;tag=400231974

To: "bd030c0f-0f0e-4c53-a71d-02df901aa822@10.121.43.202"<sip:19909126131721@10.121.43.202>;tag=F2EB328-1553

Date: Sat, 14 Sep 2013 07:22:22 GMT

Call-ID: bd030c0f-0f0e-4c53-a71d-02df901aa822@10.121.43.202

Server: Cisco-SIPGateway/IOS-12.x

CSeq: 1 INVITE

Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, COMET, REFER, SUBSCRIBE, NOTIFY, INFO, UPDATE, REGISTER

Allow-Events: telephone-event

Contact: <sip:19909126131721@10.121.43.201:5060>

Content-Type: application/sdp

Content-Length: 250

v=0

o=CiscoSystemsSIP-GW-UserAgent 6982 8340 IN IP4 10.121.43.201

s=SIP Call

c=IN IP4 10.121.43.201

t=0 0

m=audio 16388 RTP/AVP 8 101

c=IN IP4 10.121.43.201

a=rtpmap:8 PCMA/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-15

a=ptime:20

Sep 14 07:22:28: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Received:

ACK sip:1111@10.121.43.202:5060 SIP/2.0

Via: SIP/2.0/UDP 10.121.43.202:5060;branch=z9hG4bK-57fa4f40-11a3-4247-ba33-5abdfb3ce731-ppco

Max-Forwards: 10

To: "bd030c0f-0f0e-4c53-a71d-02df901aa822@10.121.43.202"<sip:19909126131721@10.121.43.202>;tag=F2EB328-1553

From: "100"<sip:100@10.121.43.202>;tag=400231974

Call-ID: bd030c0f-0f0e-4c53-a71d-02df901aa822@10.121.43.202

CSeq: 1 ACK

User-Agent: CallCenter

Content-Length: 0

Sep 14 07:22:29: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

SIP/2.0 200 OK

Via: SIP/2.0/UDP 10.121.43.202:5060;branch=z9hG4bK-57fa4f40-11a3-4247-ba33-5abdfb3ce731-ppco

From: "100"<sip:100@10.121.43.202>;tag=400231974

To: "bd030c0f-0f0e-4c53-a71d-02df901aa822@10.121.43.202"<sip:19909126131721@10.121.43.202>;tag=F2EB328-1553

Date: Sat, 14 Sep 2013 07:22:22 GMT

Call-ID: bd030c0f-0f0e-4c53-a71d-02df901aa822@10.121.43.202

Server: Cisco-SIPGateway/IOS-12.x

CSeq: 1 INVITE

Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, COMET, REFER, SUBSCRIBE, NOTIFY, INFO, UPDATE, REGISTER

Allow-Events: telephone-event

Contact: <sip:19909126131721@10.121.43.201:5060>

Content-Type: application/sdp

Content-Length: 250

v=0

o=CiscoSystemsSIP-GW-UserAgent 6982 8340 IN IP4 10.121.43.201

s=SIP Call

c=IN IP4 10.121.43.201

t=0 0

m=audio 16388 RTP/AVP 8 101

c=IN IP4 10.121.43.201

a=rtpmap:8 PCMA/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-15

a=ptime:20

Sep 14 07:22:29: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Received:

ACK sip:1111@10.121.43.202:5060 SIP/2.0

Via: SIP/2.0/UDP 10.121.43.202:5060;branch=z9hG4bK-57fa4f40-11a3-4247-ba33-5abdfb3ce731-ppco

Max-Forwards: 10

To: "bd030c0f-0f0e-4c53-a71d-02df901aa822@10.121.43.202"<sip:19909126131721@10.121.43.202>;tag=F2EB328-1553

From: "100"<sip:100@10.121.43.202>;tag=400231974

Call-ID: bd030c0f-0f0e-4c53-a71d-02df901aa822@10.121.43.202

CSeq: 1 ACK

User-Agent: CallCenter

Content-Length: 0

Sep 14 07:22:30: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

SIP/2.0 200 OK

Via: SIP/2.0/UDP 10.121.43.202:5060;branch=z9hG4bK-57fa4f40-11a3-4247-ba33-5abdfb3ce731-ppco

From: "100"<sip:100@10.121.43.202>;tag=400231974

To: "bd030c0f-0f0e-4c53-a71d-02df901aa822@10.121.43.202"<sip:19909126131721@10.121.43.202>;tag=F2EB328-1553

Date: Sat, 14 Sep 2013 07:22:22 GMT

Call-ID: bd030c0f-0f0e-4c53-a71d-02df901aa822@10.121.43.202

Server: Cisco-SIPGateway/IOS-12.x

CSeq: 1 INVITE

Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, COMET, REFER, SUBSCRIBE, NOTIFY, INFO, UPDATE, REGISTER

Allow-Events: telephone-event

Contact: <sip:19909126131721@10.121.43.201:5060>

Content-Type: application/sdp

Content-Length: 250

v=0

o=CiscoSystemsSIP-GW-UserAgent 6982 8340 IN IP4 10.121.43.201

s=SIP Call

c=IN IP4 10.121.43.201

t=0 0

m=audio 16388 RTP/AVP 8 101

c=IN IP4 10.121.43.201

a=rtpmap:8 PCMA/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-15

a=ptime:20

Sep 14 07:22:30: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Received:

ACK sip:1111@10.121.43.202:5060 SIP/2.0

Via: SIP/2.0/UDP 10.121.43.202:5060;branch=z9hG4bK-57fa4f40-11a3-4247-ba33-5abdfb3ce731-ppco

Max-Forwards: 10

To: "bd030c0f-0f0e-4c53-a71d-02df901aa822@10.121.43.202"<sip:19909126131721@10.121.43.202>;tag=F2EB328-1553

From: "100"<sip:100@10.121.43.202>;tag=400231974

Call-ID: bd030c0f-0f0e-4c53-a71d-02df901aa822@10.121.43.202

CSeq: 1 ACK

User-Agent: CallCenter

Content-Length: 0

Sep 14 07:22:32: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

SIP/2.0 200 OK

Via: SIP/2.0/UDP 10.121.43.202:5060;branch=z9hG4bK-57fa4f40-11a3-4247-ba33-5abdfb3ce731-ppco

From: "100"<sip:100@10.121.43.202>;tag=400231974

To: "bd030c0f-0f0e-4c53-a71d-02df901aa822@10.121.43.202"<sip:19909126131721@10.121.43.202>;tag=F2EB328-1553

Date: Sat, 14 Sep 2013 07:22:22 GMT

Call-ID: bd030c0f-0f0e-4c53-a71d-02df901aa822@10.121.43.202

Server: Cisco-SIPGateway/IOS-12.x

CSeq: 1 INVITE

Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, COMET, REFER, SUBSCRIBE, NOTIFY, INFO, UPDATE, REGISTER

Allow-Events: telephone-event

Contact: <sip:19909126131721@10.121.43.201:5060>

Content-Type: application/sdp

Content-Length: 250

v=0

o=CiscoSystemsSIP-GW-UserAgent 6982 8340 IN IP4 10.121.43.201

s=SIP Call

c=IN IP4 10.121.43.201

t=0 0

m=audio 16388 RTP/AVP 8 101

c=IN IP4 10.121.43.201

a=rtpmap:8 PCMA/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-15

a=ptime:20

Sep 14 07:22:32: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Received:

ACK sip:1111@10.121.43.202:5060 SIP/2.0

Via: SIP/2.0/UDP 10.121.43.202:5060;branch=z9hG4bK-57fa4f40-11a3-4247-ba33-5abdfb3ce731-ppco

Max-Forwards: 10

To: "bd030c0f-0f0e-4c53-a71d-02df901aa822@10.121.43.202"<sip:19909126131721@10.121.43.202>;tag=F2EB328-1553

From: "100"<sip:100@10.121.43.202>;tag=400231974

Call-ID: bd030c0f-0f0e-4c53-a71d-02df901aa822@10.121.43.202

CSeq: 1 ACK

User-Agent: CallCenter

Content-Length: 0

Sep 14 07:22:36: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

SIP/2.0 200 OK

Via: SIP/2.0/UDP 10.121.43.202:5060;branch=z9hG4bK-57fa4f40-11a3-4247-ba33-5abdfb3ce731-ppco

From: "100"<sip:100@10.121.43.202>;tag=400231974

To: "bd030c0f-0f0e-4c53-a71d-02df901aa822@10.121.43.202"<sip:19909126131721@10.121.43.202>;tag=F2EB328-1553

Date: Sat, 14 Sep 2013 07:22:22 GMT

Call-ID: bd030c0f-0f0e-4c53-a71d-02df901aa822@10.121.43.202

Server: Cisco-SIPGateway/IOS-12.x

CSeq: 1 INVITE

Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, COMET, REFER, SUBSCRIBE, NOTIFY, INFO, UPDATE, REGISTER

Allow-Events: telephone-event

Contact: <sip:19909126131721@10.121.43.201:5060>

Content-Type: application/sdp

Content-Length: 250

v=0

o=CiscoSystemsSIP-GW-UserAgent 6982 8340 IN IP4 10.121.43.201

s=SIP Call

c=IN IP4 10.121.43.201

t=0 0

m=audio 16388 RTP/AVP 8 101

c=IN IP4 10.121.43.201

a=rtpmap:8 PCMA/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-15

a=ptime:20

Sep 14 07:22:36: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Received:

ACK sip:1111@10.121.43.202:5060 SIP/2.0

Via: SIP/2.0/UDP 10.121.43.202:5060;branch=z9hG4bK-57fa4f40-11a3-4247-ba33-5abdfb3ce731-ppco

Max-Forwards: 10

To: "bd030c0f-0f0e-4c53-a71d-02df901aa822@10.121.43.202"<sip:19909126131721@10.121.43.202>;tag=F2EB328-1553

From: "100"<sip:100@10.121.43.202>;tag=400231974

Call-ID: bd030c0f-0f0e-4c53-a71d-02df901aa822@10.121.43.202

CSeq: 1 ACK

User-Agent: CallCenter

Content-Length: 0

Sep 14 07:22:40: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

SIP/2.0 200 OK

Via: SIP/2.0/UDP 10.121.43.202:5060;branch=z9hG4bK-57fa4f40-11a3-4247-ba33-5abdfb3ce731-ppco

From: "100"<sip:100@10.121.43.202>;tag=400231974

To: "bd030c0f-0f0e-4c53-a71d-02df901aa822@10.121.43.202"<sip:19909126131721@10.121.43.202>;tag=F2EB328-1553

Date: Sat, 14 Sep 2013 07:22:22 GMT

Call-ID: bd030c0f-0f0e-4c53-a71d-02df901aa822@10.121.43.202

Server: Cisco-SIPGateway/IOS-12.x

CSeq: 1 INVITE

Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, COMET, REFER, SUBSCRIBE, NOTIFY, INFO, UPDATE, REGISTER

Allow-Events: telephone-event

Contact: <sip:19909126131721@10.121.43.201:5060>

Content-Type: application/sdp

Content-Length: 250

v=0

o=CiscoSystemsSIP-GW-UserAgent 6982 8340 IN IP4 10.121.43.201

s=SIP Call

c=IN IP4 10.121.43.201

t=0 0

m=audio 16388 RTP/AVP 8 101

c=IN IP4 10.121.43.201

a=rtpmap:8 PCMA/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-15

a=ptime:20

Sep 14 07:22:40: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Received:

ACK sip:1111@10.121.43.202:5060 SIP/2.0

Via: SIP/2.0/UDP 10.121.43.202:5060;branch=z9hG4bK-57fa4f40-11a3-4247-ba33-5abdfb3ce731-ppco

Max-Forwards: 10

To: "bd030c0f-0f0e-4c53-a71d-02df901aa822@10.121.43.202"<sip:19909126131721@10.121.43.202>;tag=F2EB328-1553

From: "100"<sip:100@10.121.43.202>;tag=400231974

Call-ID: bd030c0f-0f0e-4c53-a71d-02df901aa822@10.121.43.202

CSeq: 1 ACK

User-Agent: CallCenter

Content-Length: 0

Sep 14 07:22:44: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

SIP/2.0 200 OK

Via: SIP/2.0/UDP 10.121.43.202:5060;branch=z9hG4bK-57fa4f40-11a3-4247-ba33-5abdfb3ce731-ppco

From: "100"<sip:100@10.121.43.202>;tag=400231974

To: "bd030c0f-0f0e-4c53-a71d-02df901aa822@10.121.43.202"<sip:19909126131721@10.121.43.202>;tag=F2EB328-1553

Date: Sat, 14 Sep 2013 07:22:22 GMT

Call-ID: bd030c0f-0f0e-4c53-a71d-02df901aa822@10.121.43.202

Server: Cisco-SIPGateway/IOS-12.x

CSeq: 1 INVITE

Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, COMET, REFER, SUBSCRIBE, NOTIFY, INFO, UPDATE, REGISTER

Allow-Events: telephone-event

Contact: <sip:19909126131721@10.121.43.201:5060>

Content-Type: application/sdp

Content-Length: 250

v=0

o=CiscoSystemsSIP-GW-UserAgent 6982 8340 IN IP4 10.121.43.201

s=SIP Call

c=IN IP4 10.121.43.201

t=0 0

m=audio 16388 RTP/AVP 8 101

c=IN IP4 10.121.43.201

a=rtpmap:8 PCMA/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-15

a=ptime:20

Sep 14 07:22:44: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Received:

ACK sip:1111@10.121.43.202:5060 SIP/2.0

Via: SIP/2.0/UDP 10.121.43.202:5060;branch=z9hG4bK-57fa4f40-11a3-4247-ba33-5abdfb3ce731-ppco

Max-Forwards: 10

To: "bd030c0f-0f0e-4c53-a71d-02df901aa822@10.121.43.202"<sip:19909126131721@10.121.43.202>;tag=F2EB328-1553

From: "100"<sip:100@10.121.43.202>;tag=400231974

Call-ID: bd030c0f-0f0e-4c53-a71d-02df901aa822@10.121.43.202

CSeq: 1 ACK

User-Agent: CallCenter

Content-Length: 0

Sep 14 07:22:45: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

BYE sip:10.121.43.202:5060 SIP/2.0

Via: SIP/2.0/UDP  10.121.43.201:5060;x-ds0num="ISDN 3/0:D 3/0:DS1 26:DS0";branch=z9hG4bK5481D52

From: <sip:5522343@10.121.43.202>;tag=F2EB4A8-14E

To: <sip:2268000@10.121.43.202>;tag=758019368

Date: Sat, 14 Sep 2013 07:22:22 GMT

Call-ID: 3B8C672A-1C4511E3-96718889-D18125B9@10.121.43.201

User-Agent: Cisco-SIPGateway/IOS-12.x

Max-Forwards: 70

Route: <sip:2268000@10.121.43.202;ftag=F2EB4A8-14E;lr=on>

Timestamp: 1379143365

CSeq: 102 BYE

Reason: Q.850;cause=16

Content-Length: 0

Sep 14 07:22:45: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Received:

SIP/2.0 200 Ok

Via: SIP/2.0/UDP 10.121.43.201:5060;branch=z9hG4bK5481D52;rport=5060

From: <sip:5522343@10.121.43.202>;tag=F2EB4A8-14E

To: <sip:2268000@10.121.43.202>;tag=758019368

Date: Sat, 14 Sep 2013 07:22:22 GMT

Call-ID: 3B8C672A-1C4511E3-96718889-D18125B9@10.121.43.201

User-Agent: Cisco-SIPGateway/IOS-12.x

Max-Forwards: 70

Route: <sip:2268000@10.121.43.202;ftag=F2EB4A8-14E;lr=on>

Timestamp: 1379143365

CSeq: 102 BYE

Reason: Q.850;cause=16

Content-Length: 0

Sep 14 07:22:46: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Received:

BYE sip:1111@10.121.43.202 SIP/2.0

Via: SIP/2.0/UDP 10.121.43.202:5060;branch=z9hG4bK-c4a2ddc9-d8df-4e86-8fd7-954ad58290ee-ppco

Call-ID: 25A950E2-1C4511E3-96598889-D18125B9@10.121.43.201

CSeq: 2 BYE

Max-Forwards: 10

To: <sip:3243502@10.121.43.202>;tag=F2E2538-D6C

From: <sip:2268000@10.121.43.202>;tag=982710943

User-Agent: CallCenter

P-hint: rr-enforced

Route: <sip:10.121.43.202;ftag=F2E2538-D6C;lr=on>

Content-Length: 0

Sep 14 07:22:46: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

SIP/2.0 200 OK

Via: SIP/2.0/UDP 10.121.43.202:5060;branch=z9hG4bK-c4a2ddc9-d8df-4e86-8fd7-954ad58290ee-ppco

From: <sip:2268000@10.121.43.202>;tag=982710943

To: <sip:3243502@10.121.43.202>;tag=F2E2538-D6C

Date: Sat, 14 Sep 2013 07:22:46 GMT

Call-ID: 25A950E2-1C4511E3-96598889-D18125B9@10.121.43.201

Server: Cisco-SIPGateway/IOS-12.x

Content-Length: 0

CSeq: 2 BYE

Sep 14 07:22:48: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

BYE sip:100@10.121.43.202:5060 SIP/2.0

Via: SIP/2.0/UDP  10.121.43.201:5060;branch=z9hG4bK548218FD

From: "bd030c0f-0f0e-4c53-a71d-02df901aa822@10.121.43.202"<sip:19909126131721@10.121.43.202>;tag=F2EB328-1553

To: "100"<sip:100@10.121.43.202>;tag=400231974

Date: Sat, 14 Sep 2013 07:22:22 GMT

Call-ID: bd030c0f-0f0e-4c53-a71d-02df901aa822@10.121.43.202

User-Agent: Cisco-SIPGateway/IOS-12.x

Max-Forwards: 70

Timestamp: 1379143368

CSeq: 101 BYE

Content-Length: 0

Sep 14 07:22:48: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Received:

SIP/2.0 200 Ok

Via: SIP/2.0/UDP 10.121.43.201:5060;branch=z9hG4bK548218FD;rport=5060

From: "bd030c0f-0f0e-4c53-a71d-02df901aa822@10.121.43.202"<sip:19909126131721@10.121.43.202>;tag=F2EB328-1553

To: "100"<sip:100@10.121.43.202>;tag=400231974

Date: Sat, 14 Sep 2013 07:22:22 GMT

Call-ID: bd030c0f-0f0e-4c53-a71d-02df901aa822@10.121.43.202

User-Agent: Cisco-SIPGateway/IOS-12.x

Max-Forwards: 70

Timestamp: 1379143368

CSeq: 101 BYE

Content-Length: 0

would you please help me to underestand what the root cause of this problem?

Everyone's tags (3)
4 ACCEPTED SOLUTIONS

Accepted Solutions

Re: Problem:Outbound calls disconnected after 19 sec

Probably the problem is in the ACK message:

Received:

ACK sip:1111@10.121.43.202:5060 SIP/2.0

Via: SIP/2.0/UDP 10.121.43.202:5060;branch=z9hG4bK-57fa4f40-11a3-4247-ba33-5abdfb3ce731-ppco

Max-Forwards: 10

To: "bd030c0f-0f0e-4c53-a71d-02df901aa822@10.121.43.202"<19909126131721>;tag=F2EB328-1553

From: "100"<100>;tag=400231974

Call-ID: bd030c0f-0f0e-4c53-a71d-02df901aa822@10.121.43.202

CSeq: 1 ACK

User-Agent: CallCenter

Content-Length: 0

The request URI in the ACK must be the Contact from the 2xx response.

Try to use sip:19909126131721@10.121.43.201:5060:

ACK sip:19909126131721@10.121.43.201:5060 SIP/2.0

Via: SIP/2.0/UDP 10.121.43.202:5060;branch=z9hG4bK-57fa4f40-11a3-4247-ba33-5abdfb3ce731-ppco

Max-Forwards: 10

To: "bd030c0f-0f0e-4c53-a71d-02df901aa822@10.121.43.202"<19909126131721>;tag=F2EB328-1553

From: "100"<100>;tag=400231974

Call-ID: bd030c0f-0f0e-4c53-a71d-02df901aa822@10.121.43.202

CSeq: 1 ACK

User-Agent: CallCenter

Content-Length: 0


Regards.

Re: Problem:Outbound calls disconnected after 19 sec

Who are subjects of communication?

INVITE from 10.121.43.202, user-agent: UMSV ---> to Cisco AS5350 10.121.43.201

TRYING from Cisco AS5350 10.121.43.201

180 RINGING from Cisco AS5350 10.121.43.201

200 OK from Cisco AS5350 10.121.43.201

ACK from 10.121.43.202, user-agent: CallCenter ---> to Cisco AS5350

The first INVITE come from "UMSV".

The ACK came from "CallCenter".

Regards.

Re: Problem:Outbound calls disconnected after 19 sec

I've already answer. The problem of disconnection is due to an inconsistent URI in ACK received from AS5350.

The request URI in the ACK must be the Contact from the 2xx response.

You must fixed your application.

In the log you can see the AS5350 that sends multiple 200 OK because doesn't understand the ACK. The timeout is about 20 seconds.

first 200ok:

Sep 14 07:22:28: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

SIP/2.0 200 OK

last 200ok

Sep 14 07:22:44: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

SIP/2.0 200 OK

timeout

Sep 14 07:22:45: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

BYE sip:10.121.43.202:5060 SIP/2.0

Use "debug ccsip all" to confirm.

Regards.

Re: Problem:Outbound calls disconnected after 19 sec

If the config is the same, you can load the IOS of working scenario.

I expect the same behavior.

Regards.

9 REPLIES

Re: Problem:Outbound calls disconnected after 19 sec

Probably the problem is in the ACK message:

Received:

ACK sip:1111@10.121.43.202:5060 SIP/2.0

Via: SIP/2.0/UDP 10.121.43.202:5060;branch=z9hG4bK-57fa4f40-11a3-4247-ba33-5abdfb3ce731-ppco

Max-Forwards: 10

To: "bd030c0f-0f0e-4c53-a71d-02df901aa822@10.121.43.202"<19909126131721>;tag=F2EB328-1553

From: "100"<100>;tag=400231974

Call-ID: bd030c0f-0f0e-4c53-a71d-02df901aa822@10.121.43.202

CSeq: 1 ACK

User-Agent: CallCenter

Content-Length: 0

The request URI in the ACK must be the Contact from the 2xx response.

Try to use sip:19909126131721@10.121.43.201:5060:

ACK sip:19909126131721@10.121.43.201:5060 SIP/2.0

Via: SIP/2.0/UDP 10.121.43.202:5060;branch=z9hG4bK-57fa4f40-11a3-4247-ba33-5abdfb3ce731-ppco

Max-Forwards: 10

To: "bd030c0f-0f0e-4c53-a71d-02df901aa822@10.121.43.202"<19909126131721>;tag=F2EB328-1553

From: "100"<100>;tag=400231974

Call-ID: bd030c0f-0f0e-4c53-a71d-02df901aa822@10.121.43.202

CSeq: 1 ACK

User-Agent: CallCenter

Content-Length: 0


Regards.
New Member

Re: Problem:Outbound calls disconnected after 19 sec

but how can I revise the ack , it must be done in 5350 or in the PBX ?

Re: Problem:Outbound calls disconnected after 19 sec

Who are subjects of communication?

INVITE from 10.121.43.202, user-agent: UMSV ---> to Cisco AS5350 10.121.43.201

TRYING from Cisco AS5350 10.121.43.201

180 RINGING from Cisco AS5350 10.121.43.201

200 OK from Cisco AS5350 10.121.43.201

ACK from 10.121.43.202, user-agent: CallCenter ---> to Cisco AS5350

The first INVITE come from "UMSV".

The ACK came from "CallCenter".

Regards.

New Member

Re: Problem:Outbound calls disconnected after 19 sec

we fixed the User-agent but the problem still remain .

apart from the Ack , why does it disconnect after 19 sec, If the ack and 200 ok has problem the connection wouldn't be established at all.  but the connection is OK , we can have conversation in both side but after 19 second is disconnected ,... is it need to set some parameteres in as5350 ? or it must be resolved by Telco? may be our application send this disconnection ????

another thing is that our inbound calls doesn't have any problem , we faced with this problem when we want to make a call from our softphone to PSTN.

I am really confused with this problem

Re: Problem:Outbound calls disconnected after 19 sec

I've already answer. The problem of disconnection is due to an inconsistent URI in ACK received from AS5350.

The request URI in the ACK must be the Contact from the 2xx response.

You must fixed your application.

In the log you can see the AS5350 that sends multiple 200 OK because doesn't understand the ACK. The timeout is about 20 seconds.

first 200ok:

Sep 14 07:22:28: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

SIP/2.0 200 OK

last 200ok

Sep 14 07:22:44: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

SIP/2.0 200 OK

timeout

Sep 14 07:22:45: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

BYE sip:10.121.43.202:5060 SIP/2.0

Use "debug ccsip all" to confirm.

Regards.

New Member

Re: Problem:Outbound calls disconnected after 19 sec

Dear Sir,

I have noticed something strange, we have another center with successful outbound call

the "debug ccsip message" displays as follows:

*Sep 22 22:17:30.076: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

Cisco#

*Sep 22 22:17:22.264: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Received:

INVITE sip:19909126131721@217.218.20.88:5060 SIP/2.0

Via: SIP/2.0/UDP 217.218.20.86:5060;branch=z9hG4bK-9033762f-21a3-4a73-90fb-6f6371811faa-ppco

Max-Forwards: 10

Contact:

To: "5229e37a-0eae-42ea-96c0-c8eb0037e03f@217.218.20.86"<19909126131721>

From: "system";tag=1289485100

Call-ID: 5229e37a-0eae-42ea-96c0-c8eb0037e03f@217.218.20.86

CSeq: 1 INVITE

Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, REGISTER, SUBSCRIBE, INFO

Supported: replaces

User-Agent: UMSV

Graph-Track: #6:1>#1:17>

Content-Type: application/sdp

Content-Length: 199

v=0

o=- 88211 88211 IN IP4 217.218.20.86

s=UMSV

c=IN IP4 217.218.20.86

t=0 0

m=audio 17801 RTP/AVP 8 101

a=rtpmap:8 PCMA/8000

a=ptime:20

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-15

*Sep 22 22:17:22.264: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

SIP/2.0 100 Trying

Via: SIP/2.0/UDP 217.218.20.86:5060;branch=z9hG4bK-9033762f-21a3-4a73-90fb-6f6371811faa-ppco

From: "system";tag=1289485100

To: "5229e37a-0eae-42ea-96c0-c8eb0037e03f@217.218.20.86"<19909126131721>;tag=1493B7A4-26C2

Date: Sun, 22 Sep 2002 22:17:22 GMT

Call-ID: 5229e37a-0eae-42ea-96c0-c8eb0037e03f@217.218.20.86

Server: Cisco-SIPGateway/IOS-12.x

CSeq: 1 INVITE

Allow-Events: telephone-event

Content-Length: 0

*Sep 22 22:17:26.744: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

SIP/2.0 180 Ringing

Via: SIP/2.0/UDP 217.218.20.86:5060;branch=z9hG4bK-9033762f-21a3-4a73-90fb-6f6371811faa-ppco

From: "system";tag=1289485100

To: "5229e37a-0eae-42ea-96c0-c8eb0037e03f@217.218.20.86"<19909126131721>;tag=1493B7A4-26C2

Date: Sun, 22 Sep 2002 22:17:22 GMT

Call-ID: 5229e37a-0eae-42ea-96c0-c8eb0037e03f@217.218.20.86

Server: Cisco-SIPGateway/IOS-12.x

CSeq: 1 INVITE

Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER

Allow-Events: telephone-event

Contact: <19909126131721>

Content-Length: 0

*Sep 22 22:17:30.076: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

SIP/2.0 200 OK

Via: SIP/2.0/UDP 217.218.20.86:5060;branch=z9hG4bK-9033762f-21a3-4a73-90fb-6f6371811faa-ppco

From: "system";tag=1289485100

To: "5229e37a-0eae-42ea-96c0-c8eb0037e03f@217.218.20.86"<19909126131721>;tag=1493B7A4-26C2

Date: Sun, 22 Sep 2002 22:17:22 GMT

Call-ID: 5229e37a-0eae-42ea-96c0-c8eb0037e03f@217.218.20.86

Server: Cisco-SIPGateway/IOS-12.x

CSeq: 1 INVITE

Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER

Allow-Events: telephone-event

Contact: <19909126131721>

Content-Type: application/sdp

Content-Disposition: session;handling=required

Content-Length: 249

v=0

o=CiscoSystemsSIP-GW-UserAgent 1770 426 IN IP4 217.218.20.88

s=SIP Call

c=IN IP4 217.218.20.88

t=0 0

m=audio 17826 RTP/AVP 8 101

c=IN IP4 217.218.20.88

a=rtpmap:8 PCMA/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-16

a=ptime:20

*Sep 22 22:17:30.076: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Received:

ACK sip:1112@217.218.20.86:5060 SIP/2.0

Via: SIP/2.0/UDP 217.218.20.86:5060;branch=z9hG4bK-9033762f-21a3-4a73-90fb-6f6371811faa-ppco

Max-Forwards: 10

To: "5229e37a-0eae-42ea-96c0-c8eb0037e03f@217.218.20.86"<19909126131721>;tag=1493B7A4-26C2

From: "system";tag=1289485100

Call-ID: 5229e37a-0eae-42ea-96c0-c8eb0037e03f@217.218.20.86

CSeq: 1 ACK

User-Agent: CallCenter

Content-Length: 0

*Sep 22 22:18:01.968: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

BYE sip:system@217.218.20.86:5060 SIP/2.0

Via: SIP/2.0/UDP 217.218.20.88:5060;branch=z9hG4bK4DC31428

From: "5229e37a-0eae-42ea-96c0-c8eb0037e03f@217.218.20.86"<19909126131721>;tag=1493B7A4-26C2

To: "system";tag=1289485100

Date: Sun, 22 Sep 2002 22:17:30 GMT

Call-ID: 5229e37a-0eae-42ea-96c0-c8eb0037e03f@217.218.20.86

User-Agent: Cisco-SIPGateway/IOS-12.x

Max-Forwards: 70

Timestamp: 1032733081

CSeq: 101 BYE

Reason: Q.850;cause=16

Content-Length: 0

there is One Ok and One Ack , furthermore the ack is

ACK sip:1112@217.218.20.86:5060 SIP/2.0

the configuration of as5350 is the same as first one that I mentioned it in previous messages

How is it possible !!!!

by the way, we are trying to revise the Ok and Ack in Sip dll template, However if anything else that we must cosider, I am really appreciate telling me.

New Member

Re: Problem:Outbound calls disconnected after 19 sec

Dear Daniele,

I found the error in "debug ccsip all" message :

from the first gateway I found that after ack it faced with error so it transmit another 200 Ok

Received:

ACK sip:1113@10.121.43.202:5060 SIP/2.0

Via: SIP/2.0/UDP 10.121.43.202:5060;branch=z9hG4bK-65a22302-cb5d-4684-ab07-d21bf659108e-ppco

Max-Forwards: 10

To: "77c16348-e88d-4e57-a234-cf47af12289d@10.121.43.202"<19909126131721>;tag=1E0714C8-229C

From: "100"<100>;tag=585182037

Call-ID: 77c16348-e88d-4e57-a234-cf47af12289d@10.121.43.202

CSeq: 1 ACK

User-Agent: CallCenter

Content-Length: 0

Sep 17 04:33:33: //-1/xxxxxxxxxxxx/SIP/Error/sipSPISipIncomingMsg: Invalid method for (STATE_IDLE): ACK

Sep 17 04:33:34: //21838/2151511CA876/SIP/Transport/sipSPISendInviteResponse: Sending 200OK Response to the Transport Layer

Sep 17 04:33:34: //21838/2151511CA876/SIP/Transport/sipSPITransportSendMessage: msg=0x65D52AA8, addr=10.121.43.202, port=5060, se

ntBy_port=5060, is_req=0, transport=1, switch=0, callBack=0x00000000

Sep 17 04:33:34: //21838/2151511CA876/SIP/Transport/sipSPITransportSendMessage: Proceedable for sending msg immediately

Sep 17 04:33:34: //21838/2151511CA876/SIP/Transport/sipTransportLogicSendMsg: switch transport is 0

Sep 17 04:33:34: //-1/xxxxxxxxxxxx/SIP/Transport/sipTransportPostSendMessage: Posting send for msg=0x65D52AA8, addr=10.121.43.202

, port=5060, connId=0 for UDP

but in the second gateway that we have successful call we observed following messages:

Received:

ACK sip:1112@217.218.20.86:5060 SIP/2.0

Via: SIP/2.0/UDP 217.218.20.86:5060;branch=z9hG4bK-856eba9a-360a-4fdb-87cf-026735f9a9d7-ppco

Max-Forwards: 10

To: "3bed38f0-30ec-42f8-bdfa-d8c813401f1b@217.218.20.86"<19909126131721>;tag=2389DB44-219D

From: "system";tag=2097595264

Call-ID: 3bed38f0-30ec-42f8-bdfa-d8c813401f1b@217.218.20.86

CSeq: 1 ACK

User-Agent: CallCenter

Content-Length: 0

*Sep 25 20:01:00.418: //-1/xxxxxxxxxxxx/SIP/Info/ccsip_new_msg_preprocessor: Checking Invite Dialog

*Sep 25 20:01:00.422: //44001/55364B20A789/SIP/Info/sipSPIFindCcbUASRespTable: *****CCB found in UAS Response table. ccb=0x66C252

2C

*Sep 25 20:01:00.422: //-1/xxxxxxxxxxxx/SIP/Transport/sipSPIUpdateResponseInfo: Subsq Transaction Address 217.218.20.86,Port 5060

, Transport 1, SentBy Port 5060

*Sep 25 20:01:00.422: //-1/xxxxxxxxxxxx/SIP/Info/sipSPISetDateHeader: Clock Time Zone is UTC, same as GMT: Using GMT

*Sep 25 20:01:00.422: //-1/xxxxxxxxxxxx/SIP/Transport/sipSPIUpdateResponseInfo: Subsq Transaction Address 217.218.20.86,Port 5060

, Transport 1, SentBy Port 5060

*Sep 25 20:01:00.422: //44001/55364B20A789/SIP/Info/act_sentsucc_new_message_request: Transaction Complete. Lock on Facilities re

leased.

what do you think ? what different between the processing of ack in these two ACK? all the headers are the same so where is their differences ?

Also,searching Net , I found a documet about caveat for cisco IOS release 12.4 which mention this error :

Symptoms: DTMF path confirmation is not received for a SIP call.

Conditions: This problem is due to an issue with th

e SIP state machine, which may result in an error

along the lines of the following:

00:05:10: //-1/xxxxxxxxxxxx/SIP/Error/sipSPISipIncomingMsg: Invalid method for

(STATE_IDLE): ACK

The call state should not be IDLE

In your Opinion , with upgrading the IOS , is the problem solved?Or we must solve it in our application?

Re: Problem:Outbound calls disconnected after 19 sec

If the config is the same, you can load the IOS of working scenario.

I expect the same behavior.

Regards.

New Member

Re: Problem:Outbound calls disconnected after 19 sec

I have already got the result .

we provide Ack Request same as invite header field ....

IOS upgrading is not a proper solution , thanks for your answer and time , It was really helpfull

2854
Views
0
Helpful
9
Replies
CreatePlease to create content