We changed from a MM 5.2 TDM connection to a SIP connection this summer and I don't know if this issue is related or not but it seems to have started around the same time. I have 9 800 #'s of which 6 work properly. The 3 that don't work do get routed to MM but after 4 seconds of hearing the voicemail message the calls get disconnected with a fast busy. Does anyone know if this might be related and if so how I can fix these lines?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
MM drops after a few seconds
- Thread starter Softail09
- Start date
- Thread starter
- #22
is 4799 the pilot number for VM ?
Ken Means
"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)
Ken Means
"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)
- Thread starter
- #24
No it isn't. This extension doesn't actually exist in my PBX so it must be a routing thing that they did when they installed MM. 4700 is the number to reach VM but 457-4799 is defined in the VM hunt group. So a call routes to the hunt group which dials the group extension of 4700 and then it sends those digits to MM to complete the call. This changed a little bit when they change the connection to SIP so I need to look at it a little more to see exactly what it is doing.
if 4574799 is in the seconda page of your hunt group then those are the routing digits. Typically the routing digits are a variation of the hunt group extension. So in your case I would have used something like 4574700 as the routing digits.
In any case you need to see how the inbound call to 306-457-4799 is routing (or 4799 internally). It may be in your UDP or some other place to route it. But if you need 4799 to integrate to a MM mailbox the easiest way to do that is to create a virtual or x-ported station with coverage to MM.
In any case you need to see how the inbound call to 306-457-4799 is routing (or 4799 internally). It may be in your UDP or some other place to route it. But if you need 4799 to integrate to a MM mailbox the easiest way to do that is to create a virtual or x-ported station with coverage to MM.
- Thread starter
- #26
Every number needs to be defined in your PBX if you want to call to be routed anywhere.
I thought you started this thread saying these three numbers were going to MM but that MM was hanging up?
If you trace your inbound trunks does the number you dialed externally even hit your PBX?
I thought you started this thread saying these three numbers were going to MM but that MM was hanging up?
If you trace your inbound trunks does the number you dialed externally even hit your PBX?
- Thread starter
- #28
The 3rd post from the top gives more detail on the situation and how this is working/not working. The issue appears to be when these 3 800 #'s try to route to MM after coming in on my LD trunk. The other 800 #'s all route over my local PRI which is where all of my lines are supposed to point. I don't know how these are coming in on the LD trunk and both AT&T, local PRI provider, and Windstream, LD provider, have gone over the routing from their perspective and they say everything is correct. We all know they lie when they need to but at this point I can't prove to either of them that it isn't my equipment. The bad part is that this may have started happening around the time of the SIP change or it may have only started happening after Paetec became Windstream. They assure me that no changes to their network have been made yet but the 1 800 number that is a hot topic for me would have identified this problem almost immediately and they didn't say anything until the end of September. The SIP connection went in at the end of June and I got a report of a problem with one of the other numbers around mid July. The problem with the other 2 numbers is they don't get much use so it is hard to pinpoint when this problem actually began. I have had Tier 3 Avaya business partner engineers looking into this and working with Paetec but after all the testing was done everyone was still confused as to what is causing this problem. I am in the process of moving the hot 800 line back to AT&T to see if that will correct the issue. If it does then I would have to believe that something in Paetec's routing is wrong and that would seem to prove it. Do you agree?
it may prove that but it can also mean that the trunk group they are using now is not setup right in the PBX.
Has you BP tone a trace on the trunk group when the call is made and then dropped ? It must have provided some type of info?
Ken Means
"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)
Has you BP tone a trace on the trunk group when the call is made and then dropped ? It must have provided some type of info?
Ken Means
"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)
- Thread starter
- #30
yes it would
What city are you in?
Ken Means
"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)
What city are you in?
Ken Means
"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)
- Thread starter
- #32
- Status
Similar threads
- Locked
- Question