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

No ring Back tone and no audio

Rafael Jimenez
Enthusiast
Enthusiast

Hello,

I just setup a 2901 cme with 3905 sip phones and a sip trunk.

the outgoing calls are not working yet. Im working with some debugs...

For the incomming calls from the sip trunk, I have two issues:

- no ring back tone.

- no audio.

Attached a debug ccsip message with a partial running config ... I need some help.

Thank.s

4 Replies 4

Rafael Jimenez
Enthusiast
Enthusiast

Whats means SIP/2.0 484 Address Incomplete ?

n May 14 09:59:33 2012: <191>855: Sent:

Mon May 14 09:59:33 2012: <191>856: INVITE sip:53683651@200.13.230.38:5060 SIP/2.0

Mon May 14 09:59:33 2012: <191>857: Via: SIP/2.0/UDP 172.22.97.82:5060;branch=z9hG4bK1716F9

Mon May 14 09:59:33 2012: <191>858: From: "5841" <53185840>;tag=C851C-F2C

Mon May 14 09:59:33 2012: <191>859: To: <53683651>

Mon May 14 09:59:33 2012: <191>860: Date: Mon, 14 May 2012 15:00:33 GMT

Mon May 14 09:59:33 2012: <191>861: Call-ID: 63B3C25B-9D0C11E1-8039FA14-B1BA080E@172.22.97.82

Mon May 14 09:59:33 2012: <191>862: Supported: 100rel,timer,resource-priority,replaces,sdp-anat

Mon May 14 09:59:33 2012: <191>863: Min-SE:  1800

Mon May 14 09:59:33 2012: <191>864: Cisco-Guid: 1637365405-2634813921-2150824468-2981758990

Mon May 14 09:59:33 2012: <191>865: User-Agent: Cisco-SIPGateway/IOS-15.2.3.T

Mon May 14 09:59:33 2012: <191>866: Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PR

Mon May 14 09:59:33 2012: <191>867: ACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER

Mon May 14 09:59:33 2012: <191>868: CSeq: 101 INVITE

Mon May 14 09:59:33 2012: <191>869: Timestamp: 1337007633

Mon May 14 09:59:33 2012: <191>870: Contact: <53185840>

Mon May 14 09:59:33 2012: <191>871: Expires: 180

Mon May 14 09:59:33 2012: <191>872: Allow-Events: telephone-event

Mon May 14 09:59:33 2012: <191>873: Max-Forwards: 69

Mon May 14 09:59:33 2012: <191>874: Content-Type: application/sdp

Mon May 14 09:59:33 2012: <191>875: Content-Disposition: session;handling=required

Mon May 14 09:59:33 2012: <191>876: Content-Length: 247

Mon May 14 09:59:33 2012: <191>877:

Mon May 14 09:59:33 2012: <191>878: v=0

Mon May 14 09:59:33 2012: <191>879: o=CiscoSystemsSIP-GW-UserAgent 7173 3972 IN IP4 172.22.97.82

Mon May 14 09:59:33 2012: <191>880: s=SIP Call

Mon May 14 09:59:33 2012: <191>881: c=IN IP4 172.22.97.82

Mon May 14 09:59:33 2012: <191>882: t=0 0

Mon May 14 09:59:33 2012: <191>883: m=audio 16402 RTP/AVP 0 101

Mon May 14 09:59:33 2012: <191>884: c=IN IP4 172.22.97.82

Mon May 14 09:59:33 2012: <191>885: a=rtpmap:0 PCMU/8000

Mon May 14 09:59:33 2012: <191>886: a=rtpmap:101 telephone-event/8000

Mon May 14 09:59:34 2012: <191>887: a=fmtp:101 0-15

Mon May 14 09:59:34 2012: <191>888: a=ptime:20

Mon May 14 09:59:34 2012: <191>889: May 14 15:00:33.591: //0/000000000000/SIP/Msg/ccsipDisplayMsg:

Mon May 14 09:59:34 2012: <191>890: Received:

Mon May 14 09:59:34 2012: <191>891: SIP/2.0 200 OK

