Dtmf RFC2833 issue
Hi All,
I got problem with dtmf RFC2833 in interconnecting with Nextone using SIP.
Nextone----------------->AS5300XM (acting as IPIP GW)------------>AS5400-------E1------->PSTN
When Nextone call in and press 103 to reach extention at my staff, my cisco AS5300XM send back OK message but when Signal-Update from SIP INFO msg my cisco AS5300XM send back Bad Request (SIP 400 msg).
Detail of debug ccsip message in my cisco as in attached file.
Thanks a lot.
BRG
Huong
did you configure dtmf-relay sip-notify or dtmf-relay rtp-nte on the AS5300 and AS5400?
Similar Messages
-
How to change DTMF RFC2833 payload type to 101 or 127
Hi,
We are using Flash Media Gateway 4.5, and we would like to change the DTMF payload type from 127 to 101 for RFC2833.
as of now, I couldn't find any configuration settings from the documents. Looks like this is a discontinued product but any help is much appreciated.
Thanks,
Uttran IHi Thomas,
according to your first question: Why does this matter to you? As I already wrote in another thread:
According to the XML namespace declaration the prefixes are just internal aliases with no external meaning.
E.g. <ns1:abc xmlns:ns1="http://www.sap.com" /> and
<iLikeLongPrefixes:abc xmlns:iLikeLongPrefixes ="http://www.sap.com" /> are totally equivalent according to the XML namespace specification.
Therefore, everyone (human or machine) who produces a program can choose the prefixes as he wants. Moreover, he may change the rules for creating these prefixes without being incompatible.
Consequently, the namespace prefixes should not be important for you.
Greetings
Stephan -
Dear All,
I have Cisco Voice router 2801 with Two FXO ports and we have terminated two PSTN lines over it. Suddently, we are facing some DTMF detection issues.
Once the Router give us the dial Tone and we tried to dialed the desired numbers but unfortunately some times router recived the wrong digits. Successful ratio is 30% means 3 calls are passing correctly out of 10.
For Example:
Dailed: 923332631696
Recived Sample 1: 92233326631116
Recived Sample 2: 9223266
Please help me to sort out this issue. Thanks.
Note: its works perfectly since couple of years.Suresh, Thanks for your Response.
I am using analog phone in order to reach the router. Below are the call flow
Analog Phone ---> FXO (PSTN Line) ----> Voice Dial Peer VOIP (SIP)
Please let me know if you any settings. I have tried to change dial type to pulse from DTMF but not much improvement.
Thanks. -
Please help with SIP configuration on 2801 router
Hi All.
Please help me to setup a SIP account. I’m already struggling to do that for a few days, and can’t find out how to finish that. We have 2xISDN lines running, so I need to add a SIP trunk to existing config.
The information from our SIP provider:
We have issued the following DDI range: 018877000 – 99
There is no need to register the DDI’s as these will be offered to your PABX IP address provided to in the completed SIP trunking form.
Configuration details are as follows:
Our Primary Proxy:- 99.234.56.78
Codec supported:- G711Alaw, G729 (G711Alaw is the preferred codec)
Fax Support:- T38 and G711Alaw
DTMF:- RFC2833 and INFO
CLI Method:- Remote-Party-ID
Trunk doesn’t require registration; you just need to send Invite. In cisco this is done through Dial-peer session-target command. We are authenticating your IP address for outgoing calls and incoming calls we then forward to the IP mentioned in the sip form.
This is a SIP configuration on Cisco2801 router (I used outgoing calls only):
translation-rule 10
Rule 0 ^90 0
Rule 1 ^91 1
Rule 2 ^92 2
Rule 3 ^93 3
Rule 4 ^94 4
Rule 5 ^95 5
Rule 6 ^96 6
Rule 7 ^97 7
Rule 8 ^98 8
Rule 9 ^99 9
interface FastEthernet0/0.1
description ***DATA VLAN***
encapsulation dot1Q 1 native
ip address 10.1.1.101 255.255.255.0
interface FastEthernet0/0.2
description ***VOICE VLAN***
encapsulation dot1Q 2
ip address 192.168.22.1 255.255.255.0
voice service voip
allow-connections h323 to h323
allow-connections h323 to sip
allow-connections sip to h323
allow-connections sip to sip
supplementary-service h450.12
h323
call start slow
sip
bind control source-interface FastEthernet0/0.2
bind media source-interface FastEthernet0/0.2
registrar server expires max 36000 min 600
voice class codec 1
codec preference 1 g729r8
codec preference 2 g711ulaw
codec preference 3 g711alaw
dial-peer voice 1 pots
description ### External Dialling via BRI ###
preference 7
destination-pattern 9T
translate-outgoing called 10
direct-inward-dial
port 0/0/0
forward-digits all
dial-peer voice 2 pots
description ### External Dialling via BRI ###
preference 2
destination-pattern 9T
translate-outgoing called 10
direct-inward-dial
port 0/0/1
forward-digits all
dial-peer voice 9000 voip
description ** Outgoing calls to SIP **
preference 1
destination-pattern 9T
voice-class sip dtmf-relay force rtp-nte
session protocol sipv2
session target ipv4:99.234.56.78:5060
dtmf-relay rtp-nte
codec g711alaw
no vad
sip-ua
timers connect 100
sip-server ipv4:99.234.56.78
I used debugging commands to troubleshoot the calls.
2801(config-dial-peer)#
094509: Jan 24 09:27:06.204: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Calling Number=211, Called Number=, Voice-Interface=0x65FA35B4,
Timeout=TRUE, Peer Encap Type=ENCAP_VOICE, Peer Search Type=PEER_TYPE_VOICE,
Peer Info Type=DIALPEER_INFO_SPEECH
094510: Jan 24 09:27:06.204: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Result=Success(0) after DP_MATCH_ORIGINATE; Incoming Dial-peer=20018
094511: Jan 24 09:27:06.716: //-1/6A877F6F9054/DPM/dpMatchPeersCore:
Calling Number=, Called Number=9, Peer Info Type=DIALPEER_INFO_SPEECH
094512: Jan 24 09:27:06.716: //-1/6A877F6F9054/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=9
094513: Jan 24 09:27:06.716: //-1/6A877F6F9054/DPM/dpMatchPeersCore:
Result=Partial Matches(1) after DP_MATCH_DEST
094514: Jan 24 09:27:06.716: //-1/6A877F6F9054/DPM/dpMatchPeersMoreArg:
Result=MORE_DIGITS_NEEDED(1)
094515: Jan 24 09:27:06.816: //-1/6A877F6F9054/DPM/dpMatchPeersCore:
Calling Number=, Called Number=90, Peer Info Type=DIALPEER_INFO_SPEECH
094516: Jan 24 09:27:06.816: //-1/6A877F6F9054/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=90
094517: Jan 24 09:27:06.816: //-1/6A877F6F9054/DPM/dpMatchPeersCore:
Result=Partial Matches(1) after DP_MATCH_DEST
094518: Jan 24 09:27:06.816: //-1/6A877F6F9054/DPM/dpMatchPeersMoreArg:
Result=MORE_DIGITS_NEEDED(1)
094519: Jan 24 09:27:06.912: //-1/6A877F6F9054/DPM/dpMatchPeersCore:
Calling Number=, Called Number=908, Peer Info Type=DIALPEER_INFO_SPEECH
094520: Jan 24 09:27:06.912: //-1/6A877F6F9054/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=908
094521: Jan 24 09:27:06.916: //-1/6A877F6F9054/DPM/dpMatchPeersCore:
Result=Partial Matches(1) after DP_MATCH_DEST
094522: Jan 24 09:27:06.916: //-1/6A877F6F9054/DPM/dpMatchPeersMoreArg:
Result=MORE_DIGITS_NEEDED(1)
094523: Jan 24 09:27:07.012: //-1/6A877F6F9054/DPM/dpMatchPeersCore:
Calling Number=, Called Number=9086, Peer Info Type=DIALPEER_INFO_SPEECH
094524: Jan 24 09:27:07.012: //-1/6A877F6F9054/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=9086
094525: Jan 24 09:27:07.016: //-1/6A877F6F9054/DPM/dpMatchPeersCore:
Result=Partial Matches(1) after DP_MATCH_DEST
094526: Jan 24 09:27:07.016: //-1/6A877F6F9054/DPM/dpMatchPeersMoreArg:
Result=MORE_DIGITS_NEEDED(1)
094527: Jan 24 09:27:07.116: //-1/6A877F6F9054/DPM/dpMatchPeersCore:
Calling Number=, Called Number=90862, Peer Info Type=DIALPEER_INFO_SPEECH
094528: Jan 24 09:27:07.116: //-1/6A877F6F9054/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=90862
094529: Jan 24 09:27:07.116: //-1/6A877F6F9054/DPM/dpMatchPeersCore:
Result=Partial Matches(1) after DP_MATCH_DEST
094530: Jan 24 09:27:07.116: //-1/6A877F6F9054/DPM/dpMatchPeersMoreArg:
Result=MORE_DIGITS_NEEDED(1)
094531: Jan 24 09:27:07.212: //-1/6A877F6F9054/DPM/dpMatchPeersCore:
Calling Number=, Called Number=908621, Peer Info Type=DIALPEER_INFO_SPEECH
094532: Jan 24 09:27:07.212: //-1/6A877F6F9054/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=908621
094533: Jan 24 09:27:07.216: //-1/6A877F6F9054/DPM/dpMatchPeersCore:
Result=Partial Matches(1) after DP_MATCH_DEST
094534: Jan 24 09:27:07.216: //-1/6A877F6F9054/DPM/dpMatchPeersMoreArg:
Result=MORE_DIGITS_NEEDED(1)
094535: Jan 24 09:27:07.316: //-1/6A877F6F9054/DPM/dpMatchPeersCore:
Calling Number=, Called Number=9086215, Peer Info Type=DIALPEER_INFO_SPEECH
094536: Jan 24 09:27:07.316: //-1/6A877F6F9054/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=9086215
094537: Jan 24 09:27:07.316: //-1/6A877F6F9054/DPM/dpMatchPeersCore:
Result=Partial Matches(1) after DP_MATCH_DEST
094538: Jan 24 09:27:07.316: //-1/6A877F6F9054/DPM/dpMatchPeersMoreArg:
Result=MORE_DIGITS_NEEDED(1)
094539: Jan 24 09:27:07.412: //-1/6A877F6F9054/DPM/dpMatchPeersCore:
Calling Number=, Called Number=90862157, Peer Info Type=DIALPEER_INFO_SPEECH
094540: Jan 24 09:27:07.412: //-1/6A877F6F9054/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=90862157
094541: Jan 24 09:27:07.416: //-1/6A877F6F9054/DPM/dpMatchPeersCore:
Result=Partial Matches(1) after DP_MATCH_DEST
094542: Jan 24 09:27:07.416: //-1/6A877F6F9054/DPM/dpMatchPeersMoreArg:
Result=MORE_DIGITS_NEEDED(1)
094543: Jan 24 09:27:07.516: //-1/6A877F6F9054/DPM/dpMatchPeersCore:
Calling Number=, Called Number=908621577, Peer Info Type=DIALPEER_INFO_SPEECH
094544: Jan 24 09:27:07.516: //-1/6A877F6F9054/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=908621577
094545: Jan 24 09:27:07.516: //-1/6A877F6F9054/DPM/dpMatchPeersCore:
Result=Partial Matches(1) after DP_MATCH_DEST
094546: Jan 24 09:27:07.516: //-1/6A877F6F9054/DPM/dpMatchPeersMoreArg:
Result=MORE_DIGITS_NEEDED(1)
094547: Jan 24 09:27:07.612: //-1/6A877F6F9054/DPM/dpMatchPeersCore:
Calling Number=, Called Number=9086215777, Peer Info Type=DIALPEER_INFO_SPEECH
094548: Jan 24 09:27:07.612: //-1/6A877F6F9054/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=9086215777
094549: Jan 24 09:27:07.616: //-1/6A877F6F9054/DPM/dpMatchPeersCore:
Result=Partial Matches(1) after DP_MATCH_DEST
094550: Jan 24 09:27:07.616: //-1/6A877F6F9054/DPM/dpMatchPeersMoreArg:
Result=MORE_DIGITS_NEEDED(1)
094551: Jan 24 09:27:07.716: //-1/6A877F6F9054/DPM/dpMatchPeersCore:
Calling Number=, Called Number=90862157774, Peer Info Type=DIALPEER_INFO_SPEECH
094552: Jan 24 09:27:07.716: //-1/6A877F6F9054/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=90862157774
094553: Jan 24 09:27:07.716: //-1/6A877F6F9054/DPM/dpMatchPeersCore:
Result=Partial Matches(1) after DP_MATCH_DEST
094554: Jan 24 09:27:07.716: //-1/6A877F6F9054/DPM/dpMatchPeersMoreArg:
Result=MORE_DIGITS_NEEDED(1)
094555: Jan 24 09:27:10.711: //-1/6A877F6F9054/DPM/dpMatchPeersCore:
Calling Number=, Called Number=90862157774T, Peer Info Type=DIALPEER_INFO_SPEECH
094556: Jan 24 09:27:10.711: //-1/6A877F6F9054/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=90862157774T
094557: Jan 24 09:27:10.711: //-1/6A877F6F9054/DPM/dpMatchPeersCore:
Result=Success(0) after DP_MATCH_DEST
094558: Jan 24 09:27:10.711: //-1/6A877F6F9054/DPM/dpMatchPeersMoreArg:
Result=SUCCESS(0)
List of Matched Outgoing Dial-peer(s):
1: Dial-peer Tag=9000
2: Dial-peer Tag=2
3: Dial-peer Tag=1
094559: Jan 24 09:27:10.711: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
Calling Number=90862157774, Called Number=90862157774, Peer Info Type=DIALPEER_INFO_SPEECH
094560: Jan 24 09:27:10.711: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=90862157774
094561: Jan 24 09:27:10.715: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
Result=Success(0) after DP_MATCH_DEST
094562: Jan 24 09:27:10.715: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersMoreArg:
Result=SUCCESS(0)
List of Matched Outgoing Dial-peer(s):
1: Dial-peer Tag=9000
2: Dial-peer Tag=2
3: Dial-peer Tag=1
094563: Jan 24 09:27:10.715: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Calling Number=90862157774, Called Number=, Voice-Interface=0x0,
Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search Type=PEER_TYPE_VOICE,
Peer Info Type=DIALPEER_INFO_SPEECH
094564: Jan 24 09:27:10.715: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Result=Success(0) after DP_MATCH_ORIGINATE; Incoming Dial-peer=9000
094565: Jan 24 09:27:10.715: //-1/6A877F6F9054/DPM/dpMatchPeersCore:
Calling Number=, Called Number=90862157774, Peer Info Type=DIALPEER_INFO_SPEECH
094566: Jan 24 09:27:10.715: //-1/6A877F6F9054/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=90862157774
094567: Jan 24 09:27:10.715: //-1/6A877F6F9054/DPM/dpMatchPeersCore:
Result=Success(0) after DP_MATCH_DEST
094568: Jan 24 09:27:10.715: //-1/6A877F6F9054/DPM/dpMatchPeersMoreArg:
Result=SUCCESS(0)
List of Matched Outgoing Dial-peer(s):
1: Dial-peer Tag=9000
2: Dial-peer Tag=2
3: Dial-peer Tag=1
094569: Jan 24 09:27:10.719: fb_get_reject_cause_code: ERROR cause_code NULL
094570: Jan 24 09:27:10.727: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.22.1:5060;branch=z9hG4bK47D116D3
Remote-Party-ID: "Sam " <sip:[email protected]>;party=calling;screen=no;privacy=off
From: "Sam " <sip:[email protected]>;tag=CDCFB8AC-F98
To: <sip:[email protected]>
Date: Tue, 24 Jan 2012 09:27:10 GMT
Call-ID: [email protected]
Supported: 100rel,timer,resource-priority,replaces
Min-SE: 1800
Cisco-Guid: 1787264879-1168380385-2421457215-1958389771
User-Agent: Cisco-SIPGateway/IOS-12.x
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 101 INVITE
Max-Forwards: 70
Timestamp: 1327397230
Contact: <sip:[email protected]:5060>
Expires: 180
Allow-Events: telephone-event
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 244
v=0
o=CiscoSystemsSIP-GW-UserAgent 3237 2021 IN IP4 192.168.22.1
s=SIP Call
c=IN IP4 192.168.22.1
t=0 0
m=audio 18258 RTP/AVP 8 101
c=IN IP4 192.168.22.1
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=ptime:20
094571: Jan 24 09:27:11.227: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.22.1:5060;branch=z9hG4bK47D116D3
Remote-Party-ID: "Sam" <sip:[email protected]>;party=calling;screen=no;privacy=off
From: "Sam " <sip:[email protected]>;tag=CDCFB8AC-F98
To: <sip:[email protected]>
Date: Tue, 24 Jan 2012 09:27:11 GMT
Call-ID: [email protected]
Supported: 100rel,timer,resource-priority,replaces
Min-SE: 1800
Cisco-Guid: 1787264879-1168380385-2421457215-1958389771
User-Agent: Cisco-SIPGateway/IOS-12.x
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 101 INVITE
Max-Forwards: 70
Timestamp: 1327397231
Contact: <sip:[email protected]:5060>
Expires: 180
Allow-Events: telephone-event
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 244
v=0
o=CiscoSystemsSIP-GW-UserAgent 3237 2021 IN IP4 192.168.22.1
s=SIP Call
c=IN IP4 192.168.22.1
t=0 0
m=audio 18258 RTP/AVP 8 101
c=IN IP4 192.168.22.1
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=ptime:20
094572: Jan 24 09:27:12.227: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.22.1:5060;branch=z9hG4bK47D116D3
Remote-Party-ID: "Sam " <sip:[email protected]>;party=calling;screen=no;privacy=off
From: "Sam " <sip:[email protected]>;tag=CDCFB8AC-F98
To: <sip:[email protected]>
Date: Tue, 24 Jan 2012 09:27:12 GMT
Call-ID: [email protected]
Supported: 100rel,timer,resource-priority,replaces
Min-SE: 1800
Cisco-Guid: 1787264879-1168380385-2421457215-1958389771
User-Agent: Cisco-SIPGateway/IOS-12.x
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 101 INVITE
Max-Forwards: 70
Timestamp: 1327397232
Contact: <sip:[email protected]:5060>
Expires: 180
Allow-Events: telephone-event
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 244
v=0
o=CiscoSystemsSIP-GW-UserAgent 3237 2021 IN IP4 192.168.22.1
s=SIP Call
c=IN IP4 192.168.22.1
t=0 0
m=audio 18258 RTP/AVP 8 101
c=IN IP4 192.168.22.1
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=ptime:20
094573: Jan 24 09:27:14.227: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.22.1:5060;branch=z9hG4bK47D116D3
Remote-Party-ID: "Sam" <sip:[email protected]>;party=calling;screen=no;privacy=off
From: "Sam" <sip:[email protected]>;tag=CDCFB8AC-F98
To: <sip:[email protected]>
Date: Tue, 24 Jan 2012 09:27:14 GMT
Call-ID: [email protected]
Supported: 100rel,timer,resource-priority,replaces
Min-SE: 1800
Cisco-Guid: 1787264879-1168380385-2421457215-1958389771
User-Agent: Cisco-SIPGateway/IOS-12.x
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 101 INVITE
Max-Forwards: 70
Timestamp: 1327397234
Contact: <sip:[email protected]:5060>
Expires: 180
Allow-Events: telephone-event
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 244
v=0
o=CiscoSystemsSIP-GW-UserAgent 3237 2021 IN IP4 192.168.22.1
s=SIP Call
c=IN IP4 192.168.22.1
t=0 0
m=audio 18258 RTP/AVP 8 101
c=IN IP4 192.168.22.1
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=ptime:20
I made some changes in the router configuration.
I removed FA0/0.2 Voice interface from Voice service voip configuration (bind control source-interface FastEthernet0/0.2 and bind media source-interface FastEthernet0/0.2). And now it’s using ip address 10.1.1.101 (data ip).
The debugging is changed now. I can send and receive a respond from SIP server. But It shows an error: SIP/2.0 404 Not Found
Then it moves to ISDN line, and use this line to make a call.
102988: Jan 24 14:45:47.290: //-1/EDCA21089304/DPM/dpMatchPeersCore:
Calling Number=, Called Number=90862157774T, Peer Info Type=DIALPEER_INFO_SPEECH
102989: Jan 24 14:45:47.290: //-1/EDCA21089304/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=90862157774T
102990: Jan 24 14:45:47.290: //-1/EDCA21089304/DPM/dpMatchPeersCore:
Result=Success(0) after DP_MATCH_DEST
102991: Jan 24 14:45:47.290: //-1/EDCA21089304/DPM/dpMatchPeersMoreArg:
Result=SUCCESS(0)
List of Matched Outgoing Dial-peer(s):
1: Dial-peer Tag=9000
2: Dial-peer Tag=2
3: Dial-peer Tag=1
102992: Jan 24 14:45:47.290: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
Calling Number=90862157774, Called Number=90862157774, Peer Info Type=DIALPEER_INFO_SPEECH
102993: Jan 24 14:45:47.290: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=90862157774
102994: Jan 24 14:45:47.294: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
Result=Success(0) after DP_MATCH_DEST
102995: Jan 24 14:45:47.294: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersMoreArg:
Result=SUCCESS(0)
List of Matched Outgoing Dial-peer(s):
1: Dial-peer Tag=9000
2: Dial-peer Tag=2
3: Dial-peer Tag=1
102996: Jan 24 14:45:47.294: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Calling Number=90862157774, Called Number=, Voice-Interface=0x0,
Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search Type=PEER_TYPE_VOICE,
Peer Info Type=DIALPEER_INFO_SPEECH
102997: Jan 24 14:45:47.294: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Result=Success(0) after DP_MATCH_ORIGINATE; Incoming Dial-peer=9000
102998: Jan 24 14:45:47.294: //-1/EDCA21089304/DPM/dpMatchPeersCore:
Calling Number=, Called Number=90862157774, Peer Info Type=DIALPEER_INFO_SPEECH
102999: Jan 24 14:45:47.294: //-1/EDCA21089304/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=90862157774
103000: Jan 24 14:45:47.294: //-1/EDCA21089304/DPM/dpMatchPeersCore:
Result=Success(0) after DP_MATCH_DEST
103001: Jan 24 14:45:47.294: //-1/EDCA21089304/DPM/dpMatchPeersMoreArg:
Result=SUCCESS(0)
List of Matched Outgoing Dial-peer(s):
1: Dial-peer Tag=9000
2: Dial-peer Tag=2
3: Dial-peer Tag=1
103002: Jan 24 14:45:47.298: fb_get_reject_cause_code: ERROR cause_code NULL
103003: Jan 24 14:45:47.310: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 10.1.1.101:5060;branch=z9hG4bK4875CB9
Remote-Party-ID: "Sam" <sip:[email protected]>;party=calling;screen=no;privacy=off
From: "Seam" <sip:[email protected]>;tag=CEF37490-172C
To: <sip:[email protected]>
Date: Tue, 24 Jan 2012 14:45:47 GMT
Call-ID: [email protected]
Supported: 100rel,timer,resource-priority,replaces
Min-SE: 1800
Cisco-Guid: 3989446920-1171263969-2466545983-1958389771
User-Agent: Cisco-SIPGateway/IOS-12.x
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 101 INVITE
Max-Forwards: 70
Timestamp: 1327416347
Contact: <sip:[email protected]:5060>
Expires: 180
Allow-Events: telephone-event
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 247
v=0
o=CiscoSystemsSIP-GW-UserAgent 2438 9821 IN IP4 10.1.1.101
s=SIP Call
c=IN IP4 10.1.1.101
t=0 0
m=audio 19412 RTP/AVP 8 101
c=IN IP4 10.1.1.101
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=ptime:20
103004: Jan 24 14:45:47.354: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 404 Not Found
From: "Sam "<sip:[email protected]>;tag=CEF37490-172C
To: <sip:[email protected]>;tag=7fad61f03708-100007f-13c4-55013-a0142-10fd12c8-a0142
Call-ID: [email protected]
CSeq: 101 INVITE
Via: SIP/2.0/UDP 10.1.1.101:5060;received=88.99.77.44;branch=z9hG4bK4875CB9
Content-Length: 0
103005: Jan 24 14:45:47.362: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
ACK sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 10.1.1.101:5060;branch=z9hG4bK4875CB9
From: "Sam " <sip:[email protected]>;tag=CEF37490-172C
To: <sip:[email protected]>;tag=7fad61f03708-100007f-13c4-55013-a0142-10fd12c8-a0142
Date: Tue, 24 Jan 2012 14:45:47 GMT
Call-ID: [email protected]
Max-Forwards: 70
CSeq: 101 ACK
Allow-Events: telephone-event
Content-Length: 0
103006: Jan 24 14:45:47.374: %ISDN-6-LAYER2UP: Layer 2 for Interface BR0/0/1, TEI 96 changed to up
103007: Jan 24 14:45:51.313: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
Calling Number=, Called Number=211, Peer Info Type=DIALPEER_INFO_SPEECH
103008: Jan 24 14:45:51.313: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=211
103009: Jan 24 14:45:51.317: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
Result=Success(0) after DP_MATCH_DEST
103010: Jan 24 14:45:51.317: //-1/xxxxxxxxxxxx/DPM/dpMatchPeers:
Result=SUCCESS(0)
List of Matched Outgoing Dial-peer(s):
1: Dial-peer Tag=20018
103011: Jan 24 14:45:51.317: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
Calling Number=, Called Number=0862157774, Peer Info Type=DIALPEER_INFO_SPEECH
103012: Jan 24 14:45:51.317: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=0862157774
103013: Jan 24 14:45:51.317: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
No Outgoing Dial-peer Is Matched; Result=NO_MATCH(-1)
103014: Jan 24 14:45:51.317: //-1/xxxxxxxxxxxx/DPM/dpMatchPeers:
Result=NO_MATCH(-1)
103015: Jan 24 14:46:08.815: %ISDN-6-LAYER2DOWN: Layer 2 for Interface BR0/0/1, TEI 96 changed to down
2801(config-dial-peer)#
Then I removed SIP-UA as I was told there is no registration necessary, only Dial-peer configuration.
But it didn’t affect anything.
Then I add translate-outgoing called 10 command to dial-peer 9000, nothing happened.
Really stuck and don't know where to look at.
Any help will be highly appreciated.
Thanks.Hi Dan.
Yes, I saw that RTP debugging, but what can I change there? Maybe I need to open more ports on ASA for RTP like 19412?
I use Cisco ASDM for ASA to make changes.
There are static NAT rules for: Server source IPs(10.1.1.100) to Outside(translated IPs, 88.99.77.44) for a few ports.
Also I added Security policy access rules for LAN: Any to SIP, and Outside: SIP to any.
For NAT:
I can't add this: for LAN: STATIC ROUTER IP 10.1.1.101 (AS SOURCE) UDP 5060 TO OUTSIDE IP 88.99.77.44
(AS TRANSLATED) UDP 5060
Because there is already translation for the Server.
Debugging looks like that now. There is no Received: SIP/2.0, but I can make an outside call with no audio.
116013: Jan 25 15:28:25.584: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Calling Number=90862157774, Called Number=, Voice-Interface=0x0,
Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search Type=PEER_TYPE_VOICE,
Peer Info Type=DIALPEER_INFO_SPEECH
116014: Jan 25 15:28:25.584: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Result=Success(0) after DP_MATCH_ORIGINATE; Incoming Dial-peer=9000
116015: Jan 25 15:28:25.584: //-1/0D0EB9CE9708/DPM/dpMatchPeersCore:
Calling Number=, Called Number=90862157774, Peer Info Type=DIALPEER_INFO_SPEECH
116016: Jan 25 15:28:25.584: //-1/0D0EB9CE9708/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=90862157774
116017: Jan 25 15:28:25.584: //-1/0D0EB9CE9708/DPM/dpMatchPeersCore:
Result=Success(0) after DP_MATCH_DEST
116018: Jan 25 15:28:25.584: //-1/0D0EB9CE9708/DPM/dpMatchPeersMoreArg:
Result=SUCCESS(0)
List of Matched Outgoing Dial-peer(s):
1: Dial-peer Tag=9000
2: Dial-peer Tag=2
3: Dial-peer Tag=1
116019: Jan 25 15:28:25.588: fb_get_reject_cause_code: ERROR cause_code NULL
116020: Jan 25 15:28:25.600: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 10.1.1.101:5060;branch=z9hG4bK491484D
Remote-Party-ID: "Sam " ;party=calling;screen=no;privacy=off
From: "Sam " ;tag=D4410748-1C9D
To:
Date: Wed, 25 Jan 2012 15:28:25 GMT
Call-ID: [email protected]
Supported: 100rel,timer,resource-priority,replaces
Min-SE: 1800
Cisco-Guid: 219068878-1184895457-2533916991-1958389771
User-Agent: Cisco-SIPGateway/IOS-12.x
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 101 INVITE
Max-Forwards: 70
Timestamp: 1327505305
Contact:
Expires: 180
Allow-Events: telephone-event
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 247
v=0
o=CiscoSystemsSIP-GW-UserAgent 1984 5803 IN IP4 10.1.1.101
s=SIP Call
c=IN IP4 10.1.1.101
t=0 0
m=audio 18782 RTP/AVP 8 101
c=IN IP4 10.1.1.101
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=ptime:20
116021: Jan 25 15:28:26.096: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 10.1.1.101:5060;branch=z9hG4bK491484D
Remote-Party-ID: "Sam " ;party=calling;screen=no;privacy=off
From: "Sam " ;tag=D4410748-1C9D
To:
Date: Wed, 25 Jan 2012 15:28:26 GMT
Call-ID: [email protected]
Supported: 100rel,timer,resource-priority,replaces
Min-SE: 1800
Cisco-Guid: 219068878-1184895457-2533916991-1958389771
User-Agent: Cisco-SIPGateway/IOS-12.x
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 101 INVITE
Max-Forwards: 70
Timestamp: 1327505306
Contact:
Expires: 180
Allow-Events: telephone-event
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 247
v=0
o=CiscoSystemsSIP-GW-UserAgent 1984 5803 IN IP4 10.1.1.101
s=SIP Call
c=IN IP4 10.1.1.101
t=0 0
m=audio 18782 RTP/AVP 8 101
c=IN IP4 10.1.1.101
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=ptime:20
116022: Jan 25 15:28:27.096: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 10.1.1.101:5060;branch=z9hG4bK491484D
Remote-Party-ID: "Sam " ;party=calling;screen=no;privacy=off
From: "Sam " ;tag=D4410748-1C9D
To:
Date: Wed, 25 Jan 2012 15:28:27 GMT
Call-ID: [email protected]
Supported: 100rel,timer,resource-priority,replaces
Min-SE: 1800
Cisco-Guid: 219068878-1184895457-2533916991-1958389771
User-Agent: Cisco-SIPGateway/IOS-12.x
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 101 INVITE
Max-Forwards: 70
Timestamp: 1327505307
Contact:
Expires: 180
Allow-Events: telephone-event
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 247
v=0
o=CiscoSystemsSIP-GW-UserAgent 1984 5803 IN IP4 10.1.1.101
s=SIP Call
c=IN IP4 10.1.1.101
t=0 0
m=audio 18782 RTP/AVP 8 101
c=IN IP4 10.1.1.101
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=ptime:20
116026: Jan 25 15:28:57.092: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 10.1.1.101:5060;branch=z9hG4bK491484D
Remote-Party-ID: "Sam" ;party=calling;screen=no;privacy=off
From: "Sam " ;tag=D4410748-1C9D
To:
Date: Wed, 25 Jan 2012 15:28:57 GMT
Call-ID: [email protected]
Supported: 100rel,timer,resource-priority,replaces
Min-SE: 1800
Cisco-Guid: 219068878-1184895457-2533916991-1958389preference 1771
User-Agent: Cisco-SIPGateway/IOS-12.x
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 101 INVITE
Max-Forwards: 70
Timestamp: 1327505337
Contact:
Expires: 180
Allow-Events: telephone-event
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 247
v=0
o=CiscoSystemsSIP-GW-UserAgent 1984 5803 IN IP4 10.1.1.101
s=SIP Call
c=IN IP4 10.1.1.101
t=0 0
m=audio 18782 RTP/AVP 8 101
c=IN IP4 10.1.1.101
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=ptime:20
I'll add Incoming dial-peer now.
Not sure what kind of NAT rule should I put into ASA to allow in and out sip traffic.
Appretiate your help.
Thanks a mill. -
Hi,
We are implementing the IPCCX version 8.0.2 and I am the following doubt: For all inbound call that are forward to CTI Route Point (IPCCX) is open the transcoding session. I would like know it is possible not is use the transcoding. If there this possibility, I need that DTMF could be forward the correctly to IPCCX. Is there the possibility?
Thanks,
WilsonHi Abu,
Below is my scenario:
IPCCX Environment:
· The calls to arrive in the ITSP by CUBE that forward the calls to CUCM:
ITSP ß SIPà CUBE ßSIPàCUCM
- Configuration Dial-peer in the CUBE:
dial-peer voice 100 voip
translation-profile incoming coloca-prefixo-SPO
destination-pattern xxxxxx....
session protocol sipv2
session target ipv4:x.x.x.x
incoming called-number xxxxxx....
voice-class codec 1
voice-class sip early-offer forced
dtmf-relay rtp-nte
no vad
· The Calls enter in the CUCM and is associate with CTI Route Point to IPCCX;
· The IPCCX is configured to work with codec g729;
· The Region of IPCCX is configured to work in codec g729 with another Region configured in the CUBE;
· O SIP TRUNK is configured to not work MTP;
· O SIP TRUNK is configured to work with DTMF RFC2833;
Unity Environment:
· The Calls arrive of the ITSP by CUBE that forward the calls to CUCM:
ITSP ß SIPà CUBE ßSIPàCUCM
- Configuration Dial-peer in the CUBE:
dial-peer voice 100 voip
translation-profile incoming coloca-prefixo-SPO
destination-pattern xxxxxx....
session protocol sipv2
session target ipv4:x.x.x.x
incoming called-number xxxxxx....
voice-class codec 1
voice-class sip early-offer forced
dtmf-relay rtp-nte
no vad
· The Calls to enter in the CUCM and is forward to UNITY by VOICE-Mail Ports;
· Unity can work codec g729 ou g711;
· Region of Unity with Region do SIP TRUNK is configured to work with g729.
· O SIP TRUNK is configured to not work MTP;
· O SIP TRUNK is configured to work with DTMF RFC2833;
The transcode is using in this solution because is implemented G711 to call internal and G229 to external calls.
Thanks,
Wilson -
CUBE - DTMF Interworking between SIP INFO and RFC2833
Hi all,
After some testing I noticed that when the cube receives dtmf via SIP INFO it doesn't translate them into rfc2833 on the other side. This happens when the incoming INVITE advertises both SIP INFO and RFC2833.
When the incoming INVITE advertises only SIP INFO then it does the translation to RFC2833 and sends the digits via RTP on the outgoing interface.
CUBE supports both RFC2833 and SIP INFO as it advertises both methods in it's sip messages. Is this the expected behaviour ?
IOS is 15.1(3)T1. CUBE is running on a 3945 router.
I have found bug CSCuh65102 which seems to be a match. Can somebody confirm this ?Hi,
Please check the following bug
https://tools.cisco.com/bugsearch/bug/CSCtj93573/?reffering_site=dumpcr
CUBE not processing DTMF SIP INFO to RFC 2833 upstream to Network
You can try an upgrade to 15.1(3)T4 or higher and check if the issue is resolved.
HTH
Manish -
We are experiencing a problem with DTMF tones on external attendants. We have a CCM 4.2 cluster connected to a CUCM 8.6.1 via a QSIG ICT.
CCM 4.2 <--> ICT <--> CUCM 8.6 <--> CUBE <--> SIP
DTMF works OK from phones in the CUCM 8.6 cluster. All inbound DTMF works all the way through to the CCM 4.2 cluster. However, DTMF from phones in the CCM 4.2 cluster does not work. It was working OK last week when some changes (adding CUC integration) were made. I have tried reversing most of the changes, but cant get it working again.
Any ideas or TS steps recommended? Thanks!Two things to add on this thread:
The statement "these are outbound calls - so they don't hit a VoIP peer." is not true. There is always an inbound and outbound dial-peer matched on IOS. If you do not have an inbound dial-peer to match, IOS will use dial-peer 0 which is almost always a bad thing. Make sure you have a VoIP dial-peer that will match for inbound calls from UCM to the router.
CCX does not support in-band DMTF such as RFC2833 with SIP. If you do not have OOB DTMF such as KPML (RFC4730) or H.245 alphanumeric, then you need to invoke an MTP for conversion. -
When I try to join a Webex, and have the system call me on my VoIP line through my SPA112, it seems that the * key is not recognized. I can use the phone to interact with other menu systems, such as my bank. But for some reason, I can't get into a Webex without dialing manually into the conference.
I use Vitelity as my SIP provider. They support G.711u, G.711a, and G.729a codecs. They prefer RFC2833 for DTMF Tx method, but I've also had success in the past with inband.
I should also mention that I've had sporadic luck getting into Webex in the past with this same configuration using the SPA112 with G.729a and Inband (though that really shouldn't work consistently because of the compression).
Just as a troubleshooting step, I tried calling the VoIP line from another phone to make sure I could hear the * key. I could hear it, even when I was using ATV (RFC2833) which I didn't think was going to be the case. However, I don't seem to be able to control the length of the tone - though I have no idea whether the length is a problem or not.
At the moment, I'm trying to generate a log from the SPA112 that would include the DTMF tones. Can anyone help me with the right settings so that I can see these in my log? Thanks.Just turn on syslog and debug to the highest level possible, send the messages to an external server and catch them all here (with either a syslogd server software or by a generic packet catcher like tcpdump or Wireshark). There is no more detailed log possible.
You can catch SIP packets and RTP stream (just the part with DTMF) as well. -
ATA 186 Reproducing DTMF tones from RFC2833 events
I am trying to get my ATA 186 (running version SCCP 3.x under CCM 5.04a) to reproduce received rtp-events. This is supporting a third-party IVR system that is connected via analog ports.
The IOS gateway that is sending the events is configured for dtmf-relay rtp-nte, and I can see the RTP events being received at the ATA. However, all I hear at the ATA is nothing or clicks.
I have the audiomode setting on the ATA set to 0x00150015 as is recommended in the ATA administrators guide.
Does anyone have DTMF working through the ATA?Hi Kevin,
have you debugged the ATA with prserv.exe?
I had some issues in the past with a PESQ tester, and setting the audiomode to 0x00120012 helped for me.
hth
Sascha
....this is the output from prserv on a good call
|->CallState[0]=4 L=1 R=4016c6c FG=0 r=0,0
FG NewState[0]=4, L=1, R=4016c6c
|->CallInfo[0]
|->SetRingerMode[0]:3
<-|StOffHk[0]
|->SetRingerMode[0]:1
|->CallState[0]=1 L=1 R=4016c6c FG=0 r=4016c6c,0
|->SetRingerMode[0]:1
[0]StopTone
|->CallState[0]=5 L=1 R=4016c6c FG=0 r=4016c6c,0
|->CallInfo[0]
[0]StopTone
|->OpenRxChn[0]
[0]StopTone
<-|OpenRxChnAck[0]
Save Media[0]
|->StartMediaTx[0]:pt=0 ps=20 ss=0 ip=a63801f:19422
[0]MPT mode 0
[2]MPT mode 0
Enable LEC adapt [0]=1
[0]Enable encoder 0
[0]DPKT 1st: 3680 3520, pt 0
15948:00;2,0,0,0,
[0]DTMF 1 , insum:323505
[0]StopTone
[0]DTMF 2 , insum:285988
[0]DTMF 3 , insum:289227
[0]DTMF 4 , insum:287021
[0]DTMF 5 , insum:284108
[0]DTMF 6 , insum:286979
[0]DTMF 7 , insum:284993
[0]DTMF 8 , insum:302792
[0]DTMF 9 , insum:293475
[0]DTMF 0 , insum:293768
[0]DTMF * , insum:279360
[0]DTMF # , insum:301230
<-|EndCall[0]
<-|SK[0]:9, L=1, FGR=4016c6c
[0]StopTone
->CloseRxChn[0]
|->StopMediaTx[0]
|->CallState[0]=2 L=1 R=4016c6c FG=0 r=4016c6c,0
IDLE[0]
|->SetRingerMode[0]:1
15948:30;2,0,0,0, -
We have noticed that something changed between ICM 7.5 and 8.5 and/or CVP 7.0 and 8.5. We have one or two situations where a call comes into the CVP Ingress Gateway, does the normal CUSP>CVP stuff, kicks off an ICM script and ICM immediately responds with a Label that evokes a DTMF *8 for Take-Back And Transfer. In ICM 7.5/CVP 7.0, this worked fine even without setting any VXML parameters or extending the RTP from the Ingress GW to the VXML GW. Ever since we migrated to ICM 8.5/CVP 8.5 and new IOS on the Ingress (15.0(1)M7) and VXML GWs (15.1(3)T1), the only way we can make the TBAT work is by playing a silence.wav file via a simple VXML app. It seems like the new versions moved the code needed for DTMF from the Ingress GW to the VXML GW, or something. I’ve tried searching Cisco.com for this issue but haven’t found anything yet.
Hi,
In BPS, you can use user specific variables or you can set up a Variable of type exit. You can also have a variable of type authorization which uses the security / authorization of the BW system.
Hope it helps...
Cheers,
Tanish -
DTMF issues on SIP trunk to Verizon
Were you able to resolve this problem? I am having an identical issue also with Verizon.
Our topology and symptoms are as follows:
Outside phone -> PSTN -> Vzn SBC -> Vzn SIP trunk -> CUBE -> CUCM / VM system
DTMF tones generated by an IP phone are heard and recognized by an outside (off-net) phone/system as you would expect. However, DTMF tones generated by an outside (off-net) phone are not recognized by our voice mail system. When listening to the DTMF tone on an IP phone, it sounds very distorted and faint. A sniffer trace performed on the CUBE shows RFC 2833 NTEs being received from Verizon, and they appear to be properly relayed by the CUBE to the destination. Payload type negotiated for both legs is 101.
We are running CUCM 6.1.5. We have a CUBE router between CUCM and the Verizon SIP trunk. The CUBE router is running 12.4(24)T3 with the IPIPGW feature set. Our voice mail system is an AVST CallXpress system running v7.9 software. To CUCM the AVST voice mail ports appear as DNs assigned to several SCCP 7940 phones (DNs are part of a hunt group, hunt pilot = vm pilot). The AVST masquerades and registers as the 7940 phones.
I tried applying the "dtmf-interworking rtp-nte" both globally and at the dial-peer level with no success. Attached is the debug output you suggested. -
Hi All,
I have an issue here. The DTMF is not recognized by the Unity when user wants to do remote login to voicemail box by pressing *
Call Flow : T1 --> AS5400 --> SIP Trunk --> CUCM 9.1.2 --> SCCP --> CUC 9.1.2
Time : Nov 12 20:06:56.417 UTC
Calling Party Number i = 0x1183, '914466553077'
Called Party Number i = 0xA1, '2067677' - 99992067677
I can see in CCAPI, * being pressed and NOTIFY message is sent to CUCM, and I get 403 Forbidden as response.
The dial-peer configuration point to CUCM is below
dial-peer voice 4320 voip
tone ringback alert-no-PI
description --- PSTN to XXX 9999.XXXXXXX ---
preference 1
destination-pattern 9999.......$
no modem passthrough
session protocol sipv2
session target ipv4:XXXXX
voice-class codec 1
voice-class sip early-offer forced
voice-class sip options-keepalive
dtmf-relay sip-notify rtp-nte
fax rate 7200
ip qos dscp cs3 signaling
no vad
Logs are attached. Please help me to find out the issue.ok..We need to use a different approach to resolve this..We need to prefix calls coming from cucm so as to break up the overlapping issue..
do this..
go to cucm, search for the Route list you use for outbound calls, click on the route group associated with it.
Under called party xformation
under discard digits: use to none
prefix digit outgoing calls: add 141 as shown below -
CUBE - New Deployment Issue - Not working DTMF Relay
Hello,
Scheme:
Cisco SCCP-based IP Phone > CUCM 9.1 w/ SIP Trunk > CUBE (28XX, 151-4.M7) > SIP ITSP
CUCM Active Call Proc. Node IP: 10.10.10.9
CUBE Inside Interface IP: 10.10.10.10
CUBE Outside Interface IP: 20.20.20.20
Cisco IP Phone: 10.10.10.8
ITSP SBC IP: 30.30.30.30
ITSP SIP domain: itsp.domain
Calling Pty: 9017654321 (translated in CUCM's route pattern which addresses CUBE)
Called Pty: 9011234567
While call was connected calling party dialed consequently 0,1,2,3,4 but far-end IVR does not react :(
Symptom:
While outbound call is connected calling party (IP Phone) dials digits which are not detected by any far-end PSTN (non-corporate) IVR at all.
Thoughts:
ITSP support only inband relay (RFC2833, Named Telephone Events or NTEs).
Using NTE provides a standard way to transport DTMF tones in RTP packets.
Thus rtp-nte is configured for both CUCM and ITSP dial-peers on CUBE.
While initial troubleshooting found that for the active call inbound CUBE's leg shows rtp-nte, but outbound inband-voice.
A have an assumption that ITSP doesn't give us 101=rtp-nte payload in 183 Response but I'm not sure.
m=audio 10318 RTP/AVP 8
b=AS:64
a=rtpmap:8 PCMA/8000
a=ptime:20
a=maxptime:20
Questions:
1.How to make CUBE to successfully relay DTMF in according to ITSP requirement?
2. Why 'show call act/hist voice brief' doesn't show call id? All my attempts are identified as 2... )
It is hard to differentiate b/w call active/history records..Ayodeji,
Thanks for your feedback.
If you look through the already attached output 'show call act voice' of the file 'case-no-dtmf_-_cube-show-20140210-1.txt' you will find the following:
PeerId=101
CallOrigin=2
tx_DtmfRelay=rtp-nte
CallDuration=00:00:05 sec
PeerId=201
CallOrigin=1
tx_DtmfRelay=inband-voice
CallDuration=00:00:05 sec
2 : 230 18:40:38.048 MSK Tue Feb 10 2015.1 +1890 pid:101 Answer 79017654321 active
dur 00:00:04 tx:234/37440 rx:233/37280
IP 10.10.10.8:22688 SRTP: off rtt:0ms pl:0/0ms lost:0/0/0 delay:0/0/0ms g711alaw TextRelay: off
media inactive detected:n media contrl rcvd:n/a timestamp:n/a
long duration call detected:n long duration call duration:n/a timestamp:n/a
2 : 231 18:40:38.068 MSK Tue Feb 10 2015.1 +1860 pid:201 Originate 79011234567 active
dur 00:00:04 tx:233/37280 rx:307/49120
IP 30.30.30.30:10318 SRTP: off rtt:0ms pl:0/0ms lost:0/0/0 delay:0/0/0ms g711alaw TextRelay: off
media inactive detected:n media contrl rcvd:n/a timestamp:n/a
long duration call detected:n long duration call duration:n/a timestamp:n/a
This means that the target dial-peers (inbound and outbound are matched as designed).
dial-peer voice 101 voip
description -= inbound leg from CUCM to CUBE =-
session protocol sipv2
incoming called-number x
voice-class codec 1
voice-class sip bind control source-interface Loopback0
voice-class sip bind media source-interface Loopback0
dtmf-relay rtp-nte
no vad
dial-peer voice 201 voip
description -= outbound leg from CUBE to ITSP =-
translation-profile outgoing cdpn-delete-prefix-00XX7
max-conn 40
destination-pattern x
session protocol sipv2
session target dns:sbc.itsp.domain
voice-class codec 1
voice-class sip profiles 1
voice-class sip bind control source-interface Vlan100
voice-class sip bind media source-interface Vlan100
dtmf-relay rtp-nte
no vad
Now I have an argue with ITSP to make them send me NTE in their 183/200 response..
I've also:
1. Tried to disable dtmf-relay at all on dial-peers (trying inband-voice) but this doesn't work and also not recommended AFAIK.
2. Changed the value for SIP Trunk DTMF Signaling Method from 'No preference' to 'RFC 2833' w/ reset applied recommended by Suresh. No luck. -
DTMF Digits Dialing issue on 8831 Conference Phone
Hi,
anyone had a DTMF digits dialing issue on Cisco 8831 conference phone. If I have to join any external conference bridge, when I trying dial my user id and password its not sending the digit i am dialing. Conference bridge is saying wrong PIN dialed.Please suggestHi
Actually this problem was on SIP call,User was dialing shortcode and it was going through their SIP trunk, raised case with TAC and they replied "its expected behavior and documented in the release guides, we do not find any defects filed to fix this. we are hoping, this behavioral change would be included in the future releases"
version of call manager 9.1.2.11900-12
current firmware running on the phone-SIP 9.3.3.5 -
IPhone 5s iOS 8.0.2 does not recognize DTMF tones when dialing an automated service. I end up losing the call because automated service does not received a response from me.
Is there a setting adjustment that needs to me made and if so, where is this located?Hello Manish
Thanks for your reply. So here is the thing. It was just as i feared, by leaving this "REQUIRE MTP" check on the SIP trunk, now all video calls are being setup as Audio only. So this is not a good solution.
It would be nice is the MTP is only invoked for the audio only callers, from my reading this is how its supposed to work.
I suppose as another workaround, not elegant but should work I could go to the H.323 Gateway and make a specific dial-peer for this one pattern that points to Conductor for audio participants and change this to be a SIP dial-peer then setup a SIP trunk from CUCM to the same voice gateway.
Seems a little strange, i was hoping i can make this work just as it is.
Has anyone else run into this issue?
Maybe you are looking for
-
Help with Using One Master Account on a NAS server in ALAC
I want to use my Netgear ReadyNAS server to hold my music, which I am going to re-rip into Apple Lossless (using dBpoweramp converter and a sony xl1b -so as to do 200 discs at a time). That server is mainly used by my home 2008 Mac Pro. So the iTunes
-
How can I run a Local PC executable file from Enterprise Portal?
I want to run local PC executable files from inside the portal. To be more specific I want to be able to open the Outlook and some powerbuilder executable applications. How can I do it?
-
This happens every time when shutting down the system?
-
How do you get purchased music back to ipod?
I have synced but recently purchased music is not there. Help!
-
Slow-loading browser background
Good morning. I am attempting to create a website based on a booklet I published 25 years ago. The scanned pages of the actual booklet are my page background. Each page has an original photograph constituting the browser background. When viewing the