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

SIP : 484 Address Incomplete in Outbound Call

Hi,

we have cucm 8.6 and cisco gateway 2811 with sip trunk to istp. these are working fine except one extension having outbound calls issue.

i am getting 484 address incomplete msg in ccsip messages.

call flow is like

IP Phone-----CUCM----(Sip Trunk)---Gateway--(SIP Trunk)-----ITSP.

Calling Number 3030

Called number 0558902195

-----------------------------------------------------------------------------------------------

ASICO-DAM#debug ccsip messages
2734609: *Jan 6 12:39:16.305: %ENVMON-4-FAN_LOW_RPM: Fan 1 service recommended
2734610: *Jan 6 12:39:16.305: %ENVMON-4-FAN_LOW_RPM: Fan 2 service recommended
SIP Call messages tracing is enabled
ASICO-DAM#
2734611: *Jan 6 15:39:31.177: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
OPTIONS sip:172.29.25.246:5060 SIP/2.0
Via: SIP/2.0/UDP 10.205.20.50:5060;branch=z9hG4bKsbcthLNQZtAxpHZnAHBxnAnBQt4nL4n xBT10033
Call-ID: sbcthLNQpBZmLp4mVtxBcBVncqcQc4LntcHAtH4m@52p1ULIII
From: <sip:172.29.25.246:5060>;tag=sbc0806sbcthLNQV4HmHaxx
To: <sip:172.29.25.246>
CSeq: 1 OPTIONS
Max-Forwards: 70
Content-Length: 0


2734612: *Jan 6 15:39:31.189: //3028716/5DF46AF98D4C/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.205.20.50:5060;branch=z9hG4bKsbcthLNQZtAxpHZnAHBxnAnBQt4nL4n xBT10033
From: <sip:172.29.25.246:5060>;tag=sbc0806sbcthLNQV4HmHaxx
To: <sip:172.29.25.246>;tag=1720EDC4-B8F
Date: Wed, 06 Jan 2016 12:39:31 GMT
Call-ID: sbcthLNQpBZmLp4mVtxBcBVncqcQc4LntcHAtH4m@52p1ULIII
Server: Cisco-SIPGateway/IOS-12.x
CSeq: 1 OPTIONS
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIF Y, INFO, REGISTER
Allow-Events: telephone-event
Accept: application/sdp
Supported: timer,resource-priority,replaces,sdp-anat
Content-Type: application/sdp
Content-Length: 170

v=0
o=CiscoSystemsSIP-GW-UserAgent 9786 1860 IN IP4 172.29.25.246
s=SIP Call
c=IN IP4 192.168.33.5
t=0 0
m=audio 0 RTP/AVP 18 0 8 9 4 2 15 3
c=IN IP4 192.168.33.5

2734613: *Jan 6 15:39:31.725: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
INVITE sip:0558902195@192.168.33.5:5060 SIP/2.0
Via: SIP/2.0/TCP 192.168.12.190:5060;branch=z9hG4bK43ad5b394463
From: "Irfan" <sip:3030@192.168.12.190>;tag=83944~70e9433b-1d79-44ae-9a16-09a52b e377c5-19528919
To: <sip:0558902195@192.168.33.5>
Date: Wed, 06 Jan 2016 12:32:09 GMT
Call-ID: 7f96b000-68d10949-2775-be0ca8c0@192.168.12.190
Supported: timer,resource-priority,replaces
Min-SE: 1800
User-Agent: Cisco-CUCM8.6
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
CSeq: 101 INVITE
Expires: 180
Allow-Events: presence
Supported: X-cisco-srtp-fallback
Supported: Geolocation
Cisco-Guid: 2140581888-0000065536-0000002438-3188500672
Session-Expires: 1800
P-Asserted-Identity: "Irfan" <sip:3030@192.168.12.190>
Remote-Party-ID: "Irfan" <sip:3030@192.168.12.190>;party=calling;screen=yes;priv acy=off
Contact: <sip:3030@192.168.12.190:5060;transport=tcp>
Max-Forwards: 70
Content-Type: application/sdp
Content-Length: 217