Mon May 14 09:59:34 2012: <191>892: Via: SIP/2.0/UDP 192.168.100.254:5060;received=192.168.100.254;branch=z9hG4bK16256D

Mon May 14 09:59:34 2012: <191>893: Call-ID: 6198D2C5-9D0C11E1-8037FA14-B1BA080E@192.168.100.254

Mon May 14 09:59:34 2012: <191>894: From: <0>;tag=C774C-1AD2

Mon May 14 09:59:34 2012: <191>895: To: <5841>;tag=KOAlMlbgX2kqMf8hoFf4NNDMf8rifF9A

Mon May 14 09:59:34 2012: <191>896: CSeq: 102 SUBSCRIBE

Mon May 14 09:59:34 2012: <191>897: Expires: 0

Mon May 14 09:59:34 2012: <191>898: Contact: <7B50-177>;+sip.instance="";+u.sip!devicename.ccm.cisco.com="SEPA4563041505C";+u.sip!model.ccm.cisco.com="592"

Mon May 14 09:59:34 2012: <191>899: Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS

Mon May 14 09:59:34 2012: <191>900: Supported: replaces, 100rel, timer, norefersub

Mon May 14 09:59:34 2012: <191>901: Content-Length:  0

Mon May 14 09:59:34 2012: <191>902:

Mon May 14 09:59:34 2012: <191>903: May 14 15:00:33.603: //28/6198369D8032/SIP/Msg/ccsipDisplayMsg:

Mon May 14 09:59:34 2012: <191>904: Received:

Mon May 14 09:59:34 2012: <191>905: SIP/2.0 484 Address Incomplete

Mon May 14 09:59:34 2012: <191>906: Via: SIP/2.0/UDP 172.22.97.82:5060;branch=z9hG4bK1716F9

Mon May 14 09:59:34 2012: <191>907: From: "5841" <53185840>;tag=C851C-F2C

Mon May 14 09:59:34 2012: <191>908: To: <53683651>;tag=434318894b36d363432065ca63d4c6d4.5d2a

Mon May 14 09:59:34 2012: <191>909: Call-ID: 63B3C25B-9D0C11E1-8039FA14-B1BA080E@172.22.97.82

Mon May 14 09:59:34 2012: <191>910: CSeq: 101 INVITE

Mon May 14 09:59:34 2012: <191>911: Content-Length: 0

Hi!!,

I thought that the no ring back tone was solved but nooo!!.

Actually, that is no the problem. The problem is for incomming calls, I never hear the ring back.

When I pickup the ip phone, the other side (the caller) never know that I pick up the phone.

The caller continues sending 180 Ringing.....

At the end after 15 secconds aprox... the call is dropped.

I believe that is someting related with the SIP/2.0 180 Ringing and 183 Session Progress. I dont know if I need

a sip profile to change that message.

check the debug ccsip message......bellow....

Tue May 15 14:52:51 2012: <191>7964: SIP/2.0 180 Ringing

Tue May 15 14:52:51 2012: <191>7965: Via: SIP/2.0/UDP 200.13.230.38:5060;branch=z9hG4bKffc.587.0,SIP/2.0/UDP 200.30.79.17:5065;branch=z9hG4bKd15451c80310ad9c09e05923a

Tue May 15 14:52:51 2012: <191>7966: From: <3174339866>;tag=58710c5f-CC-28

Tue May 15 14:52:51 2012: <191>7967: To: <53185848>;tag=425298-2543

Tue May 15 14:52:51 2012: <191>7968: Date: Tue, 15 May 2012 14:53:16 GMT

Tue May 15 14:52:51 2012: <191>7969: Call-ID: 35a4e623a052acdd52c1edf2bfc20a37@SoftX3000

Tue May 15 14:52:51 2012: <191>7970: CSeq: 1 INVITE

Tue May 15 14:52:51 2012: <191>7971: Require: 100rel

Tue May 15 14:52:51 2012: <191>7972: RSeq: 2333

Tue May 15 14:52:51 2012: <191>7973: Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER

Tue May 15 14:52:51 2012: <191>7974:

Tue May 15 14:52:51 2012: <191>7975: Allow-Events: telephone-event

