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: v=0 000343: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
|
Solved! Go to Solution.
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:
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:
In addition, be sure to do the following on the SPA8000 for each of the lines configured on the SPA8000:
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?
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:
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:
In addition, be sure to do the following on the SPA8000 for each of the lines configured on the SPA8000:
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...
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.
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
02-18-2010 02:40 PM
Post your full config (remove passwords) and we'll take a look.
Thanks,
Marcos
02-18-2010 03:43 PM
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=calling731>97685053>731>
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.
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
02-22-2010 06:47 AM
I would start with opening a case with our TAC. They should be able to help.
Marcos
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
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
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?
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.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide