How not to send plus (+) before number 1

[infalex2xl]

Hello, sorry for my english, but I need help.
I connect to the mobile operator via sip.
they want me to send them the "user = phone" parameter in the INVITE in fields TO and FROM.
I found that hipath adds this parameter (user = phone) only if the number is transmitted in e.164 format.
In other cases, this parameter is not passed.
About field FROM, KNFOR will help me.
Let's talk on the example of LODR and field TO.

It works for me if LODR:
ADD-LODR:20,,,,NPI,ISDN ,INTERNAT;
ADD-LODR:20,,,,ECHOALL;
ADD-LODR:20,,,,END;
ADD-LODR:20,,,

sip uri In the TO:
+25075@ipaddress;user=phone

I do not want to send them a plus sign (+) before extension

How can i do this? if I change lodr to unknown, then the "user = phone" parameter will not be passed - it will look like this:
TO:25075@ipaddress

Or maybe someone knows how to pass this parameter for numbers that are not in the e.164 format?

In the end I need the line sip-uri to look like this TO:25075@ipaddress;user=phone

I hope for help, thanks.

 

[sbcsu]

Hi,
What happens if
ADD-LODR:20,,,,NPI,ISDN,NATIONAL;

 

[infalex2xl]

hi, with National

TO:25075@ipaddress

it's without user=phone and plus

 

[adibv]

If you set :
OUTPULSE: 250 or 25075
ECHO: position of area code , local code (depending of LDPLN: CD entries) ?

 

[infalex2xl]

Thanks for the help

I already tried with outpulse.
Ldpln is 2-xxxx
I tried:
npi,isdn,international, outpulse=2, echo 2
It turns out also.
TO:25075@ipaddress

no plus sign = no parameter (user = phone)

 

[adibv]

Which protocol do you use (TDCSU) ?

 

[infalex2xl]

ADD-TDCSU:OPT=NEW,PEN=1-02-011-0,COTNO=20,COPNO=20,DPLN=0,ITR=0,COS=20,LCOSV=32,LCOSD=32,CCT="TEST",DESTNO=20,PROTVAR=ECMAV2,SEGMENT=8,DEDSVC=NONE,TRTBL=GDTR,SIDANI=N,ATNTYP=TIE,CBMATTR=NONE,TCHARG=N,SUPPRESS=0,TRACOUNT=10,SATCOUNT=MANY,NNO=1-1-20,ALARMNO=2,FIDX=1,CARRIER=1,ZONE=EMPTY,COTX=20,FWDX=1,CHIMAP=N,UUSCCX=16,UUSCCY=8,FNIDX=1,NWMUXTIM=10,CLASSMRK=EC&G711&G729AOPT,TCCID="",TGRP=20,SRCHMODE=DSC,INS=Y,SECLEVEL=TRADITIO,HMUSIC=0,CALLTIM=60,WARNTIM=60,DEV=HG3550IP,BCHAN=1&&10,BCNEG=N,BCGR=1,LWPP=0,LWLT=0,LWPS=0,LWR1=0,LWR2=0,DMCALLWD=N;

 

[adibv]

For outgoing calls from 4k, I have no other ideea how can be modified external called pty.

For incoming calls from extern to 4k, 4k called pty digits (length,format) can be manipulated in TDCSU (via param SUPPRESS/DGTPR).
Maybe mobile operator partner have a similar option on their side to modify their called pty digits on incoming calls from 4k.

 

[Moriendi]

Adding "user=phone" is a function of the STMI loadware, not the 4K itself. So the STMI looks at what has been delivered to it, and decides whether to add that URI param.

If you look at a trace from the STMI, it will add it when it received an E.164 number. An E.164 number is indicated by leading +.

(SIP_SA 06 0x2fcf "04/17/2020 23:07:28.753786" CSipEngine.cpp 6837)
fAddUserPhoneParamToSipUri(): E.164 number (+1234567890) found in SIP URI, user=phone added

This makes sense. Only when you have an E.164 number can it sure that it has an unambiguous, diallable number. If there is no +, it cannot be guaranteed.

If you check RFC 3261, pg 150,

The set of valid telephone-subscriber strings is a subset of
valid user strings. The user URI parameter exists to
distinguish telephone numbers from user names that happen to
look like telephone numbers. If the user string contains a
telephone number formatted as a telephone-subscriber, the user
parameter value "phone" SHOULD be present. Even without this
parameter, recipients of SIP and SIPS URIs MAY interpret the
pre-@ part as a telephone number if local restrictions on the
name space for user name allow it.

I guess Unify response here would be that only with an E.164 number is it properly formatted as a telephone subscriber, and that's why it adds the 'phone' parameter in that case.

Are you sending them a true E.164 number with your dialled digits? You are only sending them 5 digits, 3 of which is the country code. Are they expecting some short code? I would expect them to be able to handle full E.164.

Alternatively, if you have a simplex V8 4K, you can import the Unify SBC and run that as a VM, and insert that between the STMI and provider. SBC has a parameter "Send user=phone in SIP URI - When checked, the SBC adds “user=phone” in SIP URIs towards SSP." But you'd need a license for the SBC.

Or, you could try a ticket to Unify to ask for a GUI parameter to enable/disable user=phone in the STMIX GUI, but I would expect that to be treated as change request, not a fault, and so would be slow and expensive, you'd probably have to pay. You won't know unless you ask.

 

[infalex2xl]

OK understood.
Thanks for the detailed answer.