v=0
o=CiscoSystemsCCM-SIP 83944 1 IN IP4 192.168.12.190
s=SIP Call
c=IN IP4 192.168.12.190
t=0 0
m=audio 31512 RTP/AVP 8 101
a=rtpmap:8 PCMA/8000
a=ptime:20
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15

2734614: *Jan 6 15:39:31.769: //3028718/7F96B0000000/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:0558902195@10.205.20.50:5060 SIP/2.0
Via: SIP/2.0/UDP 172.29.25.246:5060;branch=z9hG4bK1E77E162C
Remote-Party-ID: "Irfan" <sip:3030@172.29.25.246>;party=calling;screen=yes;priva cy=off
From: "Irfan" <sip:3030@172.29.25.246>;tag=1720F008-209F
To: <sip:0558902195@10.205.20.50>
Date: Wed, 06 Jan 2016 12:39:31 GMT
Call-ID: 5E4CEA1F-B3A911E5-8D52B1FE-1BC3CC1A@172.29.25.246
Supported: timer,resource-priority,replaces,sdp-anat
Min-SE: 1800
Cisco-Guid: 2140581888-0000065536-0000002438-3188500672
User-Agent: Cisco-SIPGateway/IOS-12.x
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIF Y, INFO, REGISTER
CSeq: 101 INVITE
Timestamp: 1452083971
Contact: <sip:3030@172.29.25.246:5060>
Expires: 180
Allow-Events: telephone-event
Max-Forwards: 69
Session-Expires: 1800
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 250

v=0
o=CiscoSystemsSIP-GW-UserAgent 6066 4519 IN IP4 172.29.25.246
s=SIP Call
c=IN IP4 172.29.25.246
t=0 0
m=audio 16492 RTP/AVP 8 101
c=IN IP4 172.29.25.246
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20

2734615: *Jan 6 15:39:31.769: //3028717/7F96B0000000/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 100 Trying
Via: SIP/2.0/TCP 192.168.12.190:5060;branch=z9hG4bK43ad5b394463
From: "Irfan" <sip:3030@192.168.12.190>;tag=83944~70e9433b-1d79-44ae-9a16-09a52b e377c5-19528919
To: <sip:0558902195@192.168.33.5>
Date: Wed, 06 Jan 2016 12:39:31 GMT
Call-ID: 7f96b000-68d10949-2775-be0ca8c0@192.168.12.190
CSeq: 101 INVITE
Allow-Events: kpml, telephone-event
Server: Cisco-SIPGateway/IOS-12.x
Content-Length: 0


2734616: *Jan 6 15:39:31.781: //3028718/7F96B0000000/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 172.29.25.246:5060;branch=z9hG4bK1E77E162C
Call-ID: 5E4CEA1F-B3A911E5-8D52B1FE-1BC3CC1A@172.29.25.246
From: "Irfan"<sip:3030@172.29.25.246>;tag=1720F008-209F
To: <sip:0558902195@10.205.20.50>
CSeq: 101 INVITE
Content-Length: 0


2734617: *Jan 6 15:39:31.841: //3028718/7F96B0000000/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 484 Address Incomplete
Via: SIP/2.0/UDP 172.29.25.246:5060;branch=z9hG4bK1E77E162C
Record-Route: <sip:10.205.20.50:5060;transport=udp;lr>
Call-ID: 5E4CEA1F-B3A911E5-8D52B1FE-1BC3CC1A@172.29.25.246
From: "Irfan"<sip:3030@172.29.25.246>;tag=1720F008-209F
To: <sip:0558902195@10.205.20.50>;tag=sbc0802sbcthLNQ4BAmnLLt
CSeq: 101 INVITE
Reason: Q.850;cause=28;text="address incomplete"
Warning: 399 - "SoftX3000 R601-CCU Rel POS:[3103] Release from CR"
Content-Length: 0


