Quote:
Originally Posted by kurun
VBuzzer settings in Voxalot in Advanced mode :
Description : Vbuzzer (or whatever you chose)
From User : userid (alphabetical userid not associated numeric id)
From Domain : vbuzzer.com
UserName : userid (alphabetical userid)
Codecs : g729;ilbc;gsm;ulaw;alaw (Voxalot default, have not tried any other order)
Sip Proxy : vbuzzer.com
Sip Port : 80
Active : Yes
Sip Register : Yes
For a long time, I was not using the account (Set active to No), but recently I tried it again after VBuzzer introduced the numeric ID associated with the alphabetical ID. Actually, it has been working quite well, with a good audio connection, and passing CID correctly, everytime I received calls on it.
I have not yet tried a VBuzzer DID.
|
This type of setting does NOT work with vbuzzer DID.
I do find following very interesting thing with vbuzzer DID.
You will get message like "this number is not assigned or not in service" if you set up your vbuzzer at voxalot like this, you will receive the call from sipbroker access number via *452<userid>.
However it will work if you register your vbuzzer via another linksys PAP2 at the same time you register your vbuzzer at voxalot. It looks like vbuzzer does not recognize voxalot registration for its DID number but for its own userid.
Martin or Ron, could you please check why this happen? BTW, vbuzzer does use SIP port 80 and looks like require the client use port 80 too for its DID. If you register your vbuzzer by using non 80 port at PAP2 setting, your vbuzzer DID will not work but vbuzzer userid or internal number will work via sipbroker call.