Topic: creating a trunk with an * in it

[gippsweb]

I have a trunk with World Dial Point here in Aus, the internal/username has an "*" in it.
Like this 0000*00000

When I create a trunk or DiD group with this number the asterisk is stripped from the number, thus when someone one the network calls that number SAIL rejects the call because it sees 000000000, not 0000*00000 as it should.

Any ideas on a workaround for this one?

[gippsweb]

Just had to reset my routes as I recreated the trunk just in case.
It shows the primary correctly as 0000*00000.
But in routes and in extensions.conf it shows as 000000000

[gippsweb]

We can close this issue, I have solved my own problem

I created my own extension agi in extensions.conf under globals.

[mainmenu]
     
       exten => 0094*00000,1,agi(selintra,Inbound,${EXTEN})

(Number hidden to protect the guilty)

It's the same as the entry that doesn't work, but has the required * in the number


This way it appears to stay in place after a commit and I know have incoming calls working again on both my username/number and more importantly on my DiD.

[SARK devs]

yes,

a custom app would also have worked I think.   Currently we remove non-standard characters from the inout stream.  I'm actually pretty amazed that a carrier would use * in a  number when it is used so much as a control character within telephony.

Humph


Best

S


   

[gippsweb]

Yup, me thinks its pretty danm silly as well. But what can you do......