[Spce-user] Force CLI

[Martin Wong]

Hi Kevin,

unless I've stuffed something up... it's not working..

Have set user_cli as well as the E164 as well. From the sip trace, I see
that from the SPCE to the provider, the INVITE is as follows...

123.123.123.123 is the SPCE, 213.213.213.213 the provider.

As you can see, somehow the From: header has 9030 which is the extension
number of an Asterisk system. Therefore 9030 is not a valid number and thus
the provider puts it as anonymous. I can't seem to force the CLI.

Any ideas what's happening?

U 2013/05/10 01:05:03.335037 123.123.123.123:5060 -> 213.213.213.213:5060
INVITE sip:123456789 at 213.213.213.213:5060;transport=udp SIP/2.0.
Max-Forwards: 10.
Record-Route:
<sip:123.123.123.123;r2=on;lr=on;ftag=3686E06C-518BBB1F000519FA-062EA700;ngcplb=yes>.
Record-Route:
<sip:127.0.0.1;r2=on;lr=on;ftag=3686E06C-518BBB1F000519FA-062EA700;ngcplb=yes>.
Via: SIP/2.0/UDP
123.123.123.123;branch=z9hG4bK1bf6.45addc0c691ddcb65ab53185af6baca1.0.
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKOqRJLadA;rport=5080.
From: <sip:9030 at 123.123.123.123>;tag=3686E06C-518BBB1F000519FA-062EA700.
To: <sip:123456789 at 213.213.213.213>.
CSeq: 10 INVITE.
Call-ID: 243cdb514476fa870cabdef15e9c406f at 123.123.123.123_b2b-1.
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO.
Supported: replaces.
P-Asserted-Identity: <sip:9030 at 123.123.123.123>.
Content-Type: application/sdp.
Content-Length: 252.
Contact: <sip:ngcp-lb at 123.123.123.123:5060;ngcpct='sip:127.0.0.1:5080'>.
.
v=0.
o=root 13171 13172 IN IP4 123.123.123.123.
s=session.
c=IN IP4 123.123.123.123.
t=0 0.
m=audio 32354 RTP/AVP 18 101.
a=rtpmap:18 G729/8000.
a=fmtp:18 annexb=no.
a=rtpmap:101 telephone-event/8000.
a=fmtp:101 0-16.
a=ptime:20.
a=sendrecv.
a=rtcp:32355.



On Fri, May 10, 2013 at 12:21 AM, Kevin Masse <kmasse at questblue.com> wrote:

> Good morning, if you are looking to force the outbound caller ID of the
> subscriber make sure you have the DID in the e.164 number field.****
>
> That should force the outbound caller ID to be that number.****
>
> ** **
>
> For clients that have multiple outbound caller ID leave out the e.164
> subscriber number and place all the numbers in the alias area instead.****
>
> ** **
>
> Kevin****
>
> ** **
>
> ** **
>
> *From:* spce-user-bounces at lists.sipwise.com [mailto:
> spce-user-bounces at lists.sipwise.com] *On Behalf Of *Barry Flanagan
> *Sent:* Thursday, May 09, 2013 10:18 AM
> *To:* Martin Wong
> *Cc:* spce-user at lists.sipwise.com
> *Subject:* Re: [Spce-user] Force CLI****
>
> ** **
>
> On 9 May 2013 13:30, Martin Wong <martin.wong at binaryelements.com.au>
> wrote:****
>
> Hi,****
>
> ** **
>
> I am testing a few subscribers. ****
>
> ** **
>
> One is from a normal sip phone ... the fromuser at xx.xx.xx.xx is the
> correct CLI set, therefore the caller ID is correctly displayed at the end
> point device as it goes through the downstream provider.****
>
> ** **
>
> The other is an asterisk box. Even though the CLI is set in the SPCE
> portal, it comes up as something else in the fromuser at xx.xx.xx.xx****
>
> ** **
>
> I would like to force the CLI no matter what the asterisk box is giving
> out.****
>
> ** **
>
> ** **
>
> Hi ****
>
> ** **
>
> I think you want to set user_cli in the subscriber's preferences:****
>
> ** **
>
> user_cli: SIP username (the localpart of the whole SIP URI, eg., "user" of
> SIP URI "user at example.com"). "user-provided calling line identification"
> - specifies the SIP username that is used for outgoing calls. If set, this
> is put in the SIP "From" header (as user-provided calling number) if a
> client sends a CLI which is not allowed by "allowed_clis" or if
> "allowed_clis" is not set.****
>
> ** **
>
> ** **
>
> Hope this helps.****
>
> ** **
>
> -Barry****
>
> ** **
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20130510/d2a6cc2c/attachment-0001.html>