Buy or Renew
Buy or Renew
Cisco + Splunk: It’s a new day for your data. Learn more.
 
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
4460
Views
0
Helpful
13
Replies

Outgoing External Calls Failing with SPA8000

Go to solution
jamesnimmo
Level 1
Level 1

‎02-17-2010 06:51 PM - edited ‎03-21-2019 02:11 AM

I'm just setting up a Linksys SPA8000 to add some more analog ports to our UC520.

At first, no calls were working. By adding the IP of the SPA8000 to the 'Safe IP Address' list in SIP Trunks I was able to get internal calls working.

When I try to make an external call, it is just getting a busy tone.

UC520 IP: 192.168.10.1

SPA8000 IP: 192.168.10.3

Access Code to get outside line: 9

Dialling 9 7685053 works fine from a normal Cisco phone.

I followed the Cisco 'Configuring a Cisco UC500 to Operate with a Linksys SPA8000 ATA' guide to set it up.

Any suggestions would be greatly appreciated. I've been working for nearly two days on it and not making any progress. Thanks!

Call from analog port of SPA8000 to an external number

000342: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
INVITE sip:97685053@192.168.10.1 SIP/2.0
Via: SIP/2.0/UDP 192.168.10.3:5060;branch=z9hG4bK-831bf207
From: Fresh Start <sip:731@192.168.10.1>;tag=d6c0bcc5826b3d57o0
To: <sip:97685053@192.168.10.1>
Remote-Party-ID: Fresh Start <sip:731@192.168.10.1>;screen=yes;party=calling
Call-ID: 7327abdd-ac2f591f@192.168.10.3
CSeq: 101 INVITE
Max-Forwards: 70
Contact: Fresh Start <sip:731@192.168.10.3:5060>
Expires: 240
User-Agent: Linksys/SPA8000-5.1.10
Content-Length: 442
Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER
Supported: x-sipura, replaces
Content-Type: application/sdp

v=0
o=- 239833 239833 IN IP4 192.168.10.3
s=-
c=IN IP4 192.168.10.3
t=0 0
m=audio 16474 RTP/AVP 0 18 8 2 4 96 97 98 100 101
a=rtpmap:0 PCMU/8000
a=rtpmap:18 G729a/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:2 G726-32/8000
a=rtpmap:4 G723/8000
a=rtpmap:96 G726-40/8000
a=rtpmap:97 G726-24/8000
a=rtpmap:98 G726-16/8000
a=rtpmap:100 NSE/8000
a=fmtp:100 192-193
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:30
a=sendrecv

000343: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.10.3:5060;branch=z9hG4bK-831bf207
From: Fresh Start <sip:731@192.168.10.1>;tag=d6c0bcc5826b3d57o0
To: <sip:97685053@192.168.10.1>
Date: Thu, 18 Feb 2010 02:44:58 GMT
Call-ID: 7327abdd-ac2f591f@192.168.10.3
CSeq: 101 INVITE
Allow-Events: telephone-event
Server: Cisco-SIPGateway/IOS-12.x
Content-Length: 0


000344: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 486 Busy here
Via: SIP/2.0/UDP 192.168.10.3:5060;branch=z9hG4bK-831bf207
From: Fresh Start <sip:731@192.168.10.1>;tag=d6c0bcc5826b3d57o0
To: <sip:97685053@192.168.10.1>;tag=2F24FC-83A
Date: Thu, 18 Feb 2010 02:44:58 GMT
Call-ID: 7327abdd-ac2f591f@192.168.10.3
CSeq: 101 INVITE
Allow-Events: telephone-event
Server: Cisco-SIPGateway/IOS-12.x
Reason: Q.850;cause=17
Content-Length: 0


000345: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
ACK sip:97685053@192.168.10.1 SIP/2.0
Via: SIP/2.0/UDP 192.168.10.3:5060;branch=z9hG4bK-831bf207
From: Fresh Start <sip:731@192.168.10.1>;tag=d6c0bcc5826b3d57o0
To: <sip:97685053@192.168.10.1>;tag=2F24FC-83A
Call-ID: 7327abdd-ac2f591f@192.168.10.3
CSeq: 101 ACK
Max-Forwards: 70
Contact: Fresh Start <sip:731@192.168.10.3:5060>
User-Agent: Linksys/SPA8000-5.1.10
Content-Length: 0