Tue May 15 14:52:51 2012: <191>7976: Contact: <85AC-C89>

Tue May 15 14:52:51 2012: <191>7977: Record-Route: <200.13.230.38:5060>

Tue May 15 14:52:51 2012: <191>7978: Server: Cisco-SIPGateway/IOS-15.2.3.T

Tue May 15 14:52:51 2012: <191>7979: Content-Length: 0

Tue May 15 14:52:51 2012: <191>7980:

Tue May 15 14:52:54 2012: <191>7981: May 15 14:53:20.883: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Tue May 15 14:52:54 2012: <191>7982: Received:

Tue May 15 14:52:54 2012: <191>7983: INVITE sip:3185848@172.22.97.82;user=phone SIP/2.0

Tue May 15 14:52:54 2012: <191>7984: Record-Route: <200.13.230.38:5060>

Tue May 15 14:52:54 2012: <191>7985: Via: SIP/2.0/UDP 200.13.230.38:5060;branch=z9hG4bKffc.587.0

Tue May 15 14:52:54 2012: <191>7986: Via: SIP/2.0/UDP 200.30.79.17:5065;branch=z9hG4bKd15451c80310ad9c09e05923a

Tue May 15 14:52:54 2012: <191>7987: Call-ID: 35a4e623a052acdd52c1edf2bfc20a37@SoftX3000

Tue May 15 14:52:54 2012: <191>7988: From: <3174339866>;tag=58710c5f-CC-28

Tue May 15 14:52:54 2012: <191>7989: To: <53185848>

Tue May 15 14:52:54 2012: <191>7990: CSeq: 1 INVITE

Tue May 15 14:52:54 2012: <191>7991: P-Asserted-Identity: <3174339866>

Tue May 15 14:52:54 2012: <191>7992: Contact: <3174339866>

Tue May 15 14:52:54 2012: <191>7993: Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,REGISTER,INFO,PRACK,SUBSCRIBE,NOTIFY,UPDATE,MESSAGE,REFER

Tue May 15 14:52:54 2012: <191>7994: User-Agent: Huawei SoftX3000 V300R601

Tue May 15 14:52:54 2012: <191>7995: Supported: 100rel

Tue May 15 14:52:54 2012: <191>7996: Max-Forwards: 69

Tue May 15 14:52:54 2012: <191>7997: Content-Length: 419

Tue May 15 14:52:54 2012: <191>7998: Content-Type: application/sdp

Tue May 15 14:52:54 2012: <191>7999:

Tue May 15 14:52:54 2012: <191>8000: v=0

Tue May 15 14:52:54 2012: <191>8001: o=HuaweiSoftX3000 340392256 340392256 IN IP4 200.30.79.17

Tue May 15 14:52:54 2012: <191>8002: s=Sip Call

Tue May 15 14:52:54 2012: <191>8003: c=IN IP4 200.13.235.189

Tue May 15 14:52:54 2012: <191>8004: t=0 0

Tue May 15 14:52:55 2012: <191>8005: m=audio 50644 RTP/AVP 18 8 0 4 2 98 98 97

Tue May 15 14:52:55 2012: <191>8006: a=rtpmap:18 G729/8000

Tue May 15 14:52:55 2012: <191>8007: a=rtpmap:8 PCMA/8000

Tue May 15 14:52:55 2012: <191>8008: a=rtpmap:0 PCMU/8000

Tue May 15 14:52:55 2012: <191>8009: a=rtpmap:4 G723/8000

Tue May 15 14:52:55 2012: <191>8010: a

Tue May 15 14:52:55 2012: <191>8011: =rtpmap:2 G726-32/8000

Tue May 15 14:52:55 2012: <191>8012: a=rtpmap:98 G726-40/8000

Tue May 15 14:52:55 2012: <191>8013: a=rtpmap:98 G726-32/8000

Tue May 15 14:52:55 2012: <191>8014: a=rtpmap:97 telephone-event/8000

Tue May 15 14:52:55 2012: <191>8015: a=ptime:20

Tue May 15 14:52:55 2012: <191>8016: a=fmtp:97 0-15

