I have a non AVAYA VM system integrated with ASM. Our CM's are where the dialplan resides and the voicemail pilot number routes up from CM to ASM via SIP trunks and then on to the VM system. The VM system has callout capabilities and mobile app functions. The callback from the mobile app to 4 digit extensions is not working and I'm wondering if ASM doesn't know what to do with the calls as they come from VM. How would I treat that within ASM to get those to direct to the CM entity link?
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 Rhinorhino on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
VM --> ASM --> CM
- Thread starter wpetilli
- Start date
It totally should be able to call the 4 digit extensions. When you set up AAM or MM off ASM, you need to make a dial pattern for your voicemail pilot to tell ASM that those calls should route to voicemail, and you must also make dial patterns matching your extension ranges in CM such that when AAM/MM/3rd party voicemail sends an MWI SIP message that this message is routed to CM to tell it to light the lamp for the station.
So, on the surface, I'd think your voicemail would be leveraging the same ASM programming to say "call 1234" as it would to "turn on mwi for 1234".
That being said, in SM's routing, you setup domains, dial patterns, routing policies and locations. Check into "locations" - you can assign a location to an entity as well as to IP address ranges.
That routing setup works something like:
If you dial 911 from "location" 5, route the call to the routing policy for the little audiocodes gateway with a single analog trunk at location 5. If you did the same from location 6, do the same but to the gateway in location 6.
If you dial the voicemail pilot from any location (except CM), then, send the call to the CM routing policy so it goes through CM's voicemail hunt group. If you dial the voicemail pilot from the CM location, then actually route the call to your voicemail. With a setup like you can always look at things from a design perspective as having the voicemail "behind" the PBX.
So, on the surface, I'd think your voicemail would be leveraging the same ASM programming to say "call 1234" as it would to "turn on mwi for 1234".
That being said, in SM's routing, you setup domains, dial patterns, routing policies and locations. Check into "locations" - you can assign a location to an entity as well as to IP address ranges.
That routing setup works something like:
If you dial 911 from "location" 5, route the call to the routing policy for the little audiocodes gateway with a single analog trunk at location 5. If you did the same from location 6, do the same but to the gateway in location 6.
If you dial the voicemail pilot from any location (except CM), then, send the call to the CM routing policy so it goes through CM's voicemail hunt group. If you dial the voicemail pilot from the CM location, then actually route the call to your voicemail. With a setup like you can always look at things from a design perspective as having the voicemail "behind" the PBX.
- Thread starter
- #3
I was able to resolved this issue within the VM dialing plan. What I am struggling with is the whole CM/LSP architecture. When using this VM system Mobile App you have the option when viewing the msg to call back the number, instead of just standard vm reply. The VM system first establishes a call to the user of the mobile app to establish the connection, while at the same time the PBX is making the call to the intended party. When I have a user in an LSP site using this the PBX is not following the ARS location routing in place for that site and basically is sending the call out the main locations ars table. I tried adding the IP subnets of the main site and this remote site in the SM location, but it didn't alter the behavior.
mattKnight
Programmer
Is this AVST CallXpress by any chance?
>When I have a user in an LSP site using this the PBX is not following the ARS location routing in place for that site and basically is sending the call out the main locations ars table. I tried adding the IP subnets of the main site and this remote site in the SM location, but it didn't alter the behavior
It will do as the call is initated by the VM box, which probably isn't location aware.
Take Care
Matt
I have always wished that my computer would be as easy to use as my telephone.
My wish has come true. I no longer know how to use my telephone.
>When I have a user in an LSP site using this the PBX is not following the ARS location routing in place for that site and basically is sending the call out the main locations ars table. I tried adding the IP subnets of the main site and this remote site in the SM location, but it didn't alter the behavior
It will do as the call is initated by the VM box, which probably isn't location aware.
Take Care
Matt
I have always wished that my computer would be as easy to use as my telephone.
My wish has come true. I no longer know how to use my telephone.
- Thread starter
- #5
mattKnight
Programmer
It's a PITA for many users, but could you define 2 mobile device - for the same physical device, one with the correct number for CLI matching and one prefixed with unique routing prefix to force call out of correct site's trunks
for example
Device 1 - Phone, can logon, can't receive calls - 01234 567890
Device 2 - Phone, can't logon, can receive calls - 9222 01234 567890
where prefix 9222 routes out of site 2's trunks
Might work...
Take Care
Matt
I have always wished that my computer would be as easy to use as my telephone.
My wish has come true. I no longer know how to use my telephone.
for example
Device 1 - Phone, can logon, can't receive calls - 01234 567890
Device 2 - Phone, can't logon, can receive calls - 9222 01234 567890
where prefix 9222 routes out of site 2's trunks
Might work...
Take Care
Matt
I have always wished that my computer would be as easy to use as my telephone.
My wish has come true. I no longer know how to use my telephone.
- Thread starter
- #7
This is interesting.. essentially each LSP would get ID'd by a prefix (Ex 222) and when a call function is attempted from the mobile App, CM would have an entry for each in the main ARS table that places the call out over the local site's TG?
Pretty much, yeah, that's it.
In larger Avaya voicemails, you can define sites and have dial plans/rules for each site.
I guess you'd want to think about whether its worth it to have a unique route pattern and dialed string to send calls out locally all the time, or whether it would be easier to massage everything coming out of that voicemail to dial out your core local site.
In larger Avaya voicemails, you can define sites and have dial plans/rules for each site.
I guess you'd want to think about whether its worth it to have a unique route pattern and dialed string to send calls out locally all the time, or whether it would be easier to massage everything coming out of that voicemail to dial out your core local site.
- Thread starter
- #9
At the end of the day the VM system sends the request to CM to perform the dial out and you would think CM would see the extension and know it's associated with a specific NR/location. The US is kind of easy to deal with because the dialing is pretty standard, but International is way more complicated.
- Status