Labels:
0 Helpful
2 Accepted Solutions

Accepted Solutions

Go to solution
John Platts
Level 4
Level 4

‎02-17-2010 08:28 PM

Be sure that you are running firmware release 6.1.3 or later on your SPA8000.

Add the following configuration to your UC520:

  • Configure voice class codec 10, which will specify the codecs allowed for calls from the UC500 to the SPA8000. Here is the configuration for voice class codec 10 (NOTE: you can rearrange the codecs, such that g711ulaw is listed in codec preference 1, g711alaw is listed in codec preference 2, and g729r8 is listed in codec preference 3):
    voice class codec 10
    codec preference 1 g729r8
    codec preference 2 g711ulaw
    codec preference 3 g711alaw
  • Configure the following in the voice register pool for the SPA8000:
    dtmf-relay rtp-nte
    voice-class codec 10
    no vad

Example voice register pool configuration:

!

! Codecs negotiated for calls to the SPA8000

!

voice class codec 10
codec preference 1 g729r8
codec preference 2 g711ulaw
codec preference 3 g711alaw

!

! voice register pool for SPA8000 gateway

!

voice register pool 1
id mac 001C.105C.54A8
number 1 dn 1
number 2 dn 2
number 3 dn 3
number 4 dn 4
number 5 dn 5
number 6 dn 6
number 7 dn 7
number 8 dn 8
dtmf-relay rtp-nte
voice-class codec 10
username 100 password ext100
no vad

I used voice class codec 10 instead of voice class codec 1 for the following reasons:

  • To avoid messing up the ITSP configuration
  • The SPA8000 does not support iLBC or G.722 codecs, even though ITSPs might support these codecs
  • Cisco Unity Express requires G.711 mu-law, and G.711 mu-law might not even be listed as a codec preference in voice class codec 1
  • For calls to the ITSP, the UC520 will either negotiate one of the codecs listed in both voice class codec 10 and the codec negotiation list for calls to the ITSP, transcode the call if transcoding is configured, or drop the call

In addition, be sure to do the following on the SPA8000 for each of  the lines configured on the SPA8000:

  • Set Fax Passthru Method to ReINVITE instead of NSE. The UC520 uses  ReINVITE messages to deal with Fax Passthrough
  • Have Dial Plan set to match that of the patterns allowed by your  UC500 unit. Example dial plan strings for typical UC500 deployments in  the US:
    • US, 7-digit dialing allowed: (*xx|[2-8]xx|911|9[2-9]11S0|9[2-9]xxxxxx|9[2-9]xx[2-9]xxxxxxS0|91[2-9]xx[2-9]xxxxxxS0|9011x.)
    • US, 10-digit dialing required: (*xx|[2-8]xx|911|9[2-9]11S0|9[2-9]xx[2-9]xxxxxxS0|91[2-9]xx[2-9]xxxxxxS0|9011x.)
  • Set Preferred Codec to either G729a, G711u, or G711a
  • Set Second Preferred Codec to either G729a, G711u, G711a, or  Unspecified
  • Set Third Preferred Codec to either G729a, G711u, G711a, or  Unspecified
  • Set Use Pref Codec Only to No
  • Be sure that G711u is set in Preferred Codec, Second Preferred Codec, or Third Preferred Codec, since Cisco Unity Express requires G.711 mu-law.

View solution in original post

0 Helpful

Go to solution
Marcos Hernandez
Level 8
Level 8
In response to jamesnimmo

‎02-25-2010 06:37 PM

OK, if you do have a SIP trunk provider we need to be more cautious about security, in order to avoid toll fraud. Did my suggestion work?

View solution in original post

0 Helpful
13 Replies 13

Go to solution
John Platts
Level 4
Level 4

