Jump to content

andrewgroup

Members
  • Content Count

    615
  • Joined

  • Last visited

Community Reputation

0 Neutral

About andrewgroup

  • Rank
    Advanced Member
  • Birthday 02/09/1957

Profile Information

  • Gender
    Male
  • Location
    Indiana
  • Interests
    IT Infrastucture Support with added VoIP services

Recent Profile Visitors

20,038 profile views
  1. The PBX snmp values are the same across the board. Linux has an snmp module, and if you want them on the same port "161" you may need to add a virual NIC net-snmp I believe is the linux module... a common command would read the linux values from the net-snmp linux module... snmpwalk -v 2c -c private 127.0.0.1 .1.3.6.1.2.1.2.2.1.2 Please Note - The Snom SNMP stack in both the PBX and any Snom Phone will not respond or support the SNMP WALK... you can only get values with a properly formed SNMP GET command....
  2. Sent a PM with my contact information, send me a note with details..
  3. We definitely had issues of crosstalk within active calls, and aligning the ports fixed the issues, or it was EXTREMELY coincidental. So we've posted various ITSP Port recommendations in the past. Coredial out of Philidelphia recommends RTP Ports: Port Range Start: 10000 Port Range End: 30000, We've had no issues with them... Window Stream - Nuvox when using their SONOS servers gave us these recommendations long ago. I assume they can use multiple UDP ranges for Media RTP Media - udp range 16384 32767 udp range 49152 53247 Signal Protocol - udp 5060 tcp 5060 udp range 17
  4. Thanks for the Snappy reply, but in the past, we've have situations where callers appeared to be cross connected, and the issues were resolved by matching the PORT range with the port range information provided by the carrier. IE Windstream / Nuvox Communications on their SONOS sip servers recommend the following ports. These SIP trunks are not behind NAT devices and making these adjustments fixed the issues at the time. RTP Media - udp range 16384 32767 udp range 49152 53247 We now make sure and ask the tech support groups at any carriers and see if they make recommendation
  5. When you have two trunks configured from two seperate providers and dial plans allowing the use of either trunk. How do we deal with the issue of each ITSP requesting the RTP ranges to be in two different Port Ranges. Example 35000 - 40000 for ITSP provider #1 and 49152-53247 for ITSP provider # Do we simply put 35000-53247 and let the SDP packets negotiate the final set of ports that will be used? Do we select the "FOLLOW RTP" option on the ports settings page? We recently added another SIP provider, and we are experiencing dropped calls... We think this may b
  6. On advise, I am making a second post about call accounting software options. We have a call center prospect and they have an interesting request. (outbound calling only) they would like a shift report that shows the IDLE time that this extension was making no calls, regardless of being on hold, talking or otherwise. they are a 30+ year old firm with ZERO technology, and a the owners believe this is the single most important report... From that report they can drill down to more information if needed. they operate on shifts so a reporting that shows EXTENSION IDLE or NO CALL TI
  7. We've recently completed a reasonable advanced and agressive setup to help a client.. We have a 10MB Fiber Trunk from Windstream Communications and the VoIP trunk originates on the PAETEC Broadsoft platform. On the trunk they provide 5 static non routable IP addresses of our choosing, 10.x.x.x, 172.x.x.x or 192.168.x.x These five IP addresses are the interface to our PBX... We have a PBX on 2 IP addresses and they have provisioned their SIP trunk to do out of band sip inquiries to the trunk. In the event the primary PBX fails to respond "200" the next inbound call we be delivere
  8. actually I believe the testing of the SIP trunk is more advanced than that. We simply outpulse the appropriate AREA CODE ANI where we have the carrier provisioned numbers, and they deliver the call through the PSTN carriers to the local numbers. All of this occures on a single SIP trunk. We simply need to make sure we only present the correct numbers in the ANI stream. So we thought we would make extensions with the correct ANI's and register multiple phones against that number... Assume my explanations of the SIP trunk will work as described, we are wondering if their is a dynam
  9. We have an "Old School" manual outbound call center that focuses all of it's dialing into less than 2 dozen area codeds among a dozen calling agents. Groups of 2,3 or 4 agents dial into these areas during a campaign. Here is the plan to help improve there success. We have a national provider than can provision our SIP trunk to deliver these area codes on our SIP trunk and will outpulse and originate the outbound call to the area codes so the recepient sees a friendly area code. We hope to eliminate the need to dial the area code in one of several ways. 1. Agent Groups are for inbund
  10. Yes, these problems arose last November after windstream - Nuvox did a software upgrade on one of their Sonus Softswitches. We quickly identified the issue after pressing them to tell us the differences between the .173 Switch and another that was on another client with no problems. We learned they had done a software upgrade, and a SIP trace they identified the problem that we were sending the call quality stuff to them that was causing the Sonus to reject the calls... We've had no problems since and make these our default settings..
  11. FYI. We have numerous clients using windstream (Formerly Nuvox) SIP trunks provided off of a T1 using a Cisco 2431 IAD. Windstream provides a Client Internet IP address on Wic1 and a seperate single IP in WIC2 for the SIP trunk... A problem began within the past day where calls to or from some cell phones would drop in 15 to 30 seconds. The problems was traced to a setting in the SIP trunk settings in the Sonus Server related to what they call a service Profile. The preferred service profile they call "Nuvox Sip-SipT-Noss" and this accommodates more codecs and keep alive set
  12. Seems the previous install has installed a newer version of C++ libraries
  13. Any further development? Seems this fails instantly on w764/pro with this error Problem Event Name: CLR20r3 Problem Signature 01: attendantconsole.exe Problem Signature 02: 1.0.0.0 Problem Signature 03: 4f91e78c Problem Signature 04: AttendantConsole Problem Signature 05: 1.0.0.0 Problem Signature 06: 4f91e78c Problem Signature 07: c Problem Signature 08: a Problem Signature 09: System.Windows.Markup.XamlParse OS Version: 6.1.7601.2.1.0.256.48 Locale ID: 1033 Additional Information 1: 0a9e Additional Infor
  14. We've taken the following approach. Burn an invisible autoattendent and create the following service flag 601 Normal Closed (Sheduled close hours) NOT OPEN 602 Holiday Closed Hours 603 Manual Closed (gone home for weather of early close) Then place the service flags in the AA service flag field in least used order 603 602 601 Then brach to to the appropriate AA,HG,AG, or EXT.... in the matching order... Make the timeout settings so if none of these are set, then send the call to a CLOSED AA.... Burning this AA allows you to create other Manual or scheduled
  15. Thanks all, this may not be the perfect solution, but added the public IP alias to the Soho, removed the 192.xxxx LAN gateway, IP replacements were added, along with routes and appears to be OK. Seems to require the remote phone ports forwarded to the PBX. We will take another look to further simplify the install, but this seems reasonable in light of the goal... Once we regain some space on our upload portal, we'll provide better docs....
×
×
  • Create New...