2734618: *Jan 6 15:39:31.865: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
ACK sip:0558902195@10.205.20.50:5060 SIP/2.0
Via: SIP/2.0/UDP 172.29.25.246:5060;branch=z9hG4bK1E77E162C
From: "Irfan" <sip:3030@172.29.25.246>;tag=1720F008-209F
To: <sip:0558902195@10.205.20.50>;tag=sbc0802sbcthLNQ4BAmnLLt
Date: Wed, 06 Jan 2016 12:39:31 GMT
Call-ID: 5E4CEA1F-B3A911E5-8D52B1FE-1BC3CC1A@172.29.25.246
Max-Forwards: 70
CSeq: 101 ACK
Allow-Events: telephone-event
Content-Length: 0

2 Accepted Solutions

Accepted Solutions

Vivek Batra
VIP Alumni
VIP Alumni

Do you mean if call to 0558902195 is made by other user, it goes through. If yes, please share the traces of that working call.

Although 484 Address Incomplete is used when there is an issue with called party number but in your case, I suspect issue is with calling number and translation rules are not being applied correctly.

- Vivek

View solution in original post

Rajan
VIP Alumni
VIP Alumni

Hi Mohammed,

as we are getting "address incomplete " mesasge from SIP ITSP, the called number is incomplete from the provider side.

From the debugs, we are matching the below dial-peer and no translation is happening as such for this call:

dial-peer voice 150 voip
description **Outgoing Call to SIP Trunk**
translation-profile outgoing OUT_FAX
destination-pattern .T
modem passthrough nse codec g711alaw
session protocol sipv2
session target ipv4:10.205.20.50
voice-class codec 2
voice-class sip bind control source-interface FastEthernet0/0
voice-class sip bind media source-interface FastEthernet0/0
dtmf-relay rtp-nte
fax rate disable
fax protocol pass-through g711alaw

Can you tell us from which extension the same outbound call is working and if possible share the debugs for one working call so that we could check what is the number sent to provider in that scenario.

Thanks,

Rajan\

Pls rate all useful posts

View solution in original post

4 Replies 4

Vivek Batra
VIP Alumni
VIP Alumni

Do you mean if call to 0558902195 is made by other user, it goes through. If yes, please share the traces of that working call.

Although 484 Address Incomplete is used when there is an issue with called party number but in your case, I suspect issue is with calling number and translation rules are not being applied correctly.

- Vivek

HI,

thank you for your replies,

its taking the wrong dial-peer,it should take dial-peer 20.

attached is the working call from another extension..

you both are correct.

the translation was not happening because when configuring i missed 0 in the translation pattern, thats why the extensions ending with 0 are giving the problems.

 rule 2 /^30\(.[12345679]\)/ /8062301/

 rule 2 /^30\(.[012345679]\)/ /8062301/

now every thing working fine

thank you all

Rajan
VIP Alumni
VIP Alumni

Hi Mohammed,

as we are getting "address incomplete " mesasge from SIP ITSP, the called number is incomplete from the provider side.

From the debugs, we are matching the below dial-peer and no translation is happening as such for this call:

dial-peer voice 150 voip
description **Outgoing Call to SIP Trunk**
translation-profile outgoing OUT_FAX
destination-pattern .T
modem passthrough nse codec g711alaw
session protocol sipv2
session target ipv4:10.205.20.50
voice-class codec 2
voice-class sip bind control source-interface FastEthernet0/0
voice-class sip bind media source-interface FastEthernet0/0
dtmf-relay rtp-nte
fax rate disable
fax protocol pass-through g711alaw

Can you tell us from which extension the same outbound call is working and if possible share the debugs for one working call so that we could check what is the number sent to provider in that scenario.

Thanks,

Rajan\

Pls rate all useful posts