Re: [asterisk-users] Coppercom and Asterisk
In the [general] section, put: register => 8159093010:[EMAIL PROTECTED] Then add a SIP peer for the outbound proxy. Something like: [essex1_outbound] fromdomain=proxy.essex1.com host=proxy.essex1.com port=5060 insecure=very username=8159093010 secret=X type=peer qualify=no canreinvite=no dtmfmode=rfc2833 disallow=all allow=ulaw The first one is needed for the registrations, and the second one is needed to answer 407 proxy challenges. Mike Hammett wrote: > My provider has a Coppercom switch. I have included the authentication > information they gave me. How would I structure this in Asterisk to the > registration and the entry in sip.conf? > > User Name - 8159093010 > Password - X > No Pin > Proxy - sip.essex1.com (10.1.3.2) > Outbound Proxy - proxy.essex1.com (63.164.210.14) > Change setting to use "outbound Proxy" > > > -- > Mike Hammett > Intelligent Computing Solutions > http://www.ics-il.com > > > > > > > ___ > -- 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 -- Alex Balashov Evariste Systems Web: http://www.evaristesys.com/ Tel: (+1) (678) 954-0670 Direct : (+1) (678) 954-0671 Mobile : (+1) (706) 338-8599 ___ -- 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
Re: [asterisk-users] Coppercom and Asterisk
I put that in, but it appears that it is trying to contact the private IP address of their SIP server. I have successfully registered to this server from over the public Internet using an Innomedia ATA. [Feb 21 11:49:18] NOTICE[4608]: chan_sip.c:7364 sip_reg_timeout:-- Registration for '[EMAIL PROTECTED]' timed out, trying again (Attempt #1) REGISTER 12 headers, 0 lines Reliably Transmitting (no NAT) to 10.1.3.2:5060: REGISTER sip:sip.essex1.com SIP/2.0 Via: SIP/2.0/UDP 10.1.5.5:5060;branch=z9hG4bK5ddcc06a;rport From: ;tag=as58a684a6 To: Call-ID: [EMAIL PROTECTED] CSeq: 103 REGISTER User-Agent: Asterisk PBX Max-Forwards: 70 Expires: 120 Contact: Event: registration Content-Length: 0 --- Really destroying SIP dialog '[EMAIL PROTECTED]' Method: REGISTER Retransmitting #1 (no NAT) to 10.1.3.2:5060: REGISTER sip:sip.essex1.com SIP/2.0 Via: SIP/2.0/UDP 10.1.5.5:5060;branch=z9hG4bK5ddcc06a;rport From: ;tag=as58a684a6 To: Call-ID: [EMAIL PROTECTED] CSeq: 103 REGISTER User-Agent: Asterisk PBX Max-Forwards: 70 Expires: 120 Contact: Event: registration Content-Length: 0 --- Retransmitting #2 (no NAT) to 10.1.3.2:5060: REGISTER sip:sip.essex1.com SIP/2.0 Via: SIP/2.0/UDP 10.1.5.5:5060;branch=z9hG4bK5ddcc06a;rport From: ;tag=as58a684a6 To: Call-ID: [EMAIL PROTECTED] CSeq: 103 REGISTER User-Agent: Asterisk PBX Max-Forwards: 70 Expires: 120 Contact: Event: registration Content-Length: 0 --- Retransmitting #3 (no NAT) to 10.1.3.2:5060: REGISTER sip:sip.essex1.com SIP/2.0 Via: SIP/2.0/UDP 10.1.5.5:5060;branch=z9hG4bK5ddcc06a;rport From: ;tag=as58a684a6 To: Call-ID: [EMAIL PROTECTED] CSeq: 103 REGISTER User-Agent: Asterisk PBX Max-Forwards: 70 Expires: 120 Contact: Event: registration Content-Length: 0 --- Really destroying SIP dialog '[EMAIL PROTECTED]' Method: REGISTER Retransmitting #4 (no NAT) to 10.1.3.2:5060: REGISTER sip:sip.essex1.com SIP/2.0 Via: SIP/2.0/UDP 10.1.5.5:5060;branch=z9hG4bK5ddcc06a;rport From: ;tag=as58a684a6 To: Call-ID: [EMAIL PROTECTED] CSeq: 103 REGISTER User-Agent: Asterisk PBX Max-Forwards: 70 Expires: 120 Contact: Event: registration Content-Length: 0 --- Aiur*CLI> -- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com - Original Message - From: "Alex Balashov" <[EMAIL PROTECTED]> To: "Asterisk Users Mailing List - Non-Commercial Discussion" Sent: Thursday, February 21, 2008 1:53 AM Subject: Re: [asterisk-users] Coppercom and Asterisk > In the [general] section, put: > > register => 8159093010:[EMAIL PROTECTED] > > Then add a SIP peer for the outbound proxy. Something like: > > [essex1_outbound] > > fromdomain=proxy.essex1.com > host=proxy.essex1.com > port=5060 > insecure=very > username=8159093010 > secret=X > type=peer > qualify=no > canreinvite=no > dtmfmode=rfc2833 > disallow=all > allow=ulaw > > The first one is needed for the registrations, and the second one is > needed to answer 407 proxy challenges. > > Mike Hammett wrote: >> My provider has a Coppercom switch. I have included the authentication >> information they gave me. How would I structure this in Asterisk to the >> registration and the entry in sip.conf? >> >> User Name - 8159093010 >> Password - X >> No Pin >> Proxy - sip.essex1.com (10.1.3.2) >> Outbound Proxy - proxy.essex1.com (63.164.210.14) >> Change setting to use "outbound Proxy" >> >> >> -- >> Mike Hammett >> Intelligent Computing Solutions >> http://www.ics-il.com >> >> >> >> >> >> >> ___ >> -- 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 > > > -- > Alex Balashov > Evariste Systems > Web: http://www.evaristesys.com/ > Tel: (+1) (678) 954-0670 > Direct : (+1) (678) 954-0671 > Mobile : (+1) (706) 338-8599 > > ___ > -- 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 > ___ -- 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
Re: [asterisk-users] Coppercom and Asterisk
*bump* -- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com - Original Message - From: Mike Hammett To: asterisk-users@lists.digium.com Sent: Wednesday, February 20, 2008 4:52 PM Subject: [asterisk-users] Coppercom and Asterisk My provider has a Coppercom switch. I have included the authentication information they gave me. How would I structure this in Asterisk to the registration and the entry in sip.conf? User Name - 8159093010 Password - X No Pin Proxy - sip.essex1.com (10.1.3.2) Outbound Proxy - proxy.essex1.com (63.164.210.14) Change setting to use "outbound Proxy" -- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com -- ___ -- 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___ -- 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
Re: [asterisk-users] Coppercom and Asterisk
> Proxy - sip.essex1.com (10.1.3.2) Isn't it a bit unusual for their proxy to be given to you as an RFC1918 address? Unless you're on their LAN of course... Regards, Chris -- C.M. Bagnall, Director, Minotaur I.T. Limited For full contact details visit http://www.minotaur.it This email is made from 100% recycled electrons ___ -- 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
Re: [asterisk-users] Coppercom and Asterisk
"Mike Hammett" <[EMAIL PROTECTED]> writes: > *bump* This is not some silly forum. *plonk* /Benny ___ -- 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
Re: [asterisk-users] Coppercom and Asterisk
It is, however, heavily trafficked and easy for someone to miss an email. -- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com - Original Message - From: "Benny Amorsen" <[EMAIL PROTECTED]> To: Sent: Monday, February 25, 2008 3:44 AM Subject: Re: [asterisk-users] Coppercom and Asterisk > "Mike Hammett" <[EMAIL PROTECTED]> writes: > >> *bump* > > This is not some silly forum. *plonk* > > > /Benny > > > > ___ > -- 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 > ___ -- 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
Re: [asterisk-users] Coppercom and Asterisk
I thought it was odd, but I've had other devices work properly with that information. -- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com - Original Message - From: "Chris Bagnall" <[EMAIL PROTECTED]> To: "'Asterisk Users Mailing List - Non-Commercial Discussion'" Sent: Sunday, February 24, 2008 8:38 PM Subject: Re: [asterisk-users] Coppercom and Asterisk >> Proxy - sip.essex1.com (10.1.3.2) > > Isn't it a bit unusual for their proxy to be given to you as an RFC1918 > address? Unless you're on their LAN of course... > > Regards, > > Chris > -- > C.M. Bagnall, Director, Minotaur I.T. Limited > For full contact details visit http://www.minotaur.it > This email is made from 100% recycled electrons > > > > ___ > -- 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 > ___ -- 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
Re: [asterisk-users] Coppercom and Asterisk
register => [EMAIL PROTECTED]:X:[EMAIL PROTECTED] [8159093010] fromdomain=proxy.essex1.com host=proxy.essex1.com port=5060 insecure=very username=8159093010 secret=X type=peer qualify=no canreinvite=no dtmfmode=rfc2833 disallow=all allow=ulaw outboundproxy=proxy.essex1.com [Feb 28 07:44:52] NOTICE[9409]: chan_sip.c:7364 sip_reg_timeout:-- Registration for '[EMAIL PROTECTED]@proxy.essex1.com' timed out, trying again (Attempt #1) REGISTER 12 headers, 0 lines Reliably Transmitting (no NAT) to 63.164.210.14:5060: REGISTER sip:proxy.essex1.com SIP/2.0 Via: SIP/2.0/UDP 10.1.5.5:5060;branch=z9hG4bK24661abe;rport From: ;tag=as16c1714c To: Call-ID: [EMAIL PROTECTED] CSeq: 103 REGISTER User-Agent: Asterisk PBX Max-Forwards: 70 Expires: 120 Contact: Event: registration Content-Length: 0 --- Aiur*CLI> <--- SIP read from 63.164.210.14:5060 ---> SIP/2.0 423 Interval Too Brief To: ;tag=ddcdjfgdeigdhifj-bibgaceacb From: ;tag=as16c1714c Via: SIP/2.0/UDP 10.1.5.5:5060;branch=z9hG4bK24661abe Call-ID: [EMAIL PROTECTED] CSeq: 103 REGISTER Expires: 120 Min-Expires: 900 Content-Length: 0 <-> --- (9 headers 0 lines) --- -- Got SIP response 423 "Interval Too Brief" back from 63.164.210.14 Really destroying SIP dialog '[EMAIL PROTECTED]' Method: REGISTER [Feb 28 07:45:12] NOTICE[9409]: chan_sip.c:7364 sip_reg_timeout:-- Registration for '[EMAIL PROTECTED]@proxy.essex1.com' timed out, trying again (Attempt #2) REGISTER 12 headers, 0 lines Reliably Transmitting (no NAT) to 63.164.210.14:5060: REGISTER sip:proxy.essex1.com SIP/2.0 Via: SIP/2.0/UDP 10.1.5.5:5060;branch=z9hG4bK7db9ed82;rport From: ;tag=as4a12e1ea To: Call-ID: [EMAIL PROTECTED] CSeq: 104 REGISTER User-Agent: Asterisk PBX Max-Forwards: 70 Expires: 120 Contact: Event: registration Content-Length: 0 --- Aiur*CLI> <--- SIP read from 63.164.210.14:5060 ---> SIP/2.0 423 Interval Too Brief To: ;tag=ejhgidfdeiidhifj-bacgaceacb From: ;tag=as4a12e1ea Via: SIP/2.0/UDP 10.1.5.5:5060;branch=z9hG4bK7db9ed82 Call-ID: [EMAIL PROTECTED] CSeq: 104 REGISTER Expires: 120 Min-Expires: 900 Content-Length: 0 <-> --- (9 headers 0 lines) --- -- Got SIP response 423 "Interval Too Brief" back from 63.164.210.14 Really destroying SIP dialog '[EMAIL PROTECTED]' Method: REGISTER -- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com - Original Message - From: Mike Hammett To: asterisk-users@lists.digium.com Sent: Wednesday, February 20, 2008 4:52 PM Subject: [asterisk-users] Coppercom and Asterisk My provider has a Coppercom switch. I have included the authentication information they gave me. How would I structure this in Asterisk to the registration and the entry in sip.conf? User Name - 8159093010 Password - X No Pin Proxy - sip.essex1.com (10.1.3.2) Outbound Proxy - proxy.essex1.com (63.164.210.14) Change setting to use "outbound Proxy" -- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com -- ___ -- 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___ -- 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
Re: [asterisk-users] Coppercom and Asterisk
*bump* -- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com - Original Message - From: "Mike Hammett" <[EMAIL PROTECTED]> To: "Asterisk Users Mailing List - Non-Commercial Discussion" Sent: Thursday, February 21, 2008 11:55 AM Subject: Re: [asterisk-users] Coppercom and Asterisk >I put that in, but it appears that it is trying to contact the private IP > address of their SIP server. I have successfully registered to this > server > from over the public Internet using an Innomedia ATA. > > [Feb 21 11:49:18] NOTICE[4608]: chan_sip.c:7364 sip_reg_timeout:-- > Registration for '[EMAIL PROTECTED]' timed out, trying again > (Attempt #1) > REGISTER 12 headers, 0 lines > Reliably Transmitting (no NAT) to 10.1.3.2:5060: > REGISTER sip:sip.essex1.com SIP/2.0 > Via: SIP/2.0/UDP 10.1.5.5:5060;branch=z9hG4bK5ddcc06a;rport > From: ;tag=as58a684a6 > To: > Call-ID: [EMAIL PROTECTED] > CSeq: 103 REGISTER > User-Agent: Asterisk PBX > Max-Forwards: 70 > Expires: 120 > Contact: > Event: registration > Content-Length: 0 > > > --- > Really destroying SIP dialog '[EMAIL PROTECTED]' > Method: REGISTER > Retransmitting #1 (no NAT) to 10.1.3.2:5060: > REGISTER sip:sip.essex1.com SIP/2.0 > Via: SIP/2.0/UDP 10.1.5.5:5060;branch=z9hG4bK5ddcc06a;rport > From: ;tag=as58a684a6 > To: > Call-ID: [EMAIL PROTECTED] > CSeq: 103 REGISTER > User-Agent: Asterisk PBX > Max-Forwards: 70 > Expires: 120 > Contact: > Event: registration > Content-Length: 0 > > > --- > Retransmitting #2 (no NAT) to 10.1.3.2:5060: > REGISTER sip:sip.essex1.com SIP/2.0 > Via: SIP/2.0/UDP 10.1.5.5:5060;branch=z9hG4bK5ddcc06a;rport > From: ;tag=as58a684a6 > To: > Call-ID: [EMAIL PROTECTED] > CSeq: 103 REGISTER > User-Agent: Asterisk PBX > Max-Forwards: 70 > Expires: 120 > Contact: > Event: registration > Content-Length: 0 > > > --- > Retransmitting #3 (no NAT) to 10.1.3.2:5060: > REGISTER sip:sip.essex1.com SIP/2.0 > Via: SIP/2.0/UDP 10.1.5.5:5060;branch=z9hG4bK5ddcc06a;rport > From: ;tag=as58a684a6 > To: > Call-ID: [EMAIL PROTECTED] > CSeq: 103 REGISTER > User-Agent: Asterisk PBX > Max-Forwards: 70 > Expires: 120 > Contact: > Event: registration > Content-Length: 0 > > > --- > Really destroying SIP dialog '[EMAIL PROTECTED]' > Method: REGISTER > Retransmitting #4 (no NAT) to 10.1.3.2:5060: > REGISTER sip:sip.essex1.com SIP/2.0 > Via: SIP/2.0/UDP 10.1.5.5:5060;branch=z9hG4bK5ddcc06a;rport > From: ;tag=as58a684a6 > To: > Call-ID: [EMAIL PROTECTED] > CSeq: 103 REGISTER > User-Agent: Asterisk PBX > Max-Forwards: 70 > Expires: 120 > Contact: > Event: registration > Content-Length: 0 > > > --- > Aiur*CLI> > > > > -- > Mike Hammett > Intelligent Computing Solutions > http://www.ics-il.com > > > - Original Message - > From: "Alex Balashov" <[EMAIL PROTECTED]> > To: "Asterisk Users Mailing List - Non-Commercial Discussion" > > Sent: Thursday, February 21, 2008 1:53 AM > Subject: Re: [asterisk-users] Coppercom and Asterisk > > >> In the [general] section, put: >> >> register => 8159093010:[EMAIL PROTECTED] >> >> Then add a SIP peer for the outbound proxy. Something like: >> >> [essex1_outbound] >> >> fromdomain=proxy.essex1.com >> host=proxy.essex1.com >> port=5060 >> insecure=very >> username=8159093010 >> secret=X >> type=peer >> qualify=no >> canreinvite=no >> dtmfmode=rfc2833 >> disallow=all >> allow=ulaw >> >> The first one is needed for the registrations, and the second one is >> needed to answer 407 proxy challenges. >> >> Mike Hammett wrote: >>> My provider has a Coppercom switch. I have included the authentication >>> information they gave me. How would I structure this in Asterisk to the >>> registration and the entry in sip.conf? >>> >>> User Name - 8159093010 >>> Password - X >>> No Pin >>> Proxy - sip.essex1.com (10.1.3.2) >>> Outbound Proxy - proxy.essex1.com (63.164.210.14) >>> Change setting to use "outbound Proxy" >>> >>> >>> -- >>> Mike Hammett >>> Intelligent Computing Solutions >>> http://www.ics-il.com >>> >>> >>> >>> >>> >>> >>> ___ >>> -- Bandwidth and Colocation Prov
Re: [asterisk-users] Coppercom and Asterisk
On Tuesday 04 March 2008 09:45:38 Mike Hammett wrote: > *bump* If people don't know, they don't know. There is no need to repost your query 10 days later. Not that many more people have signed up, and those who have signed up are unlikely to be able to answer your question. The only thing that this does is serve to annoy the rest of the people on the list. Please do not do it again. -- Tilghman ___ -- 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
Re: [asterisk-users] Coppercom and Asterisk
I was doing it because of the volume on the server. It is very easy to miss a message or 10 or 100 on a list of this traffic. -- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com - Original Message - From: "Tilghman Lesher" <[EMAIL PROTECTED]> To: "Asterisk Users Mailing List - Non-Commercial Discussion" Sent: Tuesday, March 04, 2008 10:30 AM Subject: Re: [asterisk-users] Coppercom and Asterisk > On Tuesday 04 March 2008 09:45:38 Mike Hammett wrote: >> *bump* > > If people don't know, they don't know. There is no need to repost your > query > 10 days later. Not that many more people have signed up, and those who > have > signed up are unlikely to be able to answer your question. > > The only thing that this does is serve to annoy the rest of the people on > the > list. Please do not do it again. > > -- > Tilghman > > ___ > -- 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 > ___ -- 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
Re: [asterisk-users] Coppercom and Asterisk
Mike, I might be able to help you. Contact me offline. s-h-a-n-e-b-AT-m-e- t-r-o-s-t-a-t-.-.n-e-t Shane On Mar 4, 2008, at 1:12 PM, Mike Hammett wrote: > I was doing it because of the volume on the server. It is very easy > to miss > a message or 10 or 100 on a list of this traffic. > > > -- > Mike Hammett > Intelligent Computing Solutions > http://www.ics-il.com > > > - Original Message - > From: "Tilghman Lesher" <[EMAIL PROTECTED]> > To: "Asterisk Users Mailing List - Non-Commercial Discussion" > > Sent: Tuesday, March 04, 2008 10:30 AM > Subject: Re: [asterisk-users] Coppercom and Asterisk > > >> On Tuesday 04 March 2008 09:45:38 Mike Hammett wrote: >>> *bump* >> >> If people don't know, they don't know. There is no need to repost >> your >> query >> 10 days later. Not that many more people have signed up, and those >> who >> have >> signed up are unlikely to be able to answer your question. >> >> The only thing that this does is serve to annoy the rest of the >> people on >> the >> list. Please do not do it again. >> >> -- >> Tilghman >> >> ___ >> -- 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 >> > > > ___ > -- 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 ___ -- 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
