"+" sign as a prefix 2

[plokijuh]

Hi guys.

Yeastar is connected with OS4000v8 via SIP trunk.

Whenever I call any Yeastar Subscriber from an external number I get a "+" sign before the number like this:
+000 450-27-20

I use this LODR
ADD-LODR:251,,,,ECHOALL;
ADD-LODR:251,,,,END;
ADD-LODR:251,,,"Yeastar";

I would be grateful for any help!

 

[Moriendi]

The STMI is a protocol convertor. It has Cornet-NQ on one side and SIP on the other. The call generated from OS4K to Yeastar will enter STMI on Cornet-NQ side with an NPI/TON, which doesn't have a like for like mapping on the SIP side, apart from ISDN/International will cause a leading + on the outgoing SIP invite.

I'm not sure if your problem is with the called or calling numbers.

Try forcing the outging NPI to UNKNOWN/UNKNOWN or ISDN/UNKNOWN. You can change with LODR. Or try LINO or LINC in the COT. Once you start converting between these number formats it helps to have a correct KNDEF/KNPRE etc or you can generate some strange numbers. But try it and see.

In anycase, leading + is caused by ISDN/INT somewhere in the flow.

 

[plokijuh]

Thank you very much.

I'll check and write back.

 

[plokijuh]

Hi guys. Problem solved. And this is what I did.

I added LINC to the COT, which didn't help and changed LODR with no result.

Moriendi pointed that the problem is somewhere in the flow, so I decided to switch the COT completely.

I change COT=251 to COT=90, and leading "+" sign (prefix) gone.

ADD-COT:251,RCL&XFER&ANS&CHRT&KNOR&CEBC&FWDN&FNAN&BSHT&BLOC&DPRE&LWNC&ATRS&TR6T&TSCS&ICZL&DFNN&LINC&NTON,,;

ADD-COT:90,RCL&XFER&ANS&CHRT&KNOR&CEBC&FWDN&FNAN&BSHT&BLOC&DPRE&LWNC&ATRS&TR6T&TSCS&ICZL&DFNN&NTON,,;

NGL, I don't know what exactly caused the problem.

Thanks for the tip Moriendi!

 

[Moriendi]

Yes that doesn't really make any sense, the COTs are the same apart from LINC. Something else changed.

If you need to look again, use the Assistant RDS trace to trace the ISDN side of the STMI, you'll see the NPI/TON in clear text, so you can see what affect any changes might have. LINC forces ISDN/UNKNOWN, LINO is UNKNOWN/UNKNOWN, you would see it in RDS in the outgoing setup to STMI. With neither in, it will be unfluenced by LODR as you can set NPI as one of the LODR steps. When you say "no result".. well there must have been some result, even if you still got the + somewhere, so it's always worth a look with RDS.

 

[plokijuh]

Thanks for the additional info Moriendi.

I'll check with Assistant RDS's and check all of the COTs I have to be sure what exactly cause the problem.