Douglas,
Hi, the itsp is very flexible and expects CLI in from field within the DID range. So therefore using "transform extension" should be straight forward, but it just doesn't work. I am afraid I have to reinstall sipx if we can not figure this out. This always works, but now and then I have experienced that it just doesn't work. I am not sure which process does the transformation, but you asked for the INVITE in and out of sipxBridge: "2011-08-16T21:00:26.835000Z":50892:INCOMING:INFO:ec2-184-72-109-69.comp ute-1.amazonaws.com:PipelineThread-1:00000000:sipXbridge:"Read SIP Message:\n----Remote Host:10.0.0.10---- Port: 37396----\nINVITE sip:[email protected];sipxecs-lineid=3 SIP/2.0\r\nRoute: <sip:10.0.0.10:5090;lr>\r\nRecord-Route: <sip:10.0.0.10:5060;lr;sipXecs-CallDest=UNK%2CINTN;sipXecs-rs=%2Aauth%7E .%2Afrom%7ENGQ1NWQyN2Y%60.900_ntap%2ACrT%7EOTAuMjIyLjk2LjEyOjU4NDk2O3RyY W5zcG9ydD11ZHA%60.900_ntap%2Aid%7EMTA2MDMtMg%60%60%212dbfd3a6177c474ee99 a9070271dca69>\r\nVia: SIP/2.0/TCP 10.0.0.10;branch=z9hG4bK-XX-d891mOojJsKRiK_BeRVCdAsY0A;rport=37396\r\nVi a: SIP/2.0/UDP 10.0.0.10;branch=z9hG4bK-XX-d88ewlqOPCFPnjk1`yy4TlMt1w~xW2TAGlkjsspGJ8U1 OhQkA;id=10603-2\r\nVia: SIP/2.0/UDP 10.0.0.10;branch=z9hG4bK-XX-d8894Ez6lAqWDUGvAwLqv6f5Iw~8oJpyC4VVqQ9znB`0 GttGg\r\nVia: SIP/2.0/UDP 192.168.0.6:58496;branch=z9hG4bK-d8754z-141521ccb26199d8-1---d8754z-;rpo rt=58496;received=90.222.96.12\r\nMax-Forwards: 16\r\nContact: <sip:[email protected]:58496;x-sipX-privcontact=192.168.0.6%3A58496>\r\n To: \"92127572479\" <sip:[email protected]>\r\nFrom: \"8972\" <sip:[email protected]>;tag=4d55d27f\r\nCall-ID: YjkyZGYyNzk1YjYzZWQ4Y2E4ZWM1Mjc5ZTVjMDFmNmU.\r\nCSeq: 2 INVITE\r\nAllow: INVITE,ACK,CANCEL,OPTIONS,BYE,REFER,NOTIFY,MESSAGE,SUBSCRIBE,INFO\r\nCon tent-Type: application/sdp\r\nProxy-Authorization: Digest username=\"8972\",realm=\"ec2-184-72-109-69.compute-1.amazonaws.com\",no nce=\"dd4d4fe0b582fa73b797434e606e0f9d4e4ada6a\",uri=\"sip:92127572479@1 84.72.109.69\",response=\"04bc2fc24f4455907c6db622f6ac5e65\",cnonce=\"53 0c6196b4c70280af90a60229b47d0b\",nc=00000001,qop=auth,algorithm=MD5\r\nS upported: replaces\r\nUser-Agent: X-Lite 4 release 4.1 stamp 63214\r\nDate: Tue, 16 Aug 2011 21:00:26 GMT\r\nExpires: 7200\r\nX-Sipx-Handled: X10.0.0.10-184.72.109.69\r\nContent-Length: 261\r\n\r\nv=0\r\no=- 12958002043454457 1 IN IP4 192.168.0.6\r\ns=CounterPath X-Lite 4.1\r\nc=IN IP4 192.168.0.6\r\nt=0 0\r\nm=audio 30246 RTP/AVP 0 8 101\r\nc=IN IP4 10.0.0.10\r\na=rtpmap:101 telephone-event/8000\r\na=fmtp:101 0-15\r\na=sendrecv\r\na=x-sipx-ntap:X10.0.0.10-184.72.109.69;2\r\n====== ==============END====================\n" "2011-08-16T21:00:26.943000Z":50953:OUTGOING:INFO:ec2-184-72-109-69.comp ute-1.amazonaws.com:PipelineThread-1:00000000:sipXbridge:"Sent SIP Message :\n----Remote Host:204.16.54.4---- Port: 5060----\nINVITE sip:[email protected];user=phone SIP/2.0\r\nCall-ID: YjkyZGYyNzk1YjYzZWQ4Y2E4ZWM1Mjc5ZTVjMDFmNmU..0\r\nCSeq: 1 INVITE\r\nFrom: \"8972\" <sip:[email protected]>;tag=5467023451374033598\r\nTo: <sip:[email protected];user=phone>\r\nVia: SIP/2.0/UDP 184.72.109.69:5080;branch=z9hG4bK7d8de7b84d8b097e5898107da0938f9c343534\ r\nMax-Forwards: 70\r\nUser-Agent: sipXecs/4.4.0 sipXecs/sipxbridge (Linux)\r\nP-Asserted-Identity: \"8972\" <sip:[email protected]>\r\nContact: <sip:[email protected]:5080;transport=udp>\r\nRoute: <sip:204.16.54.4:5060;transport=udp;lr>\r\nSession-Expires: 7200;refresher=uac\r\nReferences: YjkyZGYyNzk1YjYzZWQ4Y2E4ZWM1Mjc5ZTVjMDFmNmU.;rel=chain;sipxecs-tag=reque st-invite-z9hg4bk-xx-d891moojjskrik_bervcdasy0a\r\nAllow: INVITE,BYE,ACK,CANCEL,OPTIONS\r\nSupported: timer\r\nContent-Type: application/sdp\r\nContent-Length: 278\r\n\r\nv=0\r\no=sipxbridge 8402196902608860359 1 IN IP4 184.72.109.69\r\ns=CounterPath X-Lite 4.1\r\nc=IN IP4 184.72.109.69\r\nt=0 0\r\nm=audio 30500 RTP/AVP 0 101\r\nc=IN IP4 184.72.109.69\r\na=rtpmap:101 telephone-event/8000\r\na=fmtp:101 0-15\r\na=sendrecv\r\na=x-sipx-ntap:X10.0.0.10-184.72.109.69;2\r\n------ --------------END--------------------\n" ________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of Douglas Hubler Sent: 15 August 2011 15:43 To: Discussion list for users of sipXecs software Subject: Re: [sipx-users] Individual CLI not possible 2011/8/15 Sven Evensen <[email protected]> This is an issue I have seen now and then and I also saw mentioned earlier here, but was never resolved. On outbound calls through SIP trunk to ITSP, we want every user to emit own CLI. Normally that will be done in the GW setting with transform extension feature. That works most of the time, NOT here. Alternatively we can set the full CLI in the users's callerID section. That also does NOT work. The only way the outgoing INVITE has anything but the ext number is when I set default caller ID in the GW. But that is not what I want. Unless I missed it, what specific header the SIP message are you expecting to be the user's caller id. Each ITSP can be different on what is uses for caller id to PSTN. sipXbridge config is very confusing here so check each setting on the page, and report them back here. Even the advanced settings. Inspect the SIP message in and out of sipXbridge to identify if the header is goes in wrong or comes out wrong.
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
