Jump to content
Vodia PBX forum

atilla.gahbro

Members
  • Content Count

    28
  • Joined

  • Last visited

Community Reputation

0 Neutral

About atilla.gahbro

  • Rank
    Member
  1. thanks for the reply pbxnsip here is the ideal situation: create a value field or use an existing field to be inserted to the dnis of all outgoing calls for each trunk that requires it. so this would be a function to be activated on a per trunk basis on our service we dont create trunk ids such as co01 co02 etc and create the exact same trunk for each domain. but this is not necessary if we could just use a global trunk and just select it for each domain which is much faster and less error prone. however it would need to pull the tech prefix from a domain field for each domain and not from the domain that he global trunk was created under as for aarodynamics need specifically with flowroute, there is nothing special about it. they too just need to see a leading tech prefix in front of the dnis so if you need to call 12135551234 you send tech12135551234 (replace tech with what ever numeric value they assign you) our own internal needs are the same way it just needs to be something that can be managed from the top down is there a way yo insert the "name of the domain" using a switch argument in the dial plan or configuring a global trunk to pull it from the domain making the call? the p-asserted id will not work unless you can insert the needed tech prefix in front of the dialed number (we are behind a class4 that our billing system reads cdrs from and on our network all billing goes by trunk id using static ip addresses or common ip address with leading tech prefix please dont consider it a bounty. just call it professional services and lets get something workable. in place v4 may have something to address this but i cant tell as we dont have a test environment for v4 yet
  2. open offer to pbxnsip: we will pay you $1000 to create a DNIS tech prefix field that will auto insert the tech prefix in front of the dnis on all outbound calls to date we have over 300,000 un-billed outbound minutes for hosted pbx customers that are on the pbxnsip platform we gave up trying to make this work as something so simple took so long just to get across (i am not even sure if it is actually clear to pbxnsip what we need) this is what i do know: we cant manually enter it in each dial plan for for each trunk for each domain it sounds like aarodynamics has the same issue as we did (still do) i am not really sure how it can be expressed any simpler than just needing an outbound tech prefix just like you have an inbound tech prefix field pbxnsip uses the ani tech prefix field for inbound calls in the same way upstream providers need the tech prefix field to be populated for inbound (outbound from the perspective of pbxnsip) calls in our case instead of signaling the tech prefix to another service provider we are needing to send the tech prefix to our own class4 sansay switches so that our billing system can identify the domain/account making the call i think something even something like inserting the name of the domain (under domain settings > default values) where we could enter a numeric tech prefix instead of a name would work is there an argument switch that can be entered in to the dial plan that can insert the "name of the domain" ? does this make sense? am i explaining it clearly? i think many users would benefit from addressing this topic
  3. hey mario when i look at: http://kiwi.pbxnsip.com/index.php/Cbeyond i see that the config specifically states the did number assigned by cbeyond is what will be displayed on outbound calls the config in place as a work around is working by chance at the moment i dont think there is a known config in place to make the registered cbeyond trunk act like a conventional sip trunk where dids are passed like in a tdm pri there seems to be some kind of implied sip identity on the trunk that goes against the functionality you are seeking this is probably no different then most registered trunks as its more like a u.a. end point service then a switch on the customer side i think pbxnsip engineering needs to look at this and clarify the exact supported functionality so there is no doubt about what can be expected when using this service provider
  4. does pbxnsip have any special integration with snom phones as opposed to other ip phones? currently is a user activates call froward in the snom phone is there a way to tell the snom to activate the feature on pbxnsip so the call forward is initiated by pbxnsip as opposed to a call redirect when the call hits the ip phone during a regular incoming call? we are running in to situations where users are activating phone features that we cant see in the pbxnsip web interface so troubleshooting is very difficult when trying to figure things out
  5. i need to know if there is any way to play a chime when using the *82 listen code like we do with the *81 barge-in code ? unlike the listen mode *83 where the internal user also can not hear the supervisor the *82 code does a talk path cut through to the station being taught so the supervisor can be heard so i was thinking this could also be used as an OHVO (pbx/ksu feature for off-hook-voice-over) replacement to make announcements to the user who is on the phone. in addition to being a coaching feature. but execs wont want to be tapped in to without hearing a chine on their end first any way to make this happen? if not then maybe a feature enhancement for future releases?
  6. we only have about five per trunk per domain so about ten per domain the prefix is for ani and i am needing to add a tech prefix to the dnis (outbound digits)
  7. that would work to expose the sending domain but the upstream class4 switch does not look at that for determining the trunk id assigned to the domain when traffic is coming from multiple domains wit the same ip address it can only use a tech prefix for many itsp this is standard practice even when you are sending from a dedicated ip address. examples are, flowroute, grnvoip, etcetera using the dial plan would work but it would have to be a manual config for each entry and each trunk. thats the problem. many soft switches have a "tech prefix" field used just for this function and i was hoping there is something in pbxnsip trunk config that i was not aware of i guess i will have to make several hundred entries in the dial plan
  8. RFC 3455 wont work for associating to a trunk id in the class4 switch as it is not (on our network) a usable field for detecting the trunk id i am not sure how the ani can be used when we need the digits in the dialed digits (dnis) can you please explain? i am not sure i understand the common prefix in the ani like the area code either. thanks
  9. from my original post: i saw the prefix field under trunks but after reading up on it i see that its something entirely different here is the note on prefix from the url that i reviewed prior to the post: If that ANI is not set, the PBX checks if there is a Prefix set in the trunk. If this is the case, it puts the prefix in front of the primary account number and uses that as ANI. This is very useful in cases when a trunk deals with a range of numbers (typical outside of the NANPA area, e.g. Europe). The "extension" number is just put behind the prefix. here is what i need: domain xyz tech prefix is 478325 user dials 12134447777 pbxnsip sends 47832512134447777 like an auto insert to the outbound digits since all traffic from pbxnsip gets sent from the same ip address we need to identify the domain making the call and can not think of any other way to do it can this be done outside of the dial plan?
  10. i was referring to sending a tech prefix on outbound calls to the upstream carrier (our sbc/class4 switch) currently all calls from pbxnsip are handled by a common trunk group in our billing system and we have to bill by the ani which presents a problem whenthe ani is suppressed. i know we have p-asserted to work with but that requires the billing systems to look in different places we are trying to identify the domain making the call so we can have each domain (tenant) with its own trunk ip in our class4 switch so that the billing system just looks at the trunk id for billing and doe snot have to match the call record to a customer by ani i know we can insert leading digits in the dial plan but that is too difficult ot manage long term the global dial plan would be great but if the leading tech prefix has to be in the dial plan that too would not even be usable as each domains dial plan would be different what i mean by a tech prefix is the leading digits requires by some carriers/itsps such as vitelity, flowroute, etc on our sip trunking service off of our class4 switch we dont require a tech prefix on unique ip addresses but would simply use it in this case to identify the domain making the call does that make sense?
  11. outside of manually inserting a tech (leading digits, ex: 4387652 in front of 1npanxxyyyy) prefix in to each and every dial plan entry for each domain, is there a way to specify a tech prefix per trunk/domain ? currently when we or any other itsp routes calls to a multi domain pbxnsip server the call has to be sent to the fqdn url of the domain and not the ip address as only localhost domain resources are available when the call comes in to an ip address so on outbound traffic the pbxnsip server will send to the ip addresss of the itsp and with the ip address of the pbxnsip server and not the url of the domain so the only way we can think of identifying domains is to use a tech prefix function per domain so they can share the same public ip address for outbound traffic so in this config the billing system will bill for two trunk ids. one for origination (url based) and one for termination (static ip with tech prefix) i cant think of any other way to do this but need to know if there is a clean way to specify a tech prefix per trunk per domain i saw the prefix field under trunks but after reading up on it i see that its something entirely different any thoughts would be appreciated thanks
  12. john, we have been using pbnsip actively for about a year offering hosted services to a limited number of tenants totaling about 100 user accounts. from a stability point of view the application is rock solid. no restarts or anything funny like that. from a functionality point of view the product somewhat serves the multi-tenant role in two versions. the higher end versions offered by pbxnsip directly and the jointly developed solutions11 platform which is much more than a multi-tenant solution but rather more of an itsp in a box type of system. the solutions11 might be an overkill if you already have your voip network and billing system in place. the standard versions offered natively as pbxnsip on the other hand may lack some multi-tenant type functionality found in other systems. i recommend you try it out and see if you can make it work for what you want to do. one of the things we have been using it for lately is informal inbound conference room service where we track inbound minutes to the specific d.i.d number and bill for usage only. hope this info helps.
  13. we are running ver 2.1.9.2467 and are having a problem where users from one domain can not call another domain. our specific config is that the pbxnsip server is behind our sbc/class4 switches which are setup as gateways for the pbxnsip trunks for the domains so when a user from one tenant calls a user on another tenant the call hits the upstream class4 switch and gets routed back to the pbxnsip server for the second leg of the call the problems seems to be that if caller-id is not suppressed on the calling side we see an "auth requires" message in the sip logs on the inbound call coming in to the dialed number so the pbxnsip server sees the ani of the calling party and finds a match for it in it's system wide account database and views the call as an unregistered by that account even though the call is coming in on a trunk as an external call if the calling party suppresses caller-id then the call works we have tried using separate trunks for each domain as well as using trunks visible for all domains. same result so we need to figure out how to make pbxnsip disregard ani matches in system wide accounts for inbound trunk calls any help would be appreciated atilla
  14. how can we suppress the javascript in the web interface? which snom wizard are you referring to?
  15. one thing is that if you are transfering to an auto attendant and hear the greeting and then press transfer the call discoes anyway. i will try transfering to another station and see what happens. as for the upgrade, its just a matter of figuring out how to do that via tghe pbxnsip switch. we havent figured that one out yet.
×
×
  • Create New...