‎02-17-2010 08:28 PM

Be sure that you are running firmware release 6.1.3 or later on your SPA8000.

Add the following configuration to your UC520:

  • Configure voice class codec 10, which will specify the codecs allowed for calls from the UC500 to the SPA8000. Here is the configuration for voice class codec 10 (NOTE: you can rearrange the codecs, such that g711ulaw is listed in codec preference 1, g711alaw is listed in codec preference 2, and g729r8 is listed in codec preference 3):
    voice class codec 10
    codec preference 1 g729r8
    codec preference 2 g711ulaw
    codec preference 3 g711alaw
  • Configure the following in the voice register pool for the SPA8000:
    dtmf-relay rtp-nte
    voice-class codec 10
    no vad

Example voice register pool configuration:

!

! Codecs negotiated for calls to the SPA8000

!

voice class codec 10
codec preference 1 g729r8
codec preference 2 g711ulaw
codec preference 3 g711alaw

!

! voice register pool for SPA8000 gateway

!

voice register pool 1
id mac 001C.105C.54A8
number 1 dn 1
number 2 dn 2
number 3 dn 3
number 4 dn 4
number 5 dn 5
number 6 dn 6
number 7 dn 7
number 8 dn 8
dtmf-relay rtp-nte
voice-class codec 10
username 100 password ext100
no vad

I used voice class codec 10 instead of voice class codec 1 for the following reasons:

  • To avoid messing up the ITSP configuration
  • The SPA8000 does not support iLBC or G.722 codecs, even though ITSPs might support these codecs
  • Cisco Unity Express requires G.711 mu-law, and G.711 mu-law might not even be listed as a codec preference in voice class codec 1
  • For calls to the ITSP, the UC520 will either negotiate one of the codecs listed in both voice class codec 10 and the codec negotiation list for calls to the ITSP, transcode the call if transcoding is configured, or drop the call

In addition, be sure to do the following on the SPA8000 for each of  the lines configured on the SPA8000:

  • Set Fax Passthru Method to ReINVITE instead of NSE. The UC520 uses  ReINVITE messages to deal with Fax Passthrough
  • Have Dial Plan set to match that of the patterns allowed by your  UC500 unit. Example dial plan strings for typical UC500 deployments in  the US:
    • US, 7-digit dialing allowed: (*xx|[2-8]xx|911|9[2-9]11S0|9[2-9]xxxxxx|9[2-9]xx[2-9]xxxxxxS0|91[2-9]xx[2-9]xxxxxxS0|9011x.)
    • US, 10-digit dialing required: (*xx|[2-8]xx|911|9[2-9]11S0|9[2-9]xx[2-9]xxxxxxS0|91[2-9]xx[2-9]xxxxxxS0|9011x.)
  • Set Preferred Codec to either G729a, G711u, or G711a
  • Set Second Preferred Codec to either G729a, G711u, G711a, or  Unspecified
  • Set Third Preferred Codec to either G729a, G711u, G711a, or  Unspecified
  • Set Use Pref Codec Only to No
  • Be sure that G711u is set in Preferred Codec, Second Preferred Codec, or Third Preferred Codec, since Cisco Unity Express requires G.711 mu-law.
0 Helpful

Go to solution
jamesnimmo
Level 1
Level 1
In response to John Platts

‎02-17-2010 10:59 PM

Thanks very much for the quick and detailed reply John,

Unfortunately it hasn't helped with the problem.
I wasn't running the latest firmware so was hoping that would fix it, but upgraded and still can't make calls externally.

I can receive and make calls to other extensions fine...

0 Helpful

Go to solution
John Platts
Level 4
Level 4
In response to jamesnimmo

‎02-18-2010 06:36 AM

Could you send me your UC520 configuration? You can e-mail me at jplatts@ipdimensions.com or send me a private message.

0 Helpful

Go to solution
jamesnimmo
Level 1
Level 1
In response to John Platts

‎02-18-2010 01:18 PM

Tried a few things via email thanks to John, unfortunately still getting the busy signal.

