Skip to main content

ATA Port setup

Posted by moshe on Mon, 02/08/2010

Hi

I'm trying to setup 4 analog lines using 2 linksys ata devices, I'm wondering if anyone have done it already and what would be the best way to set the ports, by default it is set one. For 5060 and the other one 5061, so one could assume that the second ata would run on ports 5062 and 5063, but when I do that there is no audio on incoming calls (outgoing works fine). So I let it at the default ports than the registrations got all mixed up

I know the real answer is to use a sip proxy, but for now the customer is trying to save money,thats the reason he is using ata's in the first place. However is there a easy fix for that

Thanks in advance


Submitted by moshe on Mon, 02/08/2010 Permalink

ok i have installed a linksys wrt54gl with siproxd and all registrations are unning nicely in siproxd_registration file however when a call is made from extension 301 im getting a fast busy with the following error
WARNING[7554] chan_sip.c: username mismatch, have <304-tenantID>, digest has <301-tenantID>
NOTICE[7554] chan_sip.c: Failed to authenticate user Anonymous ;tag=b22db7fcff9ca6eo0

i don't see any thing wrong in the ata setting (at least noting different between extensions)

could any one shed some light

thanks in advance

Submitted by mattdarnell on Mon, 02/08/2010 Permalink

You should be able to use the stock firmware on the wrt54gl and have multiple spa2102 units behind it.

Change the registration time to 120 seconds and enable NAT in thirdlane.

-Matt

Submitted by moshe on Mon, 02/08/2010 Permalink

that ship had sailed i already installed openwrt with siproxd and it is working fine aside of the error which while looking around this seems to be a asterisk bug and not related to the ata or else

in runing on asterisk 1.4.29 did any one have experience with this bug

Submitted by moshe on Tue, 02/09/2010 Permalink

i have a setup of 2 spa2102 total of 4 lines and 2 Polycom 450s setup behind a linksys wrt54gl running openwrt with siproxd, and incoming calls work fine just outgoing calls from 1-3 out of the spa2102 are giving me the above error line 4 and the 2 Polycom phones are working good

it doesn't look like the bug, since with bug no phone on the network is working either incoming or outgoing, and there is a work around to set type=friend which is set by default in tl

any advice

thanks

Submitted by eeman on Tue, 02/09/2010 Permalink

you should not alter the ports on the other ata.
did you make sure the ata's are using and registering to the siproxd application?

Submitted by moshe on Tue, 02/09/2010 Permalink

all are registered in the siproxd however the ATAs are registering with their ports (default ports line1 5060 line 2 5061) next to the local IP unlike the Polycom registrations wihch have no port next to it

siproxd_registration looks like this where extension 301-304 are the ATAs and 201-202 are the polycom

sip
303-TenantID
192.168.1.105
5060
sip
303-TenantID
173.xx.xx.31

sip
303-TenantID
MTE.server.com

***:1:946789978
sip
304-TenantID
192.168.1.105
5061
sip
304-TenantID
173.xx.xx.31

sip
304-TenantID
MTE.server.com

***:1:946791191
sip
301-TenantID
192.168.1.146
5060
sip
301-TenantID
173.xx.xx.31

sip
301-TenantID
MTE.server.com

***:1:946791191
sip
302-TenantID
192.168.1.146
5061
sip
302-TenantID
173.xx.xx.31

sip
302-TenantID
MTE.server.com

***:1:946787845
sip
202-TenantID
192.168.1.243

sip
202-TenantID
173.xx.xx.31

sip
202-TenantID
MTE.server.com

***:1:946787900
sip
201-TenantID
192.168.1.223

sip
201-TenantID
173.xx.xx.31

sip
201-TenantID
MTE.server.com

***:0:0

Submitted by eeman on Tue, 02/09/2010 Permalink

the reason line 2 is 5061 is because its the same ip, so line 1 is 5060 and line 2 is 5061. you dont have to do 5063 and 5064 on the other ATA because its a different ip registering with the sip proxy.

just keep them at 5060 and 5061 as their defaults.

also make sure you have set the userid and authuserid to the same user, and checked 'use auth id'

Submitted by moshe on Tue, 02/09/2010 Permalink

just changed userid and authuserid to the same user, and checked 'use auth id' and still the same outcome incomming works outgoing only line 304 which is l2 of ata 2 is working

Submitted by eeman on Tue, 02/09/2010 Permalink

you've got a setting wrong somewhere. obviously 301 has somethign about it that matches 304. Either you are not setting up the sip settings correctly, or you dont have the ata set up correctly.

Submitted by moshe on Thu, 02/11/2010 Permalink

i have reset the ATAs to default and reentered all the info with the same result, no out going calls could be made from any line but line 4 cli is giving the following error

any ideas


[Feb 11 11:07:05] WARNING[7554] chan_sip.c: username mismatch, have <304-TenantID>, digest has <301-TenantID>
[Feb 11 11:07:05] NOTICE[7554] chan_sip.c: Failed to authenticate user Anonymous ;tag=e150c58c3123120do0
[Feb 11 11:07:46] WARNING[7554] chan_sip.c: username mismatch, have <304-TenantID>, digest has <302-TenantID>
[Feb 11 11:07:46] NOTICE[7554] chan_sip.c: Failed to authenticate user Anonymous ;tag=c0d36a469f8d3491o1
[Feb 11 11:08:15] WARNING[7554] chan_sip.c: username mismatch, have <304-TenantID>, digest has <303-TenantID>
[Feb 11 11:08:15] NOTICE[7554] chan_sip.c: Failed to authenticate user Anonymous ;tag=8950fbbdf086f5do0

Submitted by moshe on Thu, 02/11/2010 Permalink

the default version not sure the exact number but it is in the 3.3.? range,

i found on a blog that someone had a similar issue but with incoming only and the upgrade helped i figured i will give it a shot and it worked

thanks for the help

Submitted by moshe on Sat, 02/20/2010 Permalink

I cannot figure out the issue,however it is very interesting when I reset the ata to factory default and re enter all the account info it works fine I can't reproduce the issue

Submitted by moshe on Mon, 02/22/2010 Permalink

It just happened again after a power outage when the power came back on (not sure if it is related just stating the fact) incoming are working on all the lines, outgoing the polycoms ware working fine line 4 (which is line 2 of ata 2) was working the 3 other lines on the ata's outgoing aren't going trough comming back mismatch, I did the quick fix pressed #### 73738# and re entered the extension info in the ata's and it is back up, (nerve racking especially when you need to do it manually auto provisioning isn't working for spa2102)

What could be the cause, or best work around to avoid this issue,

Thanks

Submitted by moshe on Tue, 03/02/2010 Permalink

It seems like this something not going away

It works for a few days some times weeks and out of the blue it gets mismatched

What could be the issue