Thread: RE: Per-trunk codec setting |
|
Is it possible to set per-trunk codec setting for each trunk?
Something like:
disallow=all
allow=g729,ulaw,alaw
I would like to force some trunks to be g711 only while some to g729.
Thanks a lot!
|
|
Thread: RE: Presence and Location of Mobile Extensions |
|
Pascal,
Does that mean there's an API somewhere that takes in this information? I'm using Windows Mobile and Blackberry phones, and have software that does similar things as Aspicore does.
Thanks.
|
|
Thread: RE: Change CID |
ayk
Replies: |
43 |
Views: |
1771848 |
|
|
doronin, bobmats:
The method doesn't seem to work with Vitelity. I have a trunk registered to the server, then another trunk with the same credentials but in password:username format. Any time I use this outgoing trunk I get a circuit-busy from the log.
Vitelity does allow me to set CallerID, but it's on their portal and is a static number.
I tried troubleshooting this with Vitelity, but after a couple tries I got this in response:
Zitat: |
You are not setting it properly. At this time we can only suggest that you check with your PBX vendor and/or administrator for further assistance. We do not provide this type of technical assistance. |
|

|
|
Thread: RE: Change CID |
ayk
Replies: |
43 |
Views: |
1771848 |
|
|
Just a follow-up. I've since been able to forward CID information to my provider Les.net using the 1${DOLLAR}{CALLERNUMID} in outgoing CID setting. However, my other provider Vitelity is still not able to recognize that.
Unfortunately, bobmats' workaround doesn't seem to work for me as these providers either do not allow non-registered trunks to make outgoing calls or do not allow the format of password:username in the password field. If anyone else using these providers know otherwise, please kindly let me know.
|
|
Thread: RE: Disconnect current call while staying in callthru |
|
Hi,
Is it possible to disconnect a current call while staying in call-thru mode? For example, I dial into call-thru and make a call, and then use some * or # commands to disconnect the call, then continue to make a second call from call-thru?
Right now, I have to disconnect the entire call and dial into the pbx again.
Thanks a lot.
|
|
Thread: RE: Vitelity Inbound routing |
|
When I try to put "inbound1.vitelity.net" into the trunk field on the "Inbound Routing" page, this is the error given to me:
DB Error: already existsINSERT INTO extensions (context, extension, priority, application, args, descr, flags) VALUES ('ext-did', 'inbound1.vitelity.net', '1', 'SetVar', 'FROM_DID=inbound1.vitelity.net', '' , '0')
I don't have another route with the same trunk name under my account.
Thanks.
|
|
Thread: RE: Vitelity Inbound routing |
|
Instead of opening yet another thread, I decided to add another post to this.
I am now having the exact same problem with another provider iBuzz123. I've been using them for a long time and no problem with them using the username as the inbound route filter, but they recently modified one of my usernames and now that particular inbound route is not working anymore. As in the case for vitelity, I've tried using the new username, old username, trunk name, trunk ip, even part of the new username to match the old username's length. There is no setting for prefix sent.
Is there an easy way to debug this for us users? i.e. for us to see what prefix was actually sent.
|
|
Thread: RE: Vitelity Inbound routing |
|
Their per-minute Candian DID is actually quite low priced, especially for low-volume usage.
Unfortunately there's no prefix settings at all for the DID or account.
|
|
Thread: RE: Vitelity Inbound routing |
|
I have a very similar problem with Les.net (http://www1.pbxes.com/forum/thread.php?threadid=1255) that resolved successfully, but now I am having trouble routing incoming calls from Vitelity.net.
I've tried my Vitelity trunk name, sip server IP and sip username. I can't try the sip server hostname because it's actually too long for the field in the inbound routing screen (inbound1.vitelity.net). No matter what I use the calls all end up coming thru as specified in "incoming calls".
Thanks a lot!
|
|
Thread: RE: Partial CID match for inbound routing |
|
Just wondering if it's possible to do a partial CID match when using inbound routing? For example, I would like to have calls to a trunk from an area code to route to one menu while calls from another area code to another menu. Is this possible, or would it be too ambiguous for the system?
Thanks!
|
|
Thread: RE: Les.net routing |
|
Thanks a lot Diafora! Works as you described! I was scratching my head for the longest time before posting it up.
Yes, I've used and tested their pay-per-use service for a while before diving in for the DID, and their service is quite good. Les is also very responsive on feedback. Now I can put the DID to good use!
|
|
Thread: RE: Les.net routing |
|
Hi,
Just wondering if anyone had any problems with routing calls from Les.net. I have a DID from them that points to a peer that is registered from pbxes.org. However, all calls from them go to the default "incoming calls" routing.
I've added incoming routing by using the trunk name that I've set (Les.net), the server hostname/address (did.voip.les.net or 64.34.176.212), or my Les.net username that I used in the trunk setting in pbxes. In the call log incoming calls show up with the server name as trunk, and context is "ext-group". Destination is whatever I set in incoming calls.
Please advise. Thanks a lot.
|
|
|