SearchSearch  Log in to check your private messagesLog in to check your private messages  recent posts Recent Posts
Post new topic   Reply to topic
View previous topic Printable version Log in to check your private messages View next topic
Author Message
w1zzOffline



Joined: Sep 23, 2005
Posts: 32

Status: Offline
Posted: Sep 23, 2005 - 03:27 PM Reply with quote Back to top
Hi

I'm using Asterisk@Home V2.0 beta 1, and this has AMP 1-10-009

I'm having trouble with the inbound config, but only as I can't find the translation of "edit Destination One " and as such am not getting to configure the "08444846041:PLAINTEXTPASS@67.172.238.000 " element of the configuration.

Everything else seems OK as I see "failed to authenticate as inbound-voipuser" in the logs on the call presentation.

Maybe a sticky with the AMP config steps would be a useful thing?

THanks

Alan
View user's profile Send private message
ianplainOffline
Site Admin


Joined: Jul 05, 2004
Posts: 3347
Location: Bath UK
Status: Offline
Posted: Sep 23, 2005 - 04:39 PM Reply with quote Back to top
Hi Alan

Welcome to voipuser.

Have a look here http://esupport.gradwell.net/index.php? ... &_i=29

and substitute your voipuser settings for the gradwell ones. As lookng at AMPS support site they havent got the documentation for .9 up yet, Thats if it s different

I have been meaning to Get a AAH setup done but I have had to revert the Lab system back to * for a project Im working on.

So when you get yours set up, take some screen prints and we can get it put up.

Ian
View user's profile Send private message
w1zzOffline



Joined: Sep 23, 2005
Posts: 32

Status: Offline
Posted: Sep 23, 2005 - 05:20 PM Reply with quote Back to top
As I was having one of those "it does not make sense" moments I went for a coffee. Then the penny dropped.

Having already signed up for a number I was not in the "PSTN Number Termination Control Panel" and presumed I was looking for something in *.

Just testing it now.

Alan
View user's profile Send private message
w1zzOffline



Joined: Sep 23, 2005
Posts: 32

Status: Offline
Posted: Sep 23, 2005 - 06:22 PM Reply with quote Back to top
Well I'm progressing...

I'm stuck with "Rejected connect attempt from 213.166.5.129, who was trying to reach '448444844395@'" errors which I can see others have had, but I have not spotted a fix for yet.

I have half a dozen other iax trunks running fine, so I'm a bit stummped.

Time for another break.

Alan
View user's profile Send private message
ianplainOffline
Site Admin


Joined: Jul 05, 2004
Posts: 3347
Location: Bath UK
Status: Offline
Posted: Sep 23, 2005 - 07:11 PM Reply with quote Back to top
Hi

Is this a SIP or IAX connection.

Could you post copies of the conf files concerned as well as the CLI output of a failed call, as this is AAH not the debug output just the CLI,

I assume you have a relevent section in the extensions.conf and it it setup as 44844 and not 0844

Ian
View user's profile Send private message
w1zzOffline



Joined: Sep 23, 2005
Posts: 32

Status: Offline
Posted: Sep 23, 2005 - 07:14 PM Reply with quote Back to top
Ian

Had something to eat....

It's an auth problem.....

I took out the username and password and calls route in OK...

"Accepting UNAUTHENTICATED call from 213.166.5.129:"

So I'm looking at that now.

Alan
View user's profile Send private message
ianplainOffline
Site Admin


Joined: Jul 05, 2004
Posts: 3347
Location: Bath UK
Status: Offline
Posted: Sep 23, 2005 - 07:52 PM Reply with quote Back to top
Hi Alan

Without knowing what is calling in SIP or IAX and without seeing and conf files or output, Its not realy possible to say what is happening.
IAX calls can happily come in as unauthenticated normally.

Ian.
View user's profile Send private message
w1zzOffline



Joined: Sep 23, 2005
Posts: 32

Status: Offline
Posted: Sep 23, 2005 - 08:52 PM Reply with quote Back to top
Ian

Well right now all my iax2 peers have disappeared... probably me pushing to many config updates through as I try and fix this problem.

Anyway, yes this is set-up to use iax2.

When using:

IAX2/pbx.domain.com

