Hello, We have a problem where the presence of a user is not visible, because the subscribe to this user gets forwarded according to his forwarding rules in SipXecs. Situation: 482 subscribes to 283 sipxecs sends subscribe to 006xxxx@gateway presence fails.
Is this a known problem? You can find the SIP messages below: Regards, Elwin Formsma No. Time Source Destination Protocol Info 33910 1793.446211 192.168.20.62 192.168.104.1 SIP Request: SUBSCRIBE sip:[email protected] Frame 33910 (620 bytes on wire, 620 bytes captured) Ethernet II, Src: Procurve_65:4a:00 (00:21:f7:65:4a:00), Dst: Vmware_8e:09:d9 (00:50:56:8e:09:d9) Internet Protocol, Src: 192.168.20.62 (192.168.20.62), Dst: 192.168.104.1 (192.168.104.1) User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060) Source port: sip (5060) Destination port: sip (5060) Length: 586 Checksum: 0xf8d2 [correct] Session Initiation Protocol Request-Line: SUBSCRIBE sip:[email protected] SIP/2.0 Method: SUBSCRIBE [Resent Packet: False] Message Header Via: SIP/2.0/UDP 192.168.20.62:5060;branch=z9hG4bK8ceeaa5ebed6c0c456;rport From: Balie <sip:[email protected]>;tag=8ceeaa5ebed6c0c454 To: "Pepping, Reinder" <sip:[email protected]> Call-ID: [email protected] CSeq: 1 SUBSCRIBE Max-Forwards: 70 Expires: 3600 Event: dialog Accept: application/dialog-info+xml Supported: timer,replaces Contact: <sip:[email protected]> Allow: INVITE, ACK, CANCEL, BYE, OPTIONS, NOTIFY, SUBSCRIBE, MESSAGE, REFER User-Agent: VOP/1.5.1 Content-Length: 0 No. Time Source Destination Protocol Info 33911 1793.468858 192.168.104.1 193.78.57.197 SIP Request: SUBSCRIBE sip:[email protected];sipx-noroute=Voicemail;sipXecs-CallDest=MOB;sipxecs-lineid=1 Frame 33911 (1255 bytes on wire, 1255 bytes captured) Ethernet II, Src: Vmware_8e:09:d9 (00:50:56:8e:09:d9), Dst: Procurve_65:4a:00 (00:21:f7:65:4a:00) Internet Protocol, Src: 192.168.104.1 (192.168.104.1), Dst: 193.78.57.197 (193.78.57.197) User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060) Source port: sip (5060) Destination port: sip (5060) Length: 1221 Checksum: 0x2894 [incorrect, should be 0x065b (maybe caused by "UDP checksum offload"?)] Session Initiation Protocol Request-Line: SUBSCRIBE sip:[email protected];sipx-noroute=Voicemail;sipXecs-CallDest=MOB;sipxecs-lineid=1 SIP/2.0 Method: SUBSCRIBE [Resent Packet: False] Message Header Record-Route: <sip:192.168.104.1:5060;lr;sipXecs-rs=%2Aauth%7E.%2Afrom%7EOGNlZWFhNWViZWQ2YzBjNDU0%21643032cb934a2d033d4b8ad839c7bb63> Via: SIP/2.0/UDP 192.168.104.1;branch=z9hG4bK-XX-7e52unwSm_bvzd8SgdfCDcHZ5A Via: SIP/2.0/UDP 192.168.104.1;branch=z9hG4bK-XX-7e4dZo76WYk50w5AMrKgJ7iPoA~nEzw8E9g2DkojHAIKZ6CSQ Via: SIP/2.0/UDP 192.168.104.1;branch=z9hG4bK-XX-7e45Vn1ivmIaGIPObR5ZcEjOow~WmkYb3oMn5FGwMxI_HeNzg Via: SIP/2.0/UDP 192.168.20.62:5060;branch=z9hG4bK8ceeaa5ebed6c0c456;rport=5060 From: Balie <sip:[email protected]>;tag=8ceeaa5ebed6c0c454 To: "Pepping, Reinder" <sip:[email protected]> Call-Id: [email protected] Cseq: 1 SUBSCRIBE Max-Forwards: 16 Expires: 7200 Event: dialog Accept: application/dialog-info+xml Supported: timer,replaces Contact: <sip:[email protected];x-sipX-nonat> Allow: INVITE, ACK, CANCEL, BYE, OPTIONS, NOTIFY, SUBSCRIBE, MESSAGE, REFER User-Agent: VOP/1.5.1 Content-Length: 0 Date: Tue, 17 Apr 2012 09:39:59 GMT X-Sipx-Authidentity: <sip:[email protected];signature=4F8D3A6F%3A02f03015bd0a311b81ae2e88da9ffc25> _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
