![]() |
2011-04-19
, 09:17
|
Posts: 18 |
Thanked: 5 times |
Joined on Apr 2010
|
#2
|
![]() |
2011-04-19
, 13:41
|
Posts: 93 |
Thanked: 13 times |
Joined on Nov 2010
|
#3
|
Shouldnt there be a context=default in sip.conf for the sip peer localphone.com?
![]() |
2011-04-19
, 14:00
|
Posts: 13 |
Thanked: 6 times |
Joined on Apr 2011
|
#4
|
![]() |
2011-04-19
, 15:10
|
Posts: 93 |
Thanked: 13 times |
Joined on Nov 2010
|
#5
|
Where is your localphone incoming context? See
http://help.localphone.com/voip/devi...phone/asterisk
-m
Edit: Please don't use a numeric only username (you are using 1001). It can be any alphanumeric string. You should mix numbers and letters to deter brute force attacks. Suggest you read the voip tech-chat forum on dslreports.
![]() |
2011-04-19
, 17:31
|
Posts: 13 |
Thanked: 6 times |
Joined on Apr 2011
|
#6
|
What should be my sip credential to put the sip client according to localphone code?
http://help.localphone.com/voip/devi...phone/asterisk
![]() |
2011-04-19
, 19:13
|
Posts: 93 |
Thanked: 13 times |
Joined on Nov 2010
|
#7
|
I don't understand your question. At all.
If you want to find out your SIP credentials, the link is on the localphone help page, linked above. Your original problem is that you have not defined routing of localphone incoming calls. The default context, one that you posted, does not go anywhere. Don't change the default context. It should be left as you have it, to minimize the chances of abuse. Define another context, localphone-in, you can name it anything you like really, and make sure that all the calls that reach that context get routed to your local user (1001 in your original example).
You do have a localphone incoming number (DID), don't you?
Why do you want to use asterisk in the first place? Don't setup an asterisk server if you are not fully aware of all the security considerations! You definitely don't need it to connect N900 with (most) VOIP service providers.
-m
![]() |
2011-04-20
, 02:12
|
Posts: 93 |
Thanked: 13 times |
Joined on Nov 2010
|
#8
|
![]() |
2011-04-20
, 15:51
|
Posts: 13 |
Thanked: 6 times |
Joined on Apr 2011
|
#9
|
Eureka!. I found the issue. It has something wrong with localphone. I tried with voipcheap and works nicely.
Anybody knows how to use stun (or other nat stuff) of voipcheap in asterisk sip.conf to make the connection more stable?
1. Go to the relevant sip account in accounts. 2. Advanced Settings 3. Scroll all the way down. 4. Uncheck Auto-detect STUN 5. Set your preferred STUN server (stun.ekiga.net as an example) 6. Leave the STUN port to default (3478)
![]() |
2011-04-20
, 23:19
|
Posts: 93 |
Thanked: 13 times |
Joined on Nov 2010
|
#10
|
You have to a bit more specific. What worked?
N900<=>asterisk<=>voipcheap or
N900<=>voipcheap?
You still haven't answered if you have a DID. Localphone calls it an incoming number.
You can set any stun server in N900. Here is how
Stun server setting in asterisk may or may not be available. It depends on the version that you have. AFAIK, it was introduced in asterisk 1.8.Code:1. Go to the relevant sip account in accounts. 2. Advanced Settings 3. Scroll all the way down. 4. Uncheck Auto-detect STUN 5. Set your preferred STUN server (stun.ekiga.net as an example) 6. Leave the STUN port to default (3478)
If you cannot get it to work on the N900, I am not sure why you think it will work with asterisk. At the minimum, you have to have a basic understanding of SIP protocol to troubleshoot NAT related issues with asterisk. But then again YMMV.
-m
When i get incoming, the phone doesnt ring but i see, the following msg on asterisk CLI
==Using SIP RTP CoS mark 5
Shouldnt be any port forwarding stuff as i tried everything with DMZ on my router.
sip.conf
Last edited by rosh; 2011-04-19 at 08:26.