cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
428
Views
0
Helpful
0
Replies

IVR campaign,Gateway cannot transfer to PSTN

Based on the IVR campaign, the gateway reported an error 503 service unavailable, 6005 is the sipdialer virtual port, and 919821032217 is the customer number.

Gateway configuration:

dial-peer voice 62186991 pots

translation-profile outgoing outgoing

destination-pattern 9T

progress_ind alert enable 8

progress_ind progress enable 8

progress_ind connect enable 8

incoming called-number .

no digit-strip

port 0/3/1

dial-peer voice 1 voip

session protocol sipv2

incoming called-number 9T voice-class sip rel1xx supported "100rel" dtmf-relay cisco-rtp h245-alphanumeric h245-signal rtp-nte sip-kpml sip-notify codec g711ulaw no vad Gateway

Error log: 

Apr 16 14:50:31.793: //256040/6405CC37AA89/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.3.37:58800;branch=z9hG4bK-d8754z-a966f5661d317e79-1---d8754z-;rport
From: <sip:6005@192.168.3.37>;tag=d25dab5c
To: <sip:919821032217@192.168.1.200>;tag=68493604-1FDC
Date: Thu, 16 Apr 2020 06:50:31 GMT
Call-ID: 7e15bd2b-1215f06f-cd5b6a38-8e4e4a5a
CSeq: 1 INVITE
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
Remote-Party-ID: <sip:19821032217@192.168.1.200>;party=called;screen=no;privacy=off
Contact: <sip:919821032217@192.168.1.200:5060>
Supported: replaces
Supported: sdp-anat
Server: Cisco-SIPGateway/IOS-12.x
Require: timer
Session-Expires: 1800;refresher=uac
Supported: timer
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 354

v=0
o=CiscoSystemsSIP-GW-UserAgent 6614 2584 IN IP4 192.168.1.200
s=SIP Call
c=IN IP4 192.168.1.200
t=0 0
m=audio 18302 RTP/AVP 0 18 121 101
c=IN IP4 192.168.1.200
a=rtpmap:0 PCMU/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:121 frf-dialed-digit/8000
a=fmtp:121 0-15
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=inactive

Apr 16 14:50:31.797: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
ACK sip:919821032217@192.168.1.200:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.3.37:58800;branch=z9hG4bK-d8754z-08593c216961687c-1---d8754z-;rport
Max-Forwards: 70
Contact: <sip:6005@192.168.3.37:58800>
To: <sip:919821032217@192.168.1.200>;tag=68493604-1FDC
From: <sip:6005@192.168.3.37>;tag=d25dab5c
Call-ID: 7e15bd2b-1215f06f-cd5b6a38-8e4e4a5a
CSeq: 1 ACK
User-Agent: Cisco-SIPDialer/UCCE10.0
Content-Length: 0


Apr 16 14:50:31.849: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
REFER sip:919821032217@192.168.1.200:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.3.37:58800;branch=z9hG4bK-d8754z-af13aa4b8719b778-1---d8754z-;rport
Max-Forwards: 70
Contact: <sip:6005@192.168.3.37:58800>
To: <sip:919821032217@192.168.1.200>;tag=68493604-1FDC
From: <sip:6005@192.168.3.37>;tag=d25dab5c
Call-ID: 7e15bd2b-1215f06f-cd5b6a38-8e4e4a5a
CSeq: 3 REFER
User-Agent: Cisco-SIPDialer/UCCE10.0
Refer-To: <sip:5555555555@192.168.1.200>
Referred-By: <sip:6005@192.168.3.37>
Content-Length: 0


Apr 16 14:50:31.861: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 202 Accepted
Via: SIP/2.0/UDP 192.168.3.37:58800;branch=z9hG4bK-d8754z-af13aa4b8719b778-1---d8754z-;rport
From: <sip:6005@192.168.3.37>;tag=d25dab5c
To: <sip:919821032217@192.168.1.200>;tag=68493604-1FDC
Date: Thu, 16 Apr 2020 06:50:31 GMT
Call-ID: 7e15bd2b-1215f06f-cd5b6a38-8e4e4a5a
CSeq: 3 REFER
Content-Length: 0
Contact: <sip:919821032217@192.168.1.200:5060>


Apr 16 14:50:31.865: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
NOTIFY sip:6005@192.168.3.37:58800 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.200:5060;branch=z9hG4bK16321A0
From: <sip:919821032217@192.168.1.200>;tag=68493604-1FDC
To: <sip:6005@192.168.3.37>;tag=d25dab5c
Call-ID: 7e15bd2b-1215f06f-cd5b6a38-8e4e4a5a
CSeq: 101 NOTIFY
Max-Forwards: 70
Date: Thu, 16 Apr 2020 06:50:31 GMT
User-Agent: Cisco-SIPGateway/IOS-12.x
Event: refer
Subscription-State: pending;expires=180
Contact: <sip:919821032217@192.168.1.200:5060>
Content-Type: message/sipfrag
Content-Length: 22

SIP/2.0 100 Trying


Apr 16 14:50:31.885: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
NOTIFY sip:6005@192.168.3.37:58800 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.200:5060;branch=z9hG4bK164A7C
From: <sip:919821032217@192.168.1.200>;tag=68493604-1FDC
To: <sip:6005@192.168.3.37>;tag=d25dab5c
Call-ID: 7e15bd2b-1215f06f-cd5b6a38-8e4e4a5a
CSeq: 102 NOTIFY
Max-Forwards: 70
Date: Thu, 16 Apr 2020 06:50:31 GMT
User-Agent: Cisco-SIPGateway/IOS-12.x
Event: refer
Subscription-State: terminated;reason=noresource
Contact: <sip:919821032217@192.168.1.200:5060>
Content-Type: message/sipfrag
Content-Length: 35

SIP/2.0 503 Service Unavailable


Apr 16 14:50:31.889: //0/000000000000/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.200:5060;branch=z9hG4bK16321A0
Contact: <sip:6005@192.168.3.37:58800>
To: <sip:6005@192.168.3.37>;tag=d25dab5c
From: <sip:919821032217@192.168.1.200>;tag=68493604-1FDC
Call-ID: 7e15bd2b-1215f06f-cd5b6a38-8e4e4a5a
CSeq: 101 NOTIFY
User-Agent: Cisco-SIPDialer/UCCE10.0
Content-Length: 0


Apr 16 14:50:31.893: //0/000000000000/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.200:5060;branch=z9hG4bK164A7C
Contact: <sip:6005@192.168.3.37:58800>
To: <sip:6005@192.168.3.37>;tag=d25dab5c
From: <sip:919821032217@192.168.1.200>;tag=68493604-1FDC
Call-ID: 7e15bd2b-1215f06f-cd5b6a38-8e4e4a5a
CSeq: 102 NOTIFY
User-Agent: Cisco-SIPDialer/UCCE10.0
Content-Length: 0

0 Replies 0