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

sip trunk configuration problems with cme

Hello everyone
I finally got my SIP trunk  provider. They have their side configured but I can't place or recieve any calls. I keep  getting a busy signal both ways. I tried dialing 9 then a local number and  I keep getting a busy signal.
I have a cisco 2801 Voice Bundle,PVDM2-8,SP  Serv,64F/256D
flash:c2801-spservicesk9-mz.124-24.T2.bin with IP  phones on inside
Waiting on SCUE-AIM card for Unity and AA (should get it  soon I hope)

This is the information I got from my service provider to  configure my side of the SIP trunk:
DID: 1-705-269-6665 ***This is the phone  number they gave me
and IP address of the SIP server: 69.60.226.14 and username and password to go with this.

I have attached 3 files. The first one is a photo of my set, one showing my configurations with show run command and the other showing the log for debug ccsip messages. My phones are all able to place calls over PSTN but now my problem is trying to configure the phones to place and receive calls over my cable modem internet to SIP Trunk provider. I am in training and trying to learn as I go and am pretty sure that the problem is with my configurations just not sure what my problem is and how to correct it.

Thanks very much for any help

6 REPLIES
New Member

Re: sip trunk configuration problems with cme

Hello again

I'm not sure but I think that one of my problems is that I have no phones registering with SIP. Since my phones are SCCP phones with SCCP phone loads do I need to convert this to SIP phone loads? or is there a way to register my phone with SIP. From what I understand I think I need to have at least 1 phone registered with SIP correct? I'm also not sure if my incoming and outgoing voip dial-peers are well configured.


CME_router#show sip  register status
Line                              peer         expires(sec)  registered
==========================

======   ==========  ============  ==========
1001                               20001       88            no
1002                               20002       88            no
1003                              20003        88            no
1004                              20004        88            no
17052696665                20010       141           no
6665                              20005       88            no
6666                               20007       141          no
7052696665                   20006       88            no


Thanks again any  help with this

Re: sip trunk configuration problems with cme

The destination on your voip dial peer pointing to the sip provider should not be your phone number. It should be the number that you are dialing. For example, you could use 9T (this encompasses 9 + any number of digits following). See below.

dial-peer voice 6665 voip                  ****THIS IS VOIP DIAL-PEER
description **Outgoing calls to SIP Trunk**
translation-profile outgoing OUT
destination-pattern 9T      ****THIS IS THE PHONE NUMBER GIVEN BY PROVIDER
voice-class codec 100
session protocol sipv2
session target ipv4:69.60.226.14     ****THIS IS THE ADDRESS GIVEN BY PROVIDER
dtmf-relay rtp-nte
no vad

Hope this helps.

Brandon

New Member

Re: sip trunk configuration problems with cme

Hello Brandon

Thanks for the help. I tried that and still no go. No changes. I think my problem may be with the phone not registering with the SIP server.Unless the phone registers with SIP I don't think I can place or receive any calls (not sure since I,m new at this). Also when I try to call the number 7052696665 I keep getting: The number you are trying to reach is not in service, please try again. If I use the command show sip register status I have no phones registered to SIP. The phone loads I'm using are for SCCP phones so I,m wondering if this makes a difference and should I convert the SCCP phone to a SIP phone with the proper phone loads. Here are a few commands to verify the SIP trunk itself:

CME_router#sh sip service
SIP Service is up

CME_router#show sip register status
Line                              peer        expires(sec)  registered
================================  ==========  ============  ==========
1001                              20001       88            no
1002                              20002       88            no
1003                              20003       88            no
1004                              20004       88            no
17052696665                 20010       141           no
6665                              20005       88            no
6666                              20007      141           no
7052696665                   20006       88            no

CME_router#show sip status
SIP User Agent Status
SIP User Agent for UDP : ENABLED
SIP User Agent for TCP : ENABLED

SIP User Agent for TLS over TCP : ENABLED
SIP User Agent bind status(signaling): DISABLED
SIP User Agent bind status(media): DISABLED
SIP early-media for 180 responses with SDP: ENABLED
SIP max-forwards : 70
SIP DNS SRV version: 2 (rfc 2782)
NAT Settings for the SIP-UA
Role in SDP: NONE
Check media source packets: DISABLED
Maximum duration for a telephone-event in NOTIFYs: 2000 ms
SIP support for ISDN SUSPEND/RESUME: ENABLED
Redirection (3xx) message handling: ENABLED
Reason Header will override Response/Request Codes: DISABLED
Out-of-dialog Refer: DISABLED
Presence support is DISABLED
protocol mode is ipv4