One clue I just noticed while debugging the dial plan on the UC520:

If I make the call from a Cisco phone, the number gets matched to dial peer 1058 and 59

   Result=SUCCESS(0)
   List of Matched Outgoing Dial-peer(s):
     1: Dial-peer Tag=1058
     2: Dial-peer Tag=59

However, on the SPA8000, the outgoing dial-peer is matched to peer 5 - which is the Music on Hold peer???

The called number for SPA8000 is ABCD97689999

From the Cisco phones it shows as 97689999 and works.

Any tips on why the ABCD is being added, and how I can remove it?

Thanks

James

0 Helpful

Go to solution
Marcos Hernandez
Level 8
Level 8
In response to jamesnimmo

‎02-18-2010 02:40 PM

Post your full config (remove passwords) and we'll take a look.

Thanks,

Marcos

0 Helpful

Go to solution
jamesnimmo
Level 1
Level 1
In response to Marcos Hernandez

‎02-18-2010 03:43 PM

Thanks very much Marcos,

I have attached a show run

Just out of interest I also tried setting up a Linksys PAP2 and it behaves exactly the same.

Preview file
64 KB
0 Helpful

Go to solution
Steven Smith
Level 7
Level 7
In response to jamesnimmo

‎02-19-2010 07:58 AM

I think I see the problem...

From: Fresh Start <731>;tag=d6c0bcc5826b3d57o0
To: <97685053>
Remote-Party-ID: Fresh Start <731>;screen=yes;party=calling

The from IP Address and remote party IP address are expected to be 192.168.10.3.  Since they are not, I think the voice source-group translation rule is applying to them, which is why the ABCD is getting added.

I am not a SPA8000, expert, but could you see if there are any fields that would change the From and Remote party ID to 192.168.10.3?  Alternatively, you could try adding 192.168.10.1 to ACL 2.  I am not sure this will work, but it can't hurt to try.

0 Helpful

Go to solution
jamesnimmo
Level 1
Level 1
In response to Steven Smith

‎02-22-2010 04:30 AM

Thanks Steven, you may be onto something there.. Although it does show 192.168.10.3 in the via field?

I just tried adding 192.168.10.1 to ACL2 but that doesn't seem to have helped.

Obviously this is a problem we need to get resolved ideally within about a week. Any suggestions for the best way to go about this?

Would be willing to pay someone if they were able to get it resolved, and share the answer with the community.

Cheers

James

0 Helpful

Go to solution
Marcos Hernandez
Level 8
Level 8
In response to jamesnimmo

‎02-22-2010 06:47 AM

I would start with opening a case with our TAC. They should be able to help.


Marcos

0 Helpful

Go to solution
Marcos Hernandez
Level 8
Level 8
In response to Marcos Hernandez

‎02-22-2010 07:07 AM

Before you do that. try removing the translation profile from under the voice source group. Since you do not have a real SIP trunk to a provider, this should not pose any risk.

Let us know,


Marcos

0 Helpful

Go to solution
jamesnimmo
Level 1
Level 1
In response to Marcos Hernandez

‎02-23-2010 11:09 AM

Ok thanks I'll give that a try later tonight... although we do actually have a SIP trunk to a real provider in there, currently what all our calls are going out via?

Cheers

James

0 Helpful

Go to solution
Marcos Hernandez
Level 8
Level 8
In response to jamesnimmo

‎02-25-2010 06:37 PM

OK, if you do have a SIP trunk provider we need to be more cautious about security, in order to avoid toll fraud. Did my suggestion work?

0 Helpful

Go to solution
jamesnimmo
Level 1
Level 1
In response to Marcos Hernandez

‎02-28-2010 03:12 AM

Thanks very much! Sorry only just got around to trying it out now, and yes that suggestion did work..

So in actual fact, when I added the IP of the ATA to the Access-list 2, it is causing the wrong translation profile to be applied.

I must need to add the IP of the ATA to a different access-list instead.

0 Helpful
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:

Customers Also Viewed These Support Documents