Tue May 15 14:52:55 2012: <191>8017: a=fmtp:18 annexb=yes

Tue May 15 14:52:55 2012: <191>8018: a=nortpproxy:yes

Tue May 15 14:52:55 2012: <191>8019: May 15 14:53:20.883: //55/8092CA388093/SIP/Msg/ccsipDisplayMsg:

Tue May 15 14:52:55 2012: <191>8020: Sent:

Tue May 15 14:52:55 2012: <191>8021: SIP/2.0 180 Ringing

Tue May 15 14:52:55 2012: <191>8022: Via: SIP/2.0/UDP 200.13.230.38:5060;branch=z9hG4bKffc.587.0,SIP/2.0/UDP 200.30.79.17:5065;branch=z9hG4bKd15451c80310ad9c09e05923a

Tue May 15 14:52:55 2012: <191>8023: From: <3174339866>;tag=58710c5f-CC-28

Tue May 15 14:52:55 2012: <191>8024: To: <53185848>;tag=425298-2543

Tue May 15 14:52:55 2012: <191>8025: Date: Tue, 15 May 2012 14:53:20 GMT

Tue May 15 14:52:55 2012: <191>8026: Call-ID: 35a4e623a052acdd52c1edf2bfc20a37@SoftX3000

Tue May 15 14:52:55 2012: <191>8027: CSeq: 1 INVITE

Tue May 15 14:52:55 2012: <191>8028: Require: 100rel

Tue May 15 14:52:55 2012: <191>8029: RSeq: 2333

Tue May 15 14:52:55 2012: <191>8030: Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER

Tue May 15 14:52:55 2012: <191>8031:

Tue May 15 14:52:55 2012: <191>8032: Allow-Events: telephone-event

Tue May 15 14:52:55 2012: <191>8033: Contact: <85AC-C89>

Tue May 15 14:52:55 2012: <191>8034: Record-Route: <200.13.230.38:5060>

Tue May 15 14:52:55 2012: <191>8035: Server: Cisco-SIPGateway/IOS-15.2.3.T

Tue May 15 14:52:55 2012: <191>8036: Content-Length: 0

Tue May 15 14:52:55 2012: <191>8037:

Tue May 15 14:52:55 2012: <191>8038: May 15 14:53:21.099: //55/8092CA388093/SIP/Msg/ccsipDisplayMsg:

Tue May 15 14:52:55 2012: <191>8039: Sent:

Tue May 15 14:52:55 2012: <191>8040: SIP/2.0 504 Gateway Timeout

Tue May 15 14:52:55 2012: <191>8041: Via: SIP/2.0/UDP 200.13.230.38:5060;branch=z9hG4bKffc.587.0,SIP/2.0/UDP 200.30.79.17:5065;branch=z9hG4bKd15451c80310ad9c09e05923a

Tue May 15 14:52:55 2012: <191>8042: From: <3174339866>;tag=58710c5f-CC-28

Tue May 15 14:52:55 2012: <191>8043: To: <53185848>;tag=425298-2543

Tue May 15 14:52:55 2012: <191>8044: Call-ID: 35a4e623a052acdd52c1edf2bfc20a37@SoftX3000

Tue May 15 14:52:55 2012: <191>8045: CSeq: 1 INVITE

Tue May 15 14:52:55 2012: <191>8046: Reason: Q.850;cause=102

Tue May 15 14:52:55 2012: <191>8047: Content-Length: 0

Tue May 15 14:52:55 2012: <191>8048:

Tue May 15 14:52:55 2012: <191>8049: May 15 14:53:21.099: //56/8092CA388093/SIP/Msg/ccsipDisplayMsg:

Tue May 15 14:52:55 2012: <191>8050: Sent:

Tue May 15 14:52:55 2012: <191>8051: BYE sip:85AC-C89@192.168.200.56:5060 SIP/2.0

Tue May 15 14:52:55 2012: <191>8052: Via: SIP/2.0/UDP 192.168.100.254:5060;branch=z9hG4bK699CD

Tue May 15 14:52:55 2012: <191>8053: From: <3174339866>;tag=4251AC-496

