[Asterisk-Users] SIP registration

Bob Scheller bobscheller at msn.com
Tue Mar 11 21:13:54 MST 2003


I have a test SIP account set up with WorldCom and I have been trying to
have Asterisk register to the WorldCom server with no luck. It appears
that the SIP headers are different coming from Asterisk. I have included
a packet capture from a successful login with a Windows Messenger client
for reference. I have also copied in the SIP packet I captured with sip
debug turned on. In my sip.conf file, I have the following line under
the general context:

Register=bobscheller:password at 166.60.255.41

Any pointers or assistance is appreciated.

Thanks,
Bob

******ASTERISK SIP PACKET ****************

XXX Need to handle Retransmitting XXX:
REGISTER sip:166.60.255.41 SIP/2.0
Via: SIP/2.0/UDP 68.86.118.111:5060;branch=12720924
From: <sip:bobscheller at 166.60.255.41>;tag=08e71f4b
To: <sip:bobscheller at 166.60.255.41>;tag=08e71f4b
Contact: <sip:s at 68.86.118.111:5060;transport=udp>
Call-ID: 4a4af9d005d5b69523478ccd5b01bd8e at 68.86.118.111
CSeq: 113 REGISTER
User-Agent: Asterisk PBX
Expires: 120
Event: registration
 (no NAT) to 166.60.255.41:5060

********************************************

******SUCCESSFUL REGISTRATION WITH MS-MESSENGER****

Frame 3 (702 bytes on wire, 702 bytes captured)
Ethernet II, Src: 44:45:53:54:42:00, Dst: 00:00:66:61:6b:65
Internet Protocol, Src Addr: 166.50.129.159 (166.50.129.159), Dst Addr:
166.60.255.41 (166.60.255.41)
User Datagram Protocol, Src Port: 1221 (1221), Dst Port: 5060 (5060)
Session Initiation Protocol
    Request line: REGISTER sip:bobscheller SIP/2.0
    Method: REGISTER
    Message Header
        Via: SIP/2.0/UDP 166.50.129.159:15329
        From: <sip:bobscheller>;tag=d09262e2-fe8f-4350-92ab-74500ad74218
        To: <sip:bobscheller>
        Call-ID: 55323746-7eaa-4b37-9ca4-d9328f2e158e at 166.50.129.159
        CSeq: 2 REGISTER
        Contact: <sip:166.50.129.159:15329>;methods="INVITE, MESSAGE,
INFO, SUBSCRIBE, OPTIONS, BYE, CANCEL, NOTIFY, ACK"
        User-Agent: Windows RTC/1.0
        Expires: 1200
        Event: registration
        Allow-Events: presence
        Proxy-Authorization: Digest username="", realm="WCOM",
algorithm="md5", uri="sip:bobscheller",
nonce="2a26142dab7d57ee87a2a7af113d9ca8.1047441261",
response="2210be3b6c2b51959e3d544bcc80f601"
        Content-Length: 0

Frame 4 (419 bytes on wire, 419 bytes captured)
Ethernet II, Src: 00:00:66:61:6b:65, Dst: 44:45:53:54:42:00
Internet Protocol, Src Addr: 166.60.255.41 (166.60.255.41), Dst Addr:
166.50.129.159 (166.50.129.159)
User Datagram Protocol, Src Port: 5060 (5060), Dst Port: 15329 (15329)
Session Initiation Protocol
    Status line: SIP/2.0 407 Proxy Authentication Required
    Status-Code: 407
    Message Header
        v: SIP/2.0/UDP 166.50.129.159:15329;received=166.50.129.159
        f: <sip:bobscheller>;tag=d09262e2-fe8f-4350-92ab-74500ad74218
        t: <sip:bobscheller>;tag=382ebd3e
        i: 55323746-7eaa-4b37-9ca4-d9328f2e158e at 166.50.129.159
        CSeq: 2 REGISTER
        l: 0
        Proxy-Authenticate: DIGEST
realm="WCOM",nonce="2a26142dab7d57ee87a2a7af113d9ca8.1047441261"

Frame 7 (713 bytes on wire, 713 bytes captured)
Ethernet II, Src: 44:45:53:54:42:00, Dst: 00:00:66:61:6b:65
Internet Protocol, Src Addr: 166.50.129.159 (166.50.129.159), Dst Addr:
166.60.255.41 (166.60.255.41)
User Datagram Protocol, Src Port: 1222 (1222), Dst Port: 5060 (5060)
Session Initiation Protocol
    Request line: REGISTER sip:bobscheller SIP/2.0
    Method: REGISTER
    Message Header
        Via: SIP/2.0/UDP 166.50.129.159:15329
        From: <sip:bobscheller>;tag=0fa3a037-aa1e-4583-a193-53daefdab75f
        To: <sip:bobscheller>
        Call-ID: 900227e0-eaad-4221-a570-921e0e62f7b1 at 166.50.129.159
        CSeq: 2 REGISTER
        Contact: <sip:166.50.129.159:15329>;methods="INVITE, MESSAGE,
INFO, SUBSCRIBE, OPTIONS, BYE, CANCEL, NOTIFY, ACK"
        User-Agent: Windows RTC/1.0
        Expires: 1200
        Event: registration
        Allow-Events: presence
        Proxy-Authorization: Digest username="bobscheller",
realm="WCOM", algorithm="md5", uri="sip:bobscheller",
nonce="b7700c89f79057028b90322d86796384.1047441266",
response="6f3b8678d269830521af0ae47ed542be"
        Content-Length: 0

Frame 8 (290 bytes on wire, 290 bytes captured)
Ethernet II, Src: 00:00:66:61:6b:65, Dst: 44:45:53:54:42:00
Internet Protocol, Src Addr: 166.60.255.41 (166.60.255.41), Dst Addr:
166.50.129.159 (166.50.129.159)
User Datagram Protocol, Src Port: 5060 (5060), Dst Port: 15329 (15329)
Session Initiation Protocol
    Status line: SIP/2.0 100 Trying
    Status-Code: 100
    Message Header
        v: SIP/2.0/UDP 166.50.129.159:15329;received=166.50.129.159
        f: <sip:bobscheller>;tag=0fa3a037-aa1e-4583-a193-53daefdab75f
        t: <sip:bobscheller>
        i: 900227e0-eaad-4221-a570-921e0e62f7b1 at 166.50.129.159
        CSeq: 2 REGISTER
        l: 0

Frame 9 (429 bytes on wire, 429 bytes captured)
Ethernet II, Src: 00:00:66:61:6b:65, Dst: 44:45:53:54:42:00
Internet Protocol, Src Addr: 166.60.255.41 (166.60.255.41), Dst Addr:
166.50.129.159 (166.50.129.159)
User Datagram Protocol, Src Port: 5060 (5060), Dst Port: 15329 (15329)
Session Initiation Protocol
    Status line: SIP/2.0 200 OK
    Status-Code: 200
    Message Header
        v: SIP/2.0/UDP 166.50.129.159:15329;received=166.50.129.159
        f: <sip:bobscheller>;tag=0fa3a037-aa1e-4583-a193-53daefdab75f
        t: <sip:bobscheller>;tag=3d4d7cc5
        i: 900227e0-eaad-4221-a570-921e0e62f7b1 at 166.50.129.159
        CSeq: 2 REGISTER
        l: 0
        m:
<sip:166.50.129.159:15329>;q=0.500;expires=1200;methods="INVITE,
MESSAGE, INFO, SUBSCRIBE, OPTIONS, BYE, CANCEL, NOTIFY, ACK"



More information about the asterisk-users mailing list