SDP application configuration:
Version line (v=) required
Owner line (o=) required
Timespec line (t=) required
Media supported: audio video image
Network types supported: IN
Address types supported: IP4 IP6
Transport types supported: RTP/AVP udptl

CME_router#sh sip connections udp detail
Total active connections      : 1
No. of send failures          : 0
No. of remote closures        : 0
No. of conn. failures         : 0
No. of inactive conn. ageouts : 0

---------Printing Detailed Connection Report---------
Note:
** Tuples with no matching socket entry
    - Do 'clear sip conn t ipv4::'
      to overcome this error condition
++ Tuples with mismatched address/port entry
    - Do 'clear sip conn t ipv4:: id '
      to overcome this error condition

Remote-Agent:69.60.226.14, Connections-Count:1
  Remote-Port Conn-Id Conn-State  WriteQ-Size
  =========== ======= =========== ===========
         5060       2 Established           0

Thanks again for any help with this

New Member

Re: sip trunk configuration problems with cme

I can now receive incoming calls but cannot place any outbound calls.I called the service provider and got them to check their end and they had to remove the username and password since I have a static IP. The problem now is outbound calls. I still keep getting a busy signal when I try either local or long distance. I took a debug voip dialpeer and don't think that I match anything. The ISP is sending me 10 digits to my CME.

Here are my dialpeers:

!
dial-peer voice 6665 voip
description 7 Digit Local Dialing
preference 1
destination-pattern [2-9]......
voice-class codec 100
voice-class sip dtmf-relay force rtp-nte
session protocol sipv2
session target ipv4:69.60.226.14
session transport udp
dtmf-relay rtp-nte
no vad
!
dial-peer voice 6666 voip
description **Incoming calls from SIP Trunk**
preference 1
destination-pattern 7052696665
voice-class codec 100
voice-class sip dtmf-relay force rtp-nte
session protocol sipv2
session target ipv4:69.60.226.14:5060
dtmf-relay rtp-nte
no vad
!
dial-peer voice 6667 voip
description 10 Digit Long Distance
preference 1
destination-pattern [2-9]..[2-9]......
voice-class codec 100
voice-class sip dtmf-relay force rtp-nte
session protocol sipv2
session target ipv4:69.60.226.14
dtmf-relay rtp-nte
no vad
!

Here is the log:

CME_router#
Jun 25 16:19:58.407: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
   Calling Number=1001, Called Number=, Voice-Interface=0x675E0B70,
   Timeout=TRUE, Peer Encap Type=ENCAP_VOICE, Peer Search Type=PEER_TYPE_VOICE,
   Peer Info Type=DIALPEER_INFO_SPEECH
Jun 25 16:19:58.407: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
   Result=Success(0) after DP_MATCH_ORIGINATE; Incoming Dial-peer=20001
Jun 25 16:19:59.323: //-1/5526336C8448/DPM/dpMatchPeersCore:
   Calling Number=, Called Number=2, Peer Info Type=DIALPEER_INFO_SPEECH
Jun 25 16:19:59.323: //-1/5526336C8448/DPM/dpMatchPeersCore:
   Match Rule=DP_MATCH_DEST; Called Number=2
Jun 25 16:19:59.323: //-1/5526336C8448/DPM/dpMatchPeersCore:
   Result=Partial Matches(1) after DP_MATCH_DEST
Jun 25 16:19:59.323: //-1/5526336C8448/DPM/dpMatchPeersMoreArg:
   Result=MORE_DIGITS_NEEDED(1)
Jun 25 16:19:59.763: //-1/5526336C8448/DPM/dpMatchPeersCore:
   Calling Number=, Called Number=26, Peer Info Type=DIALPEER_INFO_SPEECH
Jun 25 16:19:59.763: //-1/5526336C8448/DPM/dpMatchPeersCore:
   Match Rule=DP_MATCH_DEST; Called Number=26
Jun 25 16:19:59.763: //-1/5526336C8448/DPM/dpMatchPeersCore:
   Result=Partial Matches(1) after DP_MATCH_DEST
Jun 25 16:19:59.763: //-1/5526336C8448/DPM/dpMatchPeersMoreArg:
   Result=MORE_DIGITS_NEEDED(1)
Jun 25 16:20:00.223: //-1/5526336C8448/DPM/dpMatchPeersCore:
   Calling Number=, Called Number=267, Peer Info Type=DIALPEER_INFO_SPEECH
Jun 25 16:20:00.223: //-1/5526336C8448/DPM/dpMatchPeersCore:
   Match Rule=DP_MATCH_DEST; Called Number=267
Jun 25 16:20:00.223: //-1/5526336C8448/DPM/dpMatchPeersCore:
   Result=Partial Matches(1) after DP_MATCH_DEST
