SOLVED Sipgate.co.uk passing alpha characters in DID breaks XIVO

[Oliver Gaskell]

I have numerous sipgate.co.uk trunks that have worked perfectly well with PIAF using full DID e.g 12345678e0 for inbound routing but when moving to XIV) i can't add 12345678e0 in contexts as it only takes numeric characters so i can't route the incoming calls? Has anyone come across this or got a fix or should i dump the sipgate trunks (not a big problem expect one DID that we have had a long time and would need to port out)

 

[wardmundy]

Paging @Sylvain Boily.

 

[Sylvain Boily]

Can you add a bug report on your redmine? But it's not really a bug it's a feature, because we don't support this. This is the first time i saw a configuration for a did like this... But if you give us input and report bug on our tracker we could track it and fix it.

 

[Sylvain Boily]

A workaround is possible, you only need to create a context like fix-did and you add this extension on it.

[fix-did]
exten = 12345678e0,1,Goto(from-extern,1234567890,1)

And change your sip trunk context configuration to fix-did.

 

[Oliver Gaskell]

A workaround is possible, you only need to create a context like fix-did and you add this extension on it.

[fix-did]
exten = 12345678e0,1,Goto(from-extern,1234567890,1)

And change your sip trunk context configuration to fix-did.

Thanks Sylvain - that fixed it: Took me a while to figure out what you mean't.

 

[Sylvain Boily]

Great!

 

[ostridge]

I think you will find that SG co.uk added the e0 to their sip-IDs sometime during their operations. The old sip-ID without the e0 also worked at thet time of change. Backward compatibility applies here - So simple way = try the base number without e0 (that is zero not Oh).

 

[Oliver Gaskell]

I think you will find that SG co.uk added the e0 to their sip-IDs sometime during their operations. The old sip-ID without the e0 also worked at thet time of change. Backward compatibility applies here - So simple way = try the base number without e0 .

Yes our increidble pbx/piaf box worked fine without the 'e0' but not on XIVO - anyway Sylvain's workround does the trick for anyone else stuck in the same boat..

 

[wardmundy]

Yes our increidble pbx/piaf box worked fine without the 'e0' but not on XIVO - anyway Sylvain's workround does the trick for anyone else stuck in the same boat..

Please put it on the XiVO bug tracker so it gets fixed permanently.. Thanks.