Copy of the previously supported att.pv.xml

[PD-SII]

Does anyone happen to have a copy of the old ATT provider template (att.pv.xml) from the v16/v18 days? I no longer have a copy of this since it was removed in v20, but would like to do some testing with it. I believe it was CobaltIT that originally helped create this .. thanks everyone

 

[Evolute IT]

@cobaltit

 

[PD-SII]

Thought I'd try reviving this thread one last time to see if anyone happens to have this old ATT template .. thanks guys

 

[YiannisH_3CX]

That template was created over 10 years ago with a help of a partner if I remember correctly and was never updated. I am sure a lot has changed since then. You'd be better off testing with the Generic Sip trunk template as it bares a lot of similarities. Or better yet go with a supported provider which we test and update the templates whenever necessary.

 

[PD-SII]

Do you have a suggestion for how to easily migrate from the previous ATT template to the Generic without deleting the existing trunk and causing disruption? I couldn't find a way to do that without painfully deleting the trunk and re-creating it and I have quite a few users and DIDs with primary and secondary trunks setup. Everything is working fine .. you just couldn't edit the trunk because the template name no longer exists. I found a work-around that involved exporting and placing the xml file in the proper directory which then allows you to edit .. but with limited options that will require modifying the template itself in the future rather than offering options to do so from within the UI. ATT has special deals for government around here, so switching off of them is not really an option.

 

[paulodagraca]

Hello PD-SII,

The option to delete and re-create the trunk is not the correct way (in my opinion).

You can create a new trunk whilst the old trunk is still active, just make sure the registar server FQDN is not vallid (example change myprovider.com to myprovider.comx), also the Authentication ID shoud not be the same (also add an x at the end).
Then copy the whole DID list, you can also use the reports 'inbound rules', and you can use the import DID option in the new trunk.

Once you are happy with the setup, change over the trunk by modify the existing trunk (registar server and Authentication ID) to some non valid value and correct the new trunk by deleting the last X (registar server and Authentication ID).
This will do a fast change-over of trunk.
Then go to the outbound-rules and change the rules one by one, to the new trunk for the outgoing calls.

Do some testing in/out-bound, and when all is good, delete the 'old' trunk.
Some times delete of the old trunk is not possible if the emergency numbers are configured on the trunk, please also swap this to the new trunk.

I would normally do the trunk-setup during working hours and the trunk swap during night/off hours, to keep the work and impact as small as possible.
Good luck!

Paulo

 

[PD-SII]

Thanks for the response Paulo. One question .. how would you go about re-associating all the DIDs with the users again? I will have 2 trunks, so each DID has to be added to each user twice .. once from each trunk. I used to be able to do this with an Inbound Rules export/re-import, but that option looks to have been removed in v20

 

[PhoneMan123]

You can still do an import with a CSV file and they will get associated correctly as long as the csv is right. You can export the list from the Reports -> Inbound Rules and reformat it to match the import csv for the trunk.

 

[PD-SII]

That is what I was looking for .. thank you! Export from the Reports and then Import on the Trunk. They are just in two different locations now. I didn't remember seeing that option when we first migrated, but I must have overlooked it with the shuffling of things around. I didn't want to have to manually re-associate over a 1000 DIDs and thus why I was set on trying to make the existing trunk work

Thanks again guys for the help! I feel a lot better now knowing this import option exists

 

[YiannisH_3CX]

The format for the csv is DID,extension,name. For example +1234567890,100,Sales
This will associate DID +1234567890 to extension 100 with the name "Sales". The extension and name fields are optional so you could just DIDs to your trunk without assigning them.

 

[PD-SII]

Thanks for that info. I was planning to use the same format of the inbound rules export and just change the "Trunk" column to the name of the trunk I was importing to (similar to how it used to work). It doesn't look like you can export from the trunk to get the correct format, so will the headers of the CSV be "DID", "Extension", "Name" and look similar to what I have below? I can use the Text to Columns feature of Excel to separate the extension from the name in the "Destination" column of the Inbound Rules export. Also .. can you leave just the name off and populate only DID and Extension and have the DID associated with the existing extension?

DID	Extension	Name
1235557777	1000	Test1
3214448888	1001	Test2

 

[YiannisH_3CX]

so will the headers of the CSV be "DID", "Extension", "Name" and look similar to what I have below?

You actually do not need the headers in the columns. Create the excel and then delete the headers row,

Also .. can you leave just the name off and populate only DID and Extension and have the DID associated with the existing extension?

Yes you can. Only the DID is mandatory.

 

[PD-SII]

Perfect! Thanks again for the help! That's actually a bit easier than it used to be