search

Jeff-Lewis / telephone

Automatically exported from code.google.com/p/telephone
Other
0 stars 0 forks source link

Multifone got broken with 1.1.2 update #451

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
REGISTER, everything works fine
wait 10 minutes
Happens RE-REGISTER
can NOT receive calls, they do not reach it

1.1.2 on 10.9

I see that in first REGISTER we have my IP address and answer 200.
On subsequent RE-REGISTERS I see broken IP address and answer 403.
(Additionally it is very sad that status does NOT change to "not connected" on 
window)

1st REGISTER:
Session Initiation Protocol (REGISTER)
    Request-Line: REGISTER sip:sbc.megafon.ru SIP/2.0
    Message Header
        Via: SIP/2.0/UDP 212.119.200.205:1451;rport;branch=z9hG4bKPjE2IikIxGIGq.hr1PDiHgsTjcvQaqD3-V
        Max-Forwards: 70
        From: <sip:79262444460@multifon.ru>;tag=dYgfU04JJ4zCZZ.Ttj1BYGdVpkNJkGP0
        To: <sip:79262444460@multifon.ru>
        Call-ID: rg3cNOETMe.UfUECqGx3b5Zxl-yxbc.I
        CSeq: 13285 REGISTER
        User-Agent: Telephone 1.1.2
        Contact: <sip:79262444460@192.168.2.146:5060;ob>
        Expires: 300
        Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS
        [truncated] Proxy-Authorization: Digest username="79262444460", realm="BREDBAND", nonce=...
        Content-Length:  0

RE-REGISTER:
Session Initiation Protocol (REGISTER)
    Request-Line: REGISTER sip:multifon.ru SIP/2.0
    Message Header
        Via: SIP/2.0/TCP 192.168.100.100:7777;branch=z9hG4bK3BPFScPnoMttJNGF;rport
        Contact: <sip:79262444460@192.168.100.100:7777;rinstance=0CA0181D;transport=tcp>;expires=600
        Max-Forwards: 70
        From: <sip:79262444460@multifon.ru>;tag=E73867F2DBE856EF948B0E1DFFB36115
        Allow: OPTIONS, INVITE, ACK, REFER, CANCEL, BYE, NOTIFY
        Supported: replaces, path
        User-Agent: Megafon/1.4
        To: <sip:79262444460@multifon.ru>
        Expires: 600
        Call-ID: 72E5794E384E4C9443710C427A87123821764CC0
        P-hint: background
        CSeq: 1 REGISTER
        [truncated] Proxy-Authorization: Digest username="79262444460",realm="BREDBAND",algorithm=MD5,uri="sip:multifon.ru",nonce="...
        Content-Length: 0

Original issue reported on code.google.com by alexande...@gmail.com on 27 Nov 2013 at 2:01

GoogleCodeExporter commented 8 years ago 
rualpe-ws:comp paf$ ifconfig
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
    options=3<RXCSUM,TXCSUM>
    inet6 ::1 prefixlen 128 
    inet 127.0.0.1 netmask 0xff000000 
    inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 
    nd6 options=1<PERFORMNUD>
gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
stf0: flags=0<> mtu 1280
en0: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
    options=10b<RXCSUM,TXCSUM,VLAN_HWTAGGING,AV>
    ether a8:20:66:35:0a:1a 
    inet6 fe80::aa20:66ff:fe35:a1a%en0 prefixlen 64 scopeid 0x4 
    inet 192.168.2.146 netmask 0xffffff80 broadcast 192.168.2.255
    nd6 options=1<PERFORMNUD>
    media: autoselect (100baseTX <full-duplex>)
    status: active
en1: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
    ether 20:c9:d0:92:b4:a9 
    inet 169.254.234.130 netmask 0xffff0000 broadcast 169.254.255.255
    nd6 options=1<PERFORMNUD>
    media: autoselect
    status: active
en5: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
    options=60<TSO4,TSO6>
    ether 32:00:19:53:20:a0 
    media: autoselect <full-duplex>
    status: inactive
fw0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 4078
    lladdr a8:20:66:ff:fe:95:32:0a 
    nd6 options=1<PERFORMNUD>
    media: autoselect <full-duplex>
    status: inactive
p2p0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 2304
    ether 02:c9:d0:92:b4:a9 
    media: autoselect
    status: inactive
bridge0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
    options=63<RXCSUM,TXCSUM,TSO4,TSO6>
    ether aa:20:66:53:ba:00 
    Configuration:
        id 0:0:0:0:0:0 priority 0 hellotime 0 fwddelay 0
        maxage 0 holdcnt 0 proto stp maxaddr 100 timeout 1200
        root id 0:0:0:0:0:0 priority 0 ifcost 0 port 0
        ipfilter disabled flags 0x2
    member: en5 flags=3<LEARNING,DISCOVER>
            ifmaxaddr 0 port 6 priority 0 path cost 0
    nd6 options=1<PERFORMNUD>
    media: <unknown type>
    status: inactive
bridge100: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
    options=3<RXCSUM,TXCSUM>
    ether aa:20:66:53:ba:64 
    inet 10.0.0.1 netmask 0xffffff00 broadcast 10.0.0.255
    Configuration:
        id 0:0:0:0:0:0 priority 0 hellotime 0 fwddelay 0
        maxage 0 holdcnt 0 proto stp maxaddr 100 timeout 1200
        root id 0:0:0:0:0:0 priority 0 ifcost 0 port 0
        ipfilter disabled flags 0x2
    member: en1 flags=3<LEARNING,DISCOVER>
            ifmaxaddr 0 port 5 priority 0 path cost 0
    media: autoselect
    status: active
rualpe-ws:comp paf$

Original comment by alexande...@gmail.com on 27 Nov 2013 at 2:01

GoogleCodeExporter commented 8 years ago 
192.168.100.100:7777 should not appear in VIA and Contact -- that IP address is 
not valid at all.

I didn't have this problem with previous version.

Original comment by alexande...@gmail.com on 27 Nov 2013 at 2:02

GoogleCodeExporter commented 8 years ago 
192.168.100.100:7777 is not among interfaces. 
it's totally bogus.

rualpe-ws:comp paf$ ping 192.168.100.100
PING 192.168.100.100 (192.168.100.100): 56 data bytes
Request timeout for icmp_seq 0
^C
--- 192.168.100.100 ping statistics ---
2 packets transmitted, 0 packets received, 100.0% packet loss
rualpe-ws:comp paf$

Original comment by alexande...@gmail.com on 27 Nov 2013 at 2:03

GoogleCodeExporter commented 8 years ago 
The second REGISTER is from some other user agent:

User-Agent: Megafon/1.4

Original comment by eofs...@gmail.com on 27 Nov 2013 at 9:15

GoogleCodeExporter commented 8 years ago 
Please note that development moved to GitHub: 
https://github.com/eofster/Telephone

Original comment by eofs...@gmail.com on 27 Nov 2013 at 9:16

GoogleCodeExporter commented 8 years ago 
oh oh.
that was my iPhone, sitting on shared internet connection from my Mac.

I have this configuration for some time now. 

And only recently I've noticed no incoming calls on my Mac with "Available" 
status.

Gathering more info.
This particular ticket is confusing and I suggest to close it :)

Spasibo!

Original comment by alexande...@gmail.com on 28 Nov 2013 at 6:42