This is what I think it should look like...

14:35:46.526192 00:0c:29:09:16:74 > 00:30:88:10:e5:cd, ethertype IPv4
(0x0800), length 1168: (tos 0x0, ttl 63, id 0, offset 0, flags [DF], proto
UDP (17), length 1154)
    69.34.33.146.5080 > 74.63.41.218.5060: [udp sum ok] SIP, length: 1126
    INVITE 
sip:[email protected]<sip%[email protected]>;user=phone
SIP/2.0
    Call-ID: [email protected]
    CSeq: 1 INVITE
    From: "Tony Graziano" <sip:*[email protected]
>;tag=9216259866852218105
    To: <sip:[email protected] <sip%[email protected]>
;user=phone>
    Via: SIP/2.0/UDP 69.34.33.146:5080
;branch=z9hG4bKf7bf546eb57565dfa49a86f94c1a7608373134
    Max-Forwards: 70
    User-Agent: sipXecs/4.2.1 sipXecs/sipxbridge (Linux)
    Contact: <sip:[email protected]:5080;transport=udp>
    Route: <sip:74.63.41.218:5060;transport=udp;lr>
    Session-Expires: 1800;refresher=uac
    References: [email protected]
;rel=chain;sipxecs-tag=request-invite-z9hg4bk-xx-bb1cx7apna62t0xbjasgihswtg
    Allow: INVITE,BYE,ACK,CANCEL,OPTIONS
    Supported: timer
    Content-Type: application/sdp
    Content-Length: 323

    v=0
    o=sipxbridge 412872721786354876 1 IN IP4 69.34.33.146
    s=Polycom IP Phone
    c=IN IP4 69.34.33.146
    t=0 0
    a=sendrecv
    m=audio 30500 RTP/AVP 9 0 8 101
    c=IN IP4 69.34.33.146
    a=rtpmap:9 G722/8000
    a=rtpmap:0 PCMU/8000
    a=rtpmap:8 PCMA/8000
    a=rtpmap:101 telephone-event/8000
    a=x-sipx-ntap:X10.255.251.2-69.34.33.146;7


On Fri, Aug 13, 2010 at 2:12 PM, Heather L. Sanders <[email protected]>wrote:

>  The ITSP requires that we send  ${itsp-registration-...@${itsp-domain} .
>
>
> I have attached the firewall pcap.  If you look at frame 8 of this pcap,
> you will see that the from header contains exactly that.  However, what is
> interesting...is that the PAI header contains my personalized callerid
> information in the format  ${user's-caller-...@${your-sip-domain} .
>
> So...as far as I can tell, when the call rings through, the ITSP reads the
> 'From' header and passes that along as the caller ID information, because,
> from what I understand about SIP/SDP protocols the PAI is *not* passed for
> caller id, it is for informational purposes only...right??
>
> I could have this backwards...I am new to this whole SIP thing, so please
> correct me if I am wrong.
>
>
>  ------------------------------
> Heather L. Sanders
> Linux Systems Administrator
> Saginaw Valley State University
> 7400 Bay Road
> 374 Wickes Hall
> University Center, MI 48710
> Office: (989) 964-2156
> Mobile: (989) 326-3300
> Email: [email protected]
>
> On 08/13/2010 12:38 PM, Douglas Hubler wrote:
>
> On Fri, Aug 13, 2010 at 10:13 AM, Heather L. Sanders <[email protected]> 
> <[email protected]> wrote:
>
>
>  I took your suggestion and ran a pcap at my firewall...I can see that my
> callerid info is in the PAI header.  However, my ITSP requires that we use a
> valid PAI, so sending anonymous is 'not an option' for us with this ITSP.
>
>
>  it seems there is no way to send empty PAI or PPI, would that help
> your situation?
>
> What is the exact value for PAI and PPI that your ITSP desires
>  e.g.
>     ${user's-caller-...@${your-sip-domain}
>     ${user's-caller-...@${itsp-domain}
>     ${itsp-registration-...@${itsp-domain}
>
>
>
>
> _______________________________________________
> sipx-users mailing list
> [email protected]
> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>



-- 
======================
Tony Graziano, Manager
Telephone: 434.984.8430
sip: [email protected]
Fax: 434.984.8431

Email: [email protected]

LAN/Telephony/Security and Control Systems Helpdesk:
Telephone: 434.984.8426
sip: [email protected]
Fax: 434.984.8427

Helpdesk Contract Customers:
http://www.myitdepartment.net/gethelp/

Why do mathematicians always confuse Halloween and Christmas?
Because 31 Oct = 25 Dec.
_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users/

Reply via email to