Passing * codes to dial plan is broken in ver4.0.1.3442

[voipguy]

Hi,

 

We went from ver 4.0.1.3438 to 4.0.1.3442 and just noticed today that we can no longer do *67 and the number....it should pass the whole string to the dial plan but it doesn't anymore.

 

If you have a number already in your address book with the *67 in the number it does work - like *6714166381234 the system will dial the complete number...but if you just pickup your phone and try to do *6714166381234 it reports back on the display not found and goes back to dial tone.

 

Can this one be fixed ASAP as we have customers that were using this feature?

 

Thanks

[pbx support]

Hi,

 

We went from ver 4.0.1.3438 to 4.0.1.3442 and just noticed today that we can no longer do *67 and the number....it should pass the whole string to the dial plan but it doesn't anymore.

 

If you have a number already in your address book with the *67 in the number it does work - like *6714166381234 the system will dial the complete number...but if you just pickup your phone and try to do *6714166381234 it reports back on the display not found and goes back to dial tone.

 

Can this one be fixed ASAP as we have customers that were using this feature?

 

Thanks

 

What is the dialplan entry - pattern & replacement?

 

Pattern \*([0-9]*)@.*, replacement sip:*\1@\d;user=phone seems to work fine still, provided, *67 is not in the list of domain feature codes.

[voipguy]

What is the dialplan entry - pattern & replacement?

 

Pattern \*([0-9]*)@.*, replacement sip:*\1@\d;user=phone seems to work fine still, provided, *67 is not in the list of domain feature codes.

 

Hi pbx support,

 

The dial plan is the same - all we did was upgrade from ver 4.0.1.3438 to 4.0.1.3442 that's it - we never changed anything else and now the *67 doesn't work.

[voipguy]

I got it working - what I did was switch the dial plan to text mode - copied it all...then deleted that dial plan - created a new dial plan with same text - now it works.