[Asterisk-Users] Broadvoice Problems.-
FRANCISCO PEREZ-LANDAETA
fplandae at hotmail.com
Wed Nov 10 23:35:19 MST 2004
I am a user of broadvoice. I have recently acquired another account to use
it with my asterisk box. However, there seems to be a problem with the
registration. I keep on getting the following message :
Nov 8 18:30:27 WARNING[2306]: chan_sip.c:683 retrans_pkt: Maximum retries
exceeded on call
Nov 8 18:30:41 NOTICE[2306]: chan_sip.c:4053 sip_reg_timeout: Registration
for '954XXXXXX at sip.broadvoice.com' timed out, trying again
-- parse_srv: SRV mapped to host proxy.dca.broadvoice.com, port 5060
Any ideas, how to make it work. I read there is a patch, but I am not sure
if I should install it.
Can someone send me a working configuration file just in case to
fplandae at hotmail.com
Thanks,
On 11/10/04 4:04 PM, "asterisk-users-request at lists.digium.com"
<asterisk-users-request at lists.digium.com> wrote:
> Send Asterisk-Users mailing list submissions to
> asterisk-users at lists.digium.com
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.digium.com/mailman/listinfo/asterisk-users
> or, via email, send a message with subject or body 'help' to
> asterisk-users-request at lists.digium.com
>
> You can reach the person managing the list at
> asterisk-users-owner at lists.digium.com
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Asterisk-Users digest..."
>
>
> Today's Topics:
>
> 1. Problem adding zaprtc to Asterisk CVS on debian sarge
> (Sebastian Mauer)
> 2. Broadvoice asterisk patch (brian at fcu.com)
> 3. Broadvoice Patch (TELUX)
> 4. Re: Broadvoice asterisk patch (Ryan Wilkins)
> 5. Re: Re: Is this good or bad (Rich Allen)
> 6. RE: Broadvoice asterisk patch (Tim Jackson)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 10 Nov 2004 20:51:39 +0100
> From: Sebastian Mauer <maui at areacube.de>
> Subject: [Asterisk-Users] Problem adding zaprtc to Asterisk CVS on
> debian sarge
> To: asterisk-users at lists.digium.com
> Message-ID: <4192714B.4020007 at areacube.de>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Hello there,
> I'm still new to Asterisk and until today i did not even know that
> Asterisk needs a timing source for correct use of MeetMe and MOH.
> So I looked after ztdummy (but I found out that I have USB-OHCI instead
> of UHCI) and came finally to zaprtc
>
> But there the trouble starts
>
> I fetched all zaptel, and asterisk from CVS, and put zaptrtc in the
> right directory:
>
> Making zaprtc:
> trinity:/usr/local/src/zaptelrtc# make
> cc -c zaprtc.c -D__KERNEL__ -DMODULE -DEXPORT_SYMTAB
> -fomit-frame-pointer -O2 -Wall -I/usr/src/linux/include -I../zaptel
> -Wall -DMODVERSIONS -include /usr/src/linux/include/linux/modversions.h
> In file included from /usr/src/linux/include/linux/spinlock.h:6,
> from /usr/src/linux/include/linux/module.h:12,
> from zaprtc.c:60:
> /usr/src/linux/include/asm/system.h: In Funktion ?__set_64bit_var?:
> /usr/src/linux/include/asm/system.h:192: Warnung: dereferencing
> type-punned pointer will break strict-aliasing rules
> /usr/src/linux/include/asm/system.h:192: Warnung: dereferencing
> type-punned pointer will break strict-aliasing rules
> gcc -s -Wall -Wstrict-prototypes rtctest.c -o rtctest
> rtctest.c: In Funktion ?main?:
> rtctest.c:30: Warnung: implicit declaration of function `exit'
> gcc -s -Wall -Wstrict-prototypes rtcsetup.c -o rtcsetup
> rtcsetup.c: In Funktion ?main?:
> rtcsetup.c:31: Warnung: implicit declaration of function `exit'
> rtcsetup.c:23: Warnung: unused variable `i'
> rtcsetup.c:23: Warnung: unused variable `irqcount'
> rtcsetup.c:24: Warnung: unused variable `tmp'
> rtcsetup.c:24: Warnung: unused variable `data'
> rtcsetup.c:25: Warnung: unused variable `rtc_tm'
> sync
>
> And now I try to activate it finally with make load:
> trinity:/usr/local/src/zaptelrtc# make load
> sync
> modprobe zaptel
> /lib/modules/2.4.27-1-386/misc/zaptel.o:
> /lib/modules/2.4.27-1-386/misc/zaptel.o: unresolved symbol
> create_proc_entry_R6f790657
> /lib/modules/2.4.27-1-386/misc/zaptel.o:
> /lib/modules/2.4.27-1-386/misc/zaptel.o: unresolved symbol
> remove_proc_entry_R96e689cb
> /lib/modules/2.4.27-1-386/misc/zaptel.o:
> /lib/modules/2.4.27-1-386/misc/zaptel.o: unresolved symbol
> register_chrdev_Rbe900e0b
> /lib/modules/2.4.27-1-386/misc/zaptel.o:
> /lib/modules/2.4.27-1-386/misc/zaptel.o: unresolved symbol
> proc_mkdir_R8be6b1b2
> /lib/modules/2.4.27-1-386/misc/zaptel.o:
> /lib/modules/2.4.27-1-386/misc/zaptel.o: unresolved symbol
> add_wait_queue_Rd4158ead
> /lib/modules/2.4.27-1-386/misc/zaptel.o:
> /lib/modules/2.4.27-1-386/misc/zaptel.o: unresolved symbol
> remove_wait_queue_R93e76632
> /lib/modules/2.4.27-1-386/misc/zaptel.o:
> /lib/modules/2.4.27-1-386/misc/zaptel.o: unresolved symbol
> __pollwait_R8701678a
> /lib/modules/2.4.27-1-386/misc/zaptel.o: insmod
> /lib/modules/2.4.27-1-386/misc/zaptel.o failed
> /lib/modules/2.4.27-1-386/misc/zaptel.o: insmod zaptel failed
> make: *** [load] Fehler 255
>
> I don't know what to do, but I hope someone here on this maillist can
> help me.
> By the way, YES rtc is disabled as told in the zaptrtc README, it's a
> 2.4.27 baked by myself
>
> Thanks in Advance,
> and excuse my bad English ;)
>
> Sebastian Mauer
>
>
> ------------------------------
>
> Message: 2
> Date: Wed, 10 Nov 2004 12:54:22 -0700
> From: brian at fcu.com
> Subject: [Asterisk-Users] Broadvoice asterisk patch
> To: asterisk-users at lists.digium.com
> Message-ID: <20041110195422.GA16032 at fcu.com>
> Content-Type: text/plain; charset="us-ascii"
>
> Just received this from broadvoice, anyone know if this patch will
> become part of the CVS tree?
>
>
> ------------------
> THIS PATCH MUST BE APPLIED WITHIN 5 DAYS OF RECEIVING THIS E-MAIL OR YOU
> WILL RISK THE POSSIBLE SUSPENSION OF YOUR BROADVOICE SERVICE. WE
> APOLOGIZE FOR ANY INCONVENIENCE THIS MAY CAUSE BUT REQUIRE THIS PATCH IN
> ORDER TO MAINTAIN UNINTERRUPTED OPERATION.
>
>
> Dear Asterisk-Using BroadVoice Customer,
>
> BroadVoice has been working very hard in recent months to become a
> market leader in VoIP service.? As a part of that effort, we have made a
> concerted effort to facilitate interoperability with as many different
> SIP devices as possible -- including Asterisk.? While BroadVoice does
> not directly support Asterisk and will not be able to field specific
> question on your Asterisk set-up we are doing our best to assist.
>
> Unfortunately, the SIP channel in Asterisk has a number of serious
> issues which make it very difficult for BroadVoice to accommodate
> Asterisk.? One of these issues, a bug with the Asterisk registration
> system, is causing an unacceptable load our systems.
>
> BroadVoice has hired Olle Johansson and Steve Sokol (the AstriCon team)
> to work out a solution to the issue.? Attached is a patch that, when
> applied, will reduce the undue strain on the BroadVoice systems by
> properly handling registration for Asterisk servers located behind NAT
> gateways.? We ask that you take a few minutes and patch your server
> using the following instructions.
>
> This patch applies both to the current CVS Head and the Stable 1.0
> versions of Asterisk.? If you are running an older version of Asterisk,
> please update your system to at least 1.0 prior to applying this patch
> (or you can hack the patch into place in the old chan_sip.c if you feel
> like it).
>
> Note that this patch will be incorporated into the Asterisk CVS at the
> earliest opportunity.? However, due to the serious nature of the issue
> we ask that you patch your servers immediately.
>
> -= Patch Instructions =-
>
> 1.? Copy the patch to /usr/src/asterisk/channels/ (or wherever you store
> your Asterisk source image.
>
> # cp /usr/bob/sip_patch.diff /usr/src/asterisk/channels/
>
> 2.? Apply the patch using the following command:
>
> # cd /usr/src/asterisk/channels
> # patch chan_sip.c sip_patch.diff
>
> 3.? Re-compile the SIP channel by executing 'make' in the /etc/asterisk
> directory.
>
> # cd /usr/src/asterisk
> # make
>
> 4.? Install the newly compiled SIP channel with the 'make install'
> command.
>
> # make install
>
> 5.? Restart Asterisk to enable the patch as follows:
>
> # asterisk -rx "restart when convenient"
>
> This patch will update the Asterisk channel to cache and properly handle
> registration messages.? Please review the code and, if you have any
> suggestions, send comments to the author at oej at edvina.net
>
> -= BroadVoice Configuration Notes =-
>
> Because Asterisk does not have outbound proxy support, you need to make
> a few other changes to make Asterisk work well with BroadVoice.
>
> 1.? Find the closest BroadVoice proxy using the 'ping' utility.
>
> proxy.dca.broadvoice.com??????? 147.135.0.128
> proxy.lax.broadvoice.com??????? 147.135.8.128
> proxy.mia.broadvoice.com??????? 147.135.4.128
>
>
> # ping proxy.lax.broadvoice.com
>
>
> PING proxy.lax.broadvoice.com (147.135.8.128) 56(84) bytes of data.
> 64 bytes from proxy.lax.broadvoice.com (147.135.8.128): icmp_seq=1
> ttl=47 time=41 ms
> 64 bytes from proxy.lax.broadvoice.com (147.135.8.128): icmp_seq=2
> ttl=47 time=31 ms
> 64 bytes from proxy.lax.broadvoice.com (147.135.8.128): icmp_seq=3
> ttl=47 time=58 ms
>
> # ping proxy.dca.broadvoice.com
> PING proxy.dca.broadvoice.com (147.135.0.128) 56(84) bytes of data.
> 64 bytes from proxy.dca.broadvoice.com (147.135.0.128): icmp_seq=1
> ttl=47 time=141 ms
> 64 bytes from proxy.dca.broadvoice.com (147.135.0.128): icmp_seq=2
> ttl=47 time=312 ms
> 64 bytes from proxy.dca.broadvoice.com (147.135.0.128): icmp_seq=3
> ttl=47 time=258 ms
>
> Which ever proxy is closer (has a shorter ping time) is the proxy you
> want to use.
>
> 2.? Make the proxy your default by adding it to your /etc/hosts file.
>
> cd /etc
> vi hosts
>
> If say dca is closest add a host entry that looks like:
>
> 147.135.0.128?????? sip.broadvoice.com
>
> of course replace 0.128 with the ip of the "closer" proxy
>
> 3.? Configure Asterisk to connect to BroadVoice:
>
> ?From the sip.conf file:
>
> register => 8165551212:MyPa55w07d at sip.broadvoice.com/8165551212
>
> [broadvoice]
> type=friend
> username=8165551212
> fromuser=8165551212
> secret=MyPa55w07d
> host=sip.broadvoice.com
> port=5060
> context=broadvoice
> fromdomain=sip.broadvoice.com
> canreinvite=no
> dtmfmode=inband
> insecure=very
> permit=147.135.0.128/32????? ; or of closer proxy
> qualify=yes
>
> Note that having the IP address in the host file alters the way SIP
> recognizes incoming calls from BroadVoice (before, Asterisk would not
> tie incoming BroadVoice calls to the BroadVoice peer).? For this reason
> you have to add the "insecure=very" to allow Asterisk to accept calls,
> then add the permit=147.135.X.128/32 to limit calls to only the valid
> proxy.
>
> Calls from BroadVoice will end up in the 'broadvoice' context in
> extensions.conf.? You will need to add an entry for your own phone
> number in the context and direct that to whatever device you want:
>
> [broadvoice]
> exten => 8165551212,1,Dial(SIP/100|30)
> exten => 8165551212,2,VoiceMail(u100 at default)
> exten => 8165551212,102,VoiceMail(b100 at default)
>
> Alternately you can leave the phone number off the end of the 'register'
> statement in sip.conf and Asterisk will set it to 's' automatically.? In
> that case you would want the following:
>
> exten => s,1,Dial(SIP/100|30)
> exten => s,2,VoiceMail(u100 at default)
> exten => s,102,VoiceMail(b100 at default)
>
> Send outbound PSTN calls to your BroadVoice account as follows:
>
> [outgoing-context]
> exten => _.,1,Dial(SIP/broadvoice/${EXTEN})
> exten => _.,2,Congestion()
>
>
> Thanks for helping to make Asterisk and BroadVoice work together, and
> thank you for your business.
>
>
> Sincerely,
>
> The BroadVoice Team
>
>
>
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: sip_patch.tar
> Type: application/x-tar
> Size: 20480 bytes
> Desc: sip_patch.tar
> Url :
> http://lists.digium.com/pipermail/asterisk-users/attachments/20041110/dd579ce5
> /sip_patch-0001.tar
>
> ------------------------------
>
> Message: 3
> Date: Wed, 10 Nov 2004 12:58:21 -0700
> From: TELUX <list at t1.bz>
> Subject: [Asterisk-Users] Broadvoice Patch
> To: Asterisk Users Mailing List - Non-Commercial Discussion
> <asterisk-users at lists.digium.com>
> Message-ID: <419272DD.3010900 at t1.bz>
> Content-Type: text/plain; charset=us-ascii; format=flowed
>
> Whats the deal with this Broadvoice patch?
>
>
> ------------------------------
>
> Message: 4
> Date: Wed, 10 Nov 2004 14:58:30 -0500
> From: Ryan Wilkins <ryan at deadfrog.net>
> Subject: Re: [Asterisk-Users] Broadvoice asterisk patch
> To: Asterisk Users Mailing List - Non-Commercial Discussion
> <asterisk-users at lists.digium.com>
> Message-ID: <E4E8D8E0-3352-11D9-A36C-000A95A690CA at deadfrog.net>
> Content-Type: text/plain; charset=US-ASCII; format=flowed
>
> I was just about to ask a similar question having just received the
> message.
>
> I'm more concerned about someone trying to spread a virus or something
> like that. You have to admit that the URGENT, INSTALL THIS message
> with an attachment pretty much screams virus, even if its not.
>
> I tried calling Broadvoice support but they want me to leave a message
> for them to call me later. Can anyone comment on the validity of this
> message?
>
> thanks,
> Ryan Wilkins
>
> On Nov 10, 2004, at 2:54 PM, brian at fcu.com wrote:
>
>> Just received this from broadvoice, anyone know if this patch will
>> become part of the CVS tree?
>
>
>
> ------------------------------
>
> Message: 5
> Date: Wed, 10 Nov 2004 11:02:10 -0900
> From: Rich Allen <traf at mtaonline.net>
> Subject: Re: [Asterisk-Users] Re: Is this good or bad
> To: Asterisk Users Mailing List - Non-Commercial Discussion
> <asterisk-users at lists.digium.com>
> Message-ID: <6825CD4C-3353-11D9-9579-000393C24EDA at mtaonline.net>
> Content-Type: text/plain; charset=US-ASCII; format=flowed
>
> whomever is the "carrier of last resort" (generally the ILEC) would
> find it next to impossible to "refuse" a subscriber (someone wishing to
> originate/terminate traffic)
>
> - hcir
>
> On Nov 10, 2004, at 10:26 AM, Thomas Eugene Hayden wrote:
>
>>
>> Eventually, companies like Vonage are going to get shafted because SBC
>> (or whomever) can refuse to terminate traffic from them because they
>> will only be handling IP traffic and not analog voice. The FCC won't
>> be able to do anything and neither will any state regulatory bodies
>> because both have pledged to have zero regulation in IP traffic.
>> I'm not an attorney, just a college student studying telecom, so take
>> my opinion for what it's worth...
>
>
>
> ------------------------------
>
> Message: 6
> Date: Wed, 10 Nov 2004 14:04:08 -0600
> From: "Tim Jackson" <tim at angelinacounty.net>
> Subject: RE: [Asterisk-Users] Broadvoice asterisk patch
> To: "Asterisk Users Mailing List - Non-Commercial Discussion"
> <asterisk-users at lists.digium.com>
> Message-ID: <20041110200411.8FA696FD9A at justice.angelinacounty.net>
> Content-Type: text/plain; charset="US-ASCII"
>
> I've applied the patch (after scanning over the file). No issues with *.
> BV still works, too.
>
>
> -Tim
>
> -----Original Message-----
> From: asterisk-users-bounces at lists.digium.com
> [mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of Ryan
> Wilkins
> Sent: Wednesday, November 10, 2004 1:59 PM
> To: Asterisk Users Mailing List - Non-Commercial Discussion
> Subject: Re: [Asterisk-Users] Broadvoice asterisk patch
>
> I was just about to ask a similar question having just received the
> message.
>
> I'm more concerned about someone trying to spread a virus or something
> like that. You have to admit that the URGENT, INSTALL THIS message
> with an attachment pretty much screams virus, even if its not.
>
> I tried calling Broadvoice support but they want me to leave a message
> for them to call me later. Can anyone comment on the validity of this
> message?
>
> thanks,
> Ryan Wilkins
>
> On Nov 10, 2004, at 2:54 PM, brian at fcu.com wrote:
>
>> Just received this from broadvoice, anyone know if this patch will
>> become part of the CVS tree?
>
> _______________________________________________
> Asterisk-Users mailing list
> Asterisk-Users at lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-users
> To UNSUBSCRIBE or update options visit:
> http://lists.digium.com/mailman/listinfo/asterisk-users
>
>
> ------------------------------
>
> _______________________________________________
> Asterisk-Users mailing list
> Asterisk-Users at lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-users
>
>
> End of Asterisk-Users Digest, Vol 4, Issue 130
> **********************************************
>
More information about the asterisk-users
mailing list