Topic: Selintra - Extensions-Provisioning Dial Plans Wont fit??

[pmacdona]

I am having issues with Selintra accepting an extended dial plan in the provisioning section, when the example below is inserted where the default entry goes it drops to the line below <Dial_Plan_1_> and the provisioning fails, it's ok when I load it directly into the SPA941, any ideas??

(<000:0000>S0|2xxxS0|3xxxS0|013xxxx.!|019xxxx.!|018xx.!|00055!|00[23789]xxxxxxxxS0|0<5:035>xxxxxxxS0|004xxxxxxxxS0|3xxS0|0<6:036>xxxxxxxS0|0<7:037>xxxxxxxS0|0<8:038>xxxxxxxS0|0<9:039>xxxxxxxS0|xx.|*xx*x.)

Thanks
Peter

[SARK devs]

Hi Peter

It's almost certainly the pipe delimeters which the Sipura/Linksys dialplans use. Unfortunately, the SME Server database uses pipe delimiters to separate fields inside the database so I'm guessing they're playing hell with the database rows - .  

As it happens, Sam is working on Sipura/Linksys provisioning at the moment to fix the DHCP 66 issue we have (we spoke to a Guru at the UK distributor so we now know why it wasn't working correctly).  I'll ask him to look at this for you this morning.

Just out of curiosity, any particular reason why are you loading number manipulation dialplans into the 941 rather than handling them in SAIL/Asterisk?

Kind Regards

Selintra

[SARK devs]

I am having issues with Selintra accepting an extended dial plan in the provisioning section, when the example below is inserted where the default entry goes it drops to the line below <Dial_Plan_1_> and the provisioning fails, it's ok when I load it directly into the SPA941, any ideas??

Hi Peter,

This is a bug in Sail. Your dial plan conatins []. These characters are used to delimit files in the Sail provisioning textbox. Therefore, a conflict occurred. I have fixed this, and it will be in the next release. Also, please note that when you enter the dial plan in the provisioning textbox any < characters must be replaced by &lt; and any > characters must be replaced by &gt;

Also, the next release will have a fix so that provisioning of all Sipura/Linksys devices using DHCP 66 works.

Regards,

Selintra

[SARK devs]

Hi Peter

sail-339 which fixes your problem (and the DHCP 66 issue for Sipura/Linksys devices) is now available for download from here.

ftp://81.149.154.14/CurrentStableRelease/

Simply rpm -Uvh over your existing release.

Kind Regards

Selintra

[pmacdona]

Thanks guys, will give it a try in the next few days, really appreciate your quick responses.

[pmacdona]

It's mainly for timing purposes, rather than have the users wait for the timeout period b4 the call gets processed, and a hangover from my telco days where we try to minimise analysis of incorrectly formatted digit strings, I would prefer all dialling from the phone to be complete b4 sending, probably save on cpu activity if the server is not having to deal with incomplete dial strings.