Re: [on-asterisk] vBuzzer settings for A@H

[Bruce Nik]

Thanks you for the peer details Liviu.

I am using TrixBox which is [EMAIL PROTECTED] 2.8 (I think). I have problem with incoming calls and not outgoing. Also both in and out routes register properly with Vbuzzer. The funny thing is that if I use vbuzzer soft client and SJphone (connected to my Asterisk server) at the same time and on the same computer then incoming calls are fine too. I am guessing it might be a firewall problem???!!! But I have my Asterisk server in DMZ.

Now let's get to your details:

The register string "register => youruser:[EMAIL PROTECTED]:80/inbound_ext" gives me a funny situation. This is what I did to imply ur settings: xxxxx:[EMAIL PROTECTED]:80/4004. My out calls are just fine but when I dial my DID with PSTN the msg is that the phone number is not in service. I don't think that is exact sam msg that you hear from Bell Canada and I think it comes from Vbuzzer server (even though they sound the same).

I think instead of /inbound_ext I should put my DID number. e.g. 1416XXXXXXX.

I am also guessing that as long as I have successful registeration then it's not the port 80 problem.

This is my settings:

PEER DETAILS:

allow=all
authname=XXXXXX
canreinvite=no
context=from-pstn
dtmfmode=inband
fromdomain=vbuzzer.com
fromuser=XXXXXX
hidecallerid=no
host=vbuzzer.com
insecure=very
nat=yes
port=80
qualify=200
restrictcid=yes
secret=YYYYYY
type=friend
username=XXXXXX

USER CONTEXT: VBuzzerIN

 

USER DETAILS:

 

allow=all
canreinvite=no
context=from-pstn
dtmfmode=rfc2833
fromdomain=vbuzzer.com
fromuser=XXXXXX
host=vbuzzer.com
insecure=very
nat=yes
port=80
qualify=yes
secret=XXXXXX
type=friend
username=XXXXXX

 

XXXXXX:YYYYYY:[EMAIL PROTECTED]:80/1416ZZZZZZZ

 

*****************************

*  XXXXXX=USERNAME                 *

*  YYYYY=PASSWORD                *

*  ZZZZZ=7 DIGIT DID NUMBER    *
****************************

 

I do not have the useragent specified in my details because I am not sure which version vbuzzer uses now. I think they even changed it last night with new release.

 

Does the settings you sent me work fine with you? (both incoming and outgoing)?

 

Thanks again,

Bruce

 

---

From: "Liviu Toma" <[EMAIL PROTECTED]>
To: "Bruce Nik" <[EMAIL PROTECTED]>,<asterisk@uc.org>
Subject: Re: [on-asterisk] vBuzzer settings for [EMAIL PROTECTED]
Date: Wed, 14 Jun 2006 15:37:01 -0400
MIME-Version: 1.0
Received: from mr111.mail.sc5.yahoo.com ([216.136.128.67]) by bay0-mc4-f17.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.2444); Wed, 14 Jun 2006 12:37:20 -0700
Received: (qmail 10800 invoked from network); 14 Jun 2006 19:37:17 -0000
Received: from smtp100.rog.mail.re2.yahoo.com (206.190.36.78) by mr1.mail.vip.sc5.yahoo.com with SMTP; 14 Jun 2006 19:37:17 -0000
Received: (qmail 92320 invoked from network); 14 Jun 2006 19:37:16 -0000
Received: from unknown (HELO p4msi) ([EMAIL PROTECTED]@206.248.130.141 with login) by smtp100.rog.mail.re2.yahoo.com with SMTP; 14 Jun 2006 19:37:16 -0000

I've been fighting with the vbuzzer settings for quite a while until I discovered somewhere that there is actually a bug in Asterisk 1.2.7. I don't know what version is your [EMAIL PROTECTED] or how to apply this settings in particular to [EMAIL PROTECTED], but I think the configuration is similar. Basically the problem is that you need to register with the VBuzzer server on port 80. Tipically you would do something like this:

 

register => youruser:[EMAIL PROTECTED]:80/inbound_ext

 

and then somewhere further down in the file you would have the peer settings:

 

[vbuzzer_peer]
type=friend
user=youruser
username=youruser
fromuser=youruser
authname=youruser
secret=yourpassword
;host=vbuzzer.com
host=209.47.41.48
fromdomain=vbuzzer.com
dtmf=rfc2833
dtmfmode=rfc2833
disallow=all
allow=gsm
allow=ulaw
allow=alaw
nat=yes
insecure=very  ; needed if we want to allow incoming calls to bypass authentication
qualify=200
port=80
useragent=VBuzzer/1.1.1.2
context=incoming
canreinvite=no
hidecallerid=no
auth=md5
restrictcid=yes

That registration line doesn't work that way in 1.2.7 because of the bug. Instead, you would have to do something like this:

 

register => youruser:[EMAIL PROTECTED]/inbound_ext

 

That way, it will use the settings in the [vbuzzer_peer] where the port 80 is specified as well.

Also, I found that when you make changes in the vbuzzer registration, it helps sometimes to disable the registration for a while (couple hours) to let all the previous registrations expire, then enable it again with the new settings.

I hope that helps.

----- Original Message -----

From: Bruce Nik

To: asterisk@uc.org

Sent: Wednesday, June 14, 2006 12:34 AM

Subject: [on-asterisk] vBuzzer settings for [EMAIL PROTECTED]

Hello guys,

 

I know that there has been another thread about vbuzzer but I don't think anyone posted peer details and other info for vbuzzer trunk for [EMAIL PROTECTED]. I can't get the vbuzzer (416 DID) working with my TrixBox (formerly known as [EMAIL PROTECTED]). It does register but then channels are busy.

 

Can someone please post the info.

 

 

Thanks in advance,

Bruce

---

Movies, Music & More! Visit Sympatico / MSN Entertainment --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

---

Have fun with your friends online! Look and sound great doing it. Start with a video from Microsoft