and incomming settings of

allow=ilbc
context=from-pstn
disallow=all
type=user

then I see call delivery.

When I add user/secret:

IAX2/<voipuser#>:password@pbx.domain.com

and

allow=ilbc
context=from-pstn
disallow=all
secret=password
type=user
username=<voipuser#>

Calls are rejected.

Alan
View user's profile Send private message
ianplainOffline
Site Admin


Joined: Jul 05, 2004
Posts: 3347
Location: Bath UK
Status: Offline
Posted: Sep 23, 2005 - 10:00 PM Reply with quote Back to top
Hi Alan

One thing that jumps out is that your codecs are reversed

Code:
allow=ilbc
context=from-pstn
disallow=all
type=user


it should start with disallow=all first then the codecs that are required after for example

Code:

disallow=all
allow=ilbc
context=from-pstn
type=user


Personally I would allow a few more codecs than just ilbc, also the username should be your sip username not your voipuser number

Ian
View user's profile Send private message
w1zzOffline



Joined: Sep 23, 2005
Posts: 32

Status: Offline
Posted: Sep 23, 2005 - 11:37 PM Reply with quote Back to top
Ian

That's true.... looks like a bug in AMP.

I commented out the username and secret fields after which it re-ordered the parameter list.

Alan
View user's profile Send private message
w1zzOffline



Joined: Sep 23, 2005
Posts: 32

Status: Offline
Posted: Sep 23, 2005 - 11:55 PM Reply with quote Back to top
Ian

While I've resolved the order issues, can I just clarify, all I'm trying to do is to get inbound delivery via iax as per:

http://www.voipuser.org/forum_topic_759.html

Of the examples I have looked they tend to use:

<voipuser_number>:<user_selected_password>@<address_of_target_server>

If this is not the case I need some enlightning as to how the config examples should be read.

Alan
View user's profile Send private message
ianplainOffline
Site Admin


Joined: Jul 05, 2004
Posts: 3347
Location: Bath UK
Status: Offline
Posted: Sep 24, 2005 - 09:30 AM Reply with quote Back to top
Hi Alan

Yes that corrects for that bit but on down you will see

Code:
[44870012345]
username=SIPUSERNAME ;This is your voipuser username
secret=PLAINTEXTPASS
type=user
context=inbound-voipuser ;or what ever you want to send it to


and in extensions.conf
Code:

exten => 44870012345,1,Goto(demo,567,1)



What do ou get when you do a iax2 show peers ?

Code:
44870012345:PLAINTEXTPASS@67.172.238.000
is for the destination set in the my numbers in your voipuser account.



I have changed one of my numbers to double check and it works fine.

Ian
View user's profile Send private message
w1zzOffline



Joined: Sep 23, 2005
Posts: 32

Status: Offline
Posted: Sep 24, 2005 - 06:11 PM Reply with quote Back to top
Quote:
What do ou get when you do a iax2 show peers ?

Well if I have type=user then nothing.

But if I have type=friend then:

IAX2 Peers

Name/Username Host Mask Port Status
inbound-voipuse (Unspecified) (S) 0.0.0.0 4569 Unmonitored

Inbound calls are deing delivered and routed as I want.

I would just rather have an authentication mechanism in there rather than allowing un-authenticated calls.

Alan
View user's profile Send private message
ianplainOffline
Site Admin


Joined: Jul 05, 2004
Posts: 3347
Location: Bath UK
Status: Offline
Posted: Sep 24, 2005 - 06:43 PM Reply with quote Back to top
Hi Alan

Not 100% sure whats going on with yours.

But I set up the one I posted here and the calls come in authenticated.

Without seeing what you have in the iax.conf I cant say where the problem is.

But if you substitue your numbers for whats here then it should and does work.

Ian
View user's profile Send private message


View previous topic Printable version Log in to check your private messages View next topic

Post new topic   Reply to topic
Forum Rules and Guidelines | About VoIP User | Privacy Policy


All logos and trademarks in this site are property of their respective owner.
Comments and posts are property of the poster, all the rest (c) 2003-2008 VoIP User Limited.

VoIP User Limited is incorporated in England and Wales under Company Number 6694577.

No part of this site may be reproduced without our prior consent.