Jun 25 16:20:00.223: //-1/5526336C8448/DPM/dpMatchPeersMoreArg:
   Result=MORE_DIGITS_NEEDED(1)
Jun 25 16:20:00.735: //-1/5526336C8448/DPM/dpMatchPeersCore:
   Calling Number=, Called Number=2676, Peer Info Type=DIALPEER_INFO_SPEECH
Jun 25 16:20:00.735: //-1/5526336C8448/DPM/dpMatchPeersCore:
   Match Rule=DP_MATCH_DEST; Called Number=2676
Jun 25 16:20:00.735: //-1/5526336C8448/DPM/dpMatchPeersCore:
   Result=Partial Matches(1) after DP_MATCH_DEST
Jun 25 16:20:00.735: //-1/5526336C8448/DPM/dpMatchPeersMoreArg:
   Result=MORE_DIGITS_NEEDED(1)
Jun 25 16:20:01.171: //-1/5526336C8448/DPM/dpMatchPeersCore:
   Calling Number=, Called Number=26760, Peer Info Type=DIALPEER_INFO_SPEECH
Jun 25 16:20:01.171: //-1/5526336C8448/DPM/dpMatchPeersCore:
   Match Rule=DP_MATCH_DEST; Called Number=26760
Jun 25 16:20:01.171: //-1/5526336C8448/DPM/dpMatchPeersCore:
   Result=Partial Matches(1) after DP_MATCH_DEST
Jun 25 16:20:01.171: //-1/5526336C8448/DPM/dpMatchPeersMoreArg:
   Result=MORE_DIGITS_NEEDED(1)
Jun 25 16:20:01.531: //-1/5526336C8448/DPM/dpMatchPeersCore:
   Calling Number=, Called Number=267609, Peer Info Type=DIALPEER_INFO_SPEECH
Jun 25 16:20:01.531: //-1/5526336C8448/DPM/dpMatchPeersCore:
   Match Rule=DP_MATCH_DEST; Called Number=267609
Jun 25 16:20:01.531: //-1/5526336C8448/DPM/dpMatchPeersCore:
   Result=Partial Matches(1) after DP_MATCH_DEST
Jun 25 16:20:01.531: //-1/5526336C8448/DPM/dpMatchPeersMoreArg:
   Result=MORE_DIGITS_NEEDED(1)
Jun 25 16:20:01.935: //-1/5526336C8448/DPM/dpMatchPeersCore:
   Calling Number=, Called Number=2676097, Peer Info Type=DIALPEER_INFO_SPEECH
Jun 25 16:20:01.935: //-1/5526336C8448/DPM/dpMatchPeersCore:
   Match Rule=DP_MATCH_DEST; Called Number=2676097
Jun 25 16:20:01.935: //-1/5526336C8448/DPM/dpMatchPeersCore:
   Result=Success(0) after DP_MATCH_DEST
Jun 25 16:20:01.935: //-1/5526336C8448/DPM/dpMatchPeersMoreArg:
   Result=SUCCESS(0)
   List of Matched Outgoing Dial-peer(s):
     1: Dial-peer Tag=6665
     2: Dial-peer Tag=100
Jun 25 16:20:01.939: //-1/5526336C8448/DPM/dpMatchPeersCore:
   Calling Number=, Called Number=2676097, Peer Info Type=DIALPEER_INFO_SPEECH
Jun 25 16:20:01.939: //-1/5526336C8448/DPM/dpMatchPeersCore:
   Match Rule=DP_MATCH_DEST; Called Number=2676097
Jun 25 16:20:01.939: //-1/5526336C8448/DPM/dpMatchPeersCore:
   Result=Success(0) after DP_MATCH_DEST
Jun 25 16:20:01.939: //-1/5526336C8448/DPM/dpMatchPeersMoreArg:
   Result=SUCCESS(0)
   List of Matched Outgoing Dial-peer(s):
     1: Dial-peer Tag=6665
     2: Dial-peer Tag=100
Jun 25 16:20:01.939: //-1/5526336C8448/DPM/dpMatchPeersCore:
   Calling Number=, Called Number=2676097, Peer Info Type=DIALPEER_INFO_SPEECH
Jun 25 16:20:01.939: //-1/5526336C8448/DPM/dpMatchPeersCore:
   Match Rule=DP_MATCH_DEST; Called Number=2676097
Jun 25 16:20:01.939: //-1/5526336C8448/DPM/dpMatchPeersCore:
   Result=Success(0) after DP_MATCH_DEST
