Philip Prindeville
2007-Nov-19 03:53 UTC
[asterisk-users] Help: How to configure SIP domain on SPA942
I'm using a bunch of SPA942's, and I'm trying to provision them mostly by DHCP (and what I can't set that way, I try to provision via HTTP interface into the phone). I changed the domain in my AstLinux config from "astlinux" to redfish-solutions.com, and set that in my sip.conf file as well: context=incoming canreinvite=no realm=redfish-solutions.com domain=redfish-solutions.com,incoming-redfish tos=184 disallow=all allow=ulaw allow=gsm localnet=192.168.10.0/255.255.255.0 externip=X.X.X.X (Footnote: do I need a default context? I'd rather not having one... I'd rather specify where my calls go explicitly...) However, my phones don't seem to be registering with any (symbolic) domain... just the IP address of their DHCP or TFTP server (can't tell which, since it's the same box). <-- SIP read from 192.168.10.187:5060: REGISTER sip:192.168.10.1 SIP/2.0 Via: SIP/2.0/UDP 192.168.10.187:5060;branch=z9hG4bK-1e31e66f From: <sip:office_1 at 192.168.10.1>;tag=e798d04e1a8af3a6o0 To: <sip:office_1 at 192.168.10.1> Call-ID: c32aac02-6bd1a7fd at 192.168.10.187 CSeq: 58671 REGISTER Max-Forwards: 70 Contact: <sip:office_1 at 192.168.10.187:5060>;expires=3600 User-Agent: Linksys/SPA942-5.1.15(a) Content-Length: 0 Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER Supported: replaces pbx2*CLI> --- (12 headers 0 lines) --- Using latest REGISTER request as basis request Sending to 192.168.10.187 : 5060 (non-NAT) Transmitting (no NAT) to 192.168.10.187:5060: SIP/2.0 404 Not found (unknown domain) Via: SIP/2.0/UDP 192.168.10.187:5060;branch=z9hG4bK-1e31e66f;received=192.168.10.187 From: <sip:office_1 at 192.168.10.1>;tag=e798d04e1a8af3a6o0 To: <sip:office_1 at 192.168.10.1>;tag=as7c1c3fa2 Call-ID: c32aac02-6bd1a7fd at 192.168.10.187 CSeq: 58671 REGISTER User-Agent: Asterisk PBX Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY Content-Length: 0 The config seems to take: Our local SIP domains: Context Set by redfish-solutions.com incoming-redfish [Configured] So, what's the DHCP option (or the HTTP knob) to tweak to get the phones to think they are in the redfish-solutions.com domain? Thanks, -Philip
Eric "ManxPower" Wieling
2007-Nov-19 04:12 UTC
[asterisk-users] Help: How to configure SIP domain on SPA942
> (Footnote: do I need a default context? I'd rather not having one... I'd rather specify where > my calls go explicitly...)I just set the context in [general] to be context=INVALID and not have a context named INVALID.
At 07:53 PM 11/18/2007, you wrote:>(Footnote: do I need a default context? I'd rather not having >one... I'd rather specify where >my calls go explicitly...)I think the right answer is to create a default one and either just have it play monkees and hangup or just hangup. Anything to make sure it doesn't accidently end up in an outgoing context. Ira
Johansson Olle E
2007-Nov-19 20:28 UTC
[asterisk-users] Help: How to configure SIP domain on SPA942
19 nov 2007 kl. 04.53 skrev Philip Prindeville:> I'm using a bunch of SPA942's, and I'm trying to provision them mostly > by DHCP (and what I can't set that way, I try to provision via HTTP > interface into the phone). > > I changed the domain in my AstLinux config from "astlinux" to > redfish-solutions.com, and set > that in my sip.conf file as well: > > > context=incoming > canreinvite=no > realm=redfish-solutions.com > domain=redfish-solutions.com,incoming-redfish > tos=184 > disallow=all > allow=ulaw > allow=gsm > localnet=192.168.10.0/255.255.255.0 > externip=X.X.X.X > > > (Footnote: do I need a default context? I'd rather not having > one... I'd rather specify where > my calls go explicitly...) > > > However, my phones don't seem to be registering with any (symbolic) > domain... just the IP address > of their DHCP or TFTP server (can't tell which, since it's the same > box). > > > > <-- SIP read from 192.168.10.187:5060: > REGISTER sip:192.168.10.1 SIP/2.0It surprises me that a LInksys converts the domain to an IP address, that's broken. If you add autodomain=yes the IP address will be accepted to, or add it as a domain. The problem with these devices is that you don't know which domain they where configured for, since something is translating the domain to an IP address. With that logic, you can't separate and host multiple domains in the same SIP server. /O --- * Olle E Johansson - oej at edvina.net * Asterisk SIP Masterclass - Stockholm, Sweden, Jan 2008 * Register today at http://edvina.net
joakimsen at gmail.com
2007-Nov-20 17:51 UTC
[asterisk-users] Help: How to configure SIP domain on SPA942
Take a look at the admin guides at http://spc.pifiu.com On Nov 18, 2007 10:53 PM, Philip Prindeville <philipp_subx at redfish-solutions.com> wrote:> I'm using a bunch of SPA942's, and I'm trying to provision them mostly > by DHCP (and what I can't set that way, I try to provision via HTTP > interface into the phone). > > I changed the domain in my AstLinux config from "astlinux" to redfish-solutions.com, and set > that in my sip.conf file as well: > > > context=incoming > canreinvite=no > realm=redfish-solutions.com > domain=redfish-solutions.com,incoming-redfish > tos=184 > disallow=all > allow=ulaw > allow=gsm > localnet=192.168.10.0/255.255.255.0 > externip=X.X.X.X > > > (Footnote: do I need a default context? I'd rather not having one... I'd rather specify where > my calls go explicitly...) > > > However, my phones don't seem to be registering with any (symbolic) domain... just the IP address > of their DHCP or TFTP server (can't tell which, since it's the same box). > > > > <-- SIP read from 192.168.10.187:5060: > REGISTER sip:192.168.10.1 SIP/2.0 > Via: SIP/2.0/UDP 192.168.10.187:5060;branch=z9hG4bK-1e31e66f > From: <sip:office_1 at 192.168.10.1>;tag=e798d04e1a8af3a6o0 > To: <sip:office_1 at 192.168.10.1> > Call-ID: c32aac02-6bd1a7fd at 192.168.10.187 > CSeq: 58671 REGISTER > Max-Forwards: 70 > Contact: <sip:office_1 at 192.168.10.187:5060>;expires=3600 > User-Agent: Linksys/SPA942-5.1.15(a) > Content-Length: 0 > Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER > Supported: replaces > pbx2*CLI> > > --- (12 headers 0 lines) --- > Using latest REGISTER request as basis request > Sending to 192.168.10.187 : 5060 (non-NAT) > Transmitting (no NAT) to 192.168.10.187:5060: > SIP/2.0 404 Not found (unknown domain) > Via: SIP/2.0/UDP 192.168.10.187:5060;branch=z9hG4bK-1e31e66f;received=192.168.10.187 > From: <sip:office_1 at 192.168.10.1>;tag=e798d04e1a8af3a6o0 > To: <sip:office_1 at 192.168.10.1>;tag=as7c1c3fa2 > Call-ID: c32aac02-6bd1a7fd at 192.168.10.187 > CSeq: 58671 REGISTER > User-Agent: Asterisk PBX > Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY > Content-Length: 0 > > > The config seems to take: > > Our local SIP domains: Context Set by > redfish-solutions.com incoming-redfish [Configured] > > > So, what's the DHCP option (or the HTTP knob) to tweak to get the phones to > think they are in the redfish-solutions.com domain? > > Thanks, > > -Philip > > > > > _______________________________________________ > --Bandwidth and Colocation Provided by http://www.api-digital.com-- > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users >
Apparently Analagous Threads
- [Bug 1856] New: Wrong QoS naming and obsolete defaults
- [Bug 795] New: RELATED doesn't accommodate multicast UDP solicitation resulting in unicast reply
- [Bug 1733] New: Enhance support for QoS (ToS) by supporting DSCP/CS and adding option
- yum update broke ovirt
- SIP, internet calling, per-peer contexts, and multitenancy