Tue May 15 14:52:55 2012: <191>8054: To: <5848>;tag=a7rFx3TX.n3XW9AjktPqhxq1Vu.1ro38

Tue May 15 14:52:55 2012: <191>8055: Date: Tue, 15 May 2012 14:53:01 GMT

Tue May 15 14:52:55 2012: <191>8056: Call-ID: 80940288-9DD411E1-8099BFCF-E2F82F9D@192.168.100.254

Tue May 15 14:52:55 2012: <191>8057: User-Agent: Cisco-SIPGateway/IOS-15.2.3.T

Tue May 15 14:52:55 2012: <191>8058: Max-Forwards: 70

Tue May 15 14:52:55 2012: <191>8059: Timestamp: 1337093601

Tue May 15 14:52:55 2012: <191>8060: CSeq: 102 BYE

Tue May 15 14:52:55 2012: <191>8061: Reason: Q.850;cause=102

Tue May 15 14:52:55 2012: <191>8062: P-RTP-Stat: PS=0,OS=0,PR=416,OR=6730,PL=0,JI=0,LA=0,DU=16

Tue May 15 14:52:55 2012: <191>8063: Content-Length: 0

Tue May 15 14:52:55 2012: <191>8064:

Tue May 15 14:52:55 2012: <191>8065: May 15 14:53:21.111: //56/8092CA388093/SIP/Msg/ccsipDisplayMsg:

Tue May 15 14:52:55 2012: <191>8066: Received:

Tue May 15 14:52:55 2012: <191>8067: SIP/2.0 200 OK

Tue May 15 14:52:55 2012: <191>8068: Via: SIP/2.0/UDP 192.168.100.254:5060;received=192.168.100.254;branch=z9hG4bK699CD

Tue May 15 14:52:55 2012: <191>8069: Call-ID: 80940288-9DD411E1-8099BFCF-E2F82F9D@192.168.100.254

Tue May 15 14:52:56 2012: <191>8070: From: <3174339866>;tag=4251AC-496

Tue May 15 14:52:56 2012: <191>8071: To: <5848>;tag=a7rFx3TX.n3XW9AjktPqhxq1Vu.1ro38

Tue May 15 14:52:56 2012: <191>8072: CSeq: 102 BYE

Tue May 15 14:52:56 2012: <191>8073: RTP-RxStat: Dur=16,Pkt=0,Oct=0,LatePkt=0,LostPkt=0,AvgJit=0,VQMetrics="MLQK=0.0000;MLQKav=0.0000;MLQKmn=0.0000;MLQKmx=0.0000;MLQKvr=0.95;CCR=0.0000;ICR=0.0000;ICRmx=0.0000;CS=0;SCS=0"

Tue May 15 14:52:56 2012: <191>8074: RTP-TxStat: Dur=16,Pkt=391,Oct=11020

Tue May 15 14:52:56 2012: <191>8075: Content-Length:  0

Tue May 15 14:52:56 2012: <191>8076:

Tue May 15 14:52:56 2012: <191>8077: May 15 14:53:21.199: //55/8092CA388093/SIP/Msg/ccsipDisplayMsg:

Tue May 15 14:52:56 2012: <191>8078: Sent:

Tue May 15 14:52:56 2012: <191>8079: SIP/2.0 504 Gateway Timeout

Finally, I solved the problem with the inbound calls.

for some reason I forgot put the following lines to the inbound dial-peers:

voice-class sip bind control source-interface GigabitEthernet0/0

voice-class sip bind media source-interface GigabitEthernet0/0

In the case with CME, you must add those lines to all dial-peers.

The only that is pending is the dtmf issue. I cannot call to any kind of AA or IVR.

Rafael Jimenez
Enthusiast
Enthusiast

Solved.

The first problem was setting the codec g711ulaw, but in a voice-class codec with the g711ulaw alone.

Using the codec g711ulaw in the dial-peer or voice register pool doestn work.

The other problem was the outbound translation rules. The SP toldme that I need add a prefix of "5", but it was not true

the called number do not need that prefix. (SP fault).

After some tests I saw that the real problem was one way audio. This was solved with a ip route sentence....

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Recognize Your Peers