Jun 25 16:20:01.939: //-1/5526336C8448/DPM/dpMatchPeersMoreArg:
   Result=SUCCESS(0)
   List of Matched Outgoing Dial-peer(s):
     1: Dial-peer Tag=6665
     2: Dial-peer Tag=100
Jun 25 16:20:01.939: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
   Calling Number=2676097, Called Number=2676097, Peer Info Type=DIALPEER_INFO_S
PEECH
Jun 25 16:20:01.939: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
   Match Rule=DP_MATCH_DEST; Called Number=2676097
Jun 25 16:20:01.939: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
   Result=Success(0) after DP_MATCH_DEST
Jun 25 16:20:01.939: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersMoreArg:
   Result=SUCCESS(0)
   List of Matched Outgoing Dial-peer(s):
     1: Dial-peer Tag=6665
     2: Dial-peer Tag=100
Jun 25 16:20:01.943: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
   Calling Number=, Called Number=, Voice-Interface=0x0,
   Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search Type=PEER_TYPE_VOICE,
   Peer Info Type=DIALPEER_INFO_SPEECH
Jun 25 16:20:01.943: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
   Result=NO_MATCH(-1) After All Match Rules Attempt
Jun 25 16:20:01.943: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
   Calling Number=2676097, Called Number=, Voice-Interface=0x0,
   Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search Type=PEER_TYPE_VOICE,
   Peer Info Type=DIALPEER_INFO_SPEECH
Jun 25 16:20:01.943: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
   Result=Success(0) after DP_MATCH_ORIGINATE; Incoming Dial-peer=6665
Jun 25 16:20:01.943: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
   Calling Number=, Called Number=2676097, Peer Info Type=DIALPEER_INFO_SPEECH
Jun 25 16:20:01.943: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
   Match Rule=DP_MATCH_DEST; Called Number=2676097
Jun 25 16:20:01.943: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
   Result=Success(0) after DP_MATCH_DEST
Jun 25 16:20:01.943: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersMoreArg:
   Result=SUCCESS(0)
   List of Matched Outgoing Dial-peer(s):
     1: Dial-peer Tag=6665
     2: Dial-peer Tag=100
Jun 25 16:20:01.943: //-1/5526336C8448/DPM/dpMatchPeersCore:
   Calling Number=, Called Number=2676097, Peer Info Type=DIALPEER_INFO_SPEECH
Jun 25 16:20:01.943: //-1/5526336C8448/DPM/dpMatchPeersCore:
   Match Rule=DP_MATCH_DEST; Called Number=2676097
Jun 25 16:20:01.947: //-1/5526336C8448/DPM/dpMatchPeersCore:
   Result=Success(0) after DP_MATCH_DEST
Jun 25 16:20:01.947: //-1/5526336C8448/DPM/dpMatchPeersMoreArg:
   Result=SUCCESS(0)
   List of Matched Outgoing Dial-peer(s):
     1: Dial-peer Tag=6665
     2: Dial-peer Tag=100
Jun 25 16:20:02.067: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
   Calling Number=[2-9]......, Called Number=, Voice-Interface=0x0,
   Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search Type=PEER_TYPE_VOICE,
   Peer Info Type=DIALPEER_INFO_SPEECH
Jun 25 16:20:02.067: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
   Result=NO_MATCH(-1) After All Match Rules Attempt
Jun 25 16:20:03.298: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
   Calling Number=[2-9]......, Called Number=, Voice-Interface=0x0,
   Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search Type=PEER_TYPE_VOICE,
   Peer Info Type=DIALPEER_INFO_SPEECH
Jun 25 16:20:03.298: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
   Result=NO_MATCH(-1) After All Match Rules Attempt
Jun 25 16:20:06.378: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
   Calling Number=1001$, Called Number=, Voice-Interface=0x0,
   Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search Type=PEER_TYPE_VOICE,
   Peer Info Type=DIALPEER_INFO_SPEECH
Jun 25 16:20:06.378: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
   Result=NO_MATCH(-1) After All Match Rules Attempt
CME_router#undebug all
All possible debugging has been turned off

New Member

Re: sip trunk configuration problems with cme

Finally got it working.
Problem 1: No inbound calls. Service provider issue. Missing a command.
Problem 2: No outbound calls. Service provider issue. Missing 2 commands..
At least the problem wasn't on my side. All is great now.

Thanks for the help
New Member

sip trunk configuration problems with cme

Hi Marc,

I realise that this is an old post.

However I have to configure a SIP trunk on a CME. Can you confirm whether your CME Router is configured with a Public IP address on one of it's Interfaces. Are you natting on this Router as I am aware that SIP has nat issues due to the embedded nature of the protocol.

regards

Ian.

1279
Views
0
Helpful
6
Replies
CreatePlease to create content