Is there any samples let's forwarded Subscribe fix the Contact: I mean Proxy URI not the customer mapped. Let's the followed NOTIFY go over proxy not P2P.
Thanks in avance.
Andrew O. Zhukov
2009/8/25 Andrew O. Zhukov gnugk@telegroup.com.ua:
Is there any samples let's forwarded Subscribe fix the Contact: I mean Proxy URI not the customer mapped. Let's the followed NOTIFY go over proxy not P2P.
Hi, I don't understand the question, could you explain it a bit more?
Andrew O. Zhukov schrieb:
Is there any samples let's forwarded Subscribe fix the Contact: I mean Proxy URI not the customer mapped.
?????
If the proxy should forward a SUBSCRIBE and fix the contact, just call fix_nated_contact() for the SUBSCRIBE request.
Let's the followed NOTIFY go over proxy not P2P.
You have to call record_route() for the SUBSCRIBE request.
klaus
Klaus Darilion пишет:
Andrew O. Zhukov schrieb:
Is there any samples let's forwarded Subscribe fix the Contact: I mean Proxy URI not the customer mapped.
?????
If the proxy should forward a SUBSCRIBE and fix the contact, just call fix_nated_contact() for the SUBSCRIBE request.
It fixed by fix_nated_contact(). However, it should be Openser, not customer IP:PORT outside NAT box. I guess :)
Openser receive registration of both X Lite clients from the same NAT box 193.28.184.10:xxx
12:29:14.9 RECEIVING FROM: 193.28.184.13:5060 SUBSCRIBE sip:100011@193.28.184.10:6144 SIP/2.0 Via: SIP/2.0/UDP 193.28.184.13;branch=z9hG4bK47b8.3e380593.0 Via: SIP/2.0/UDP 10.0.1.13:26946;received=193.28.184.10;branch=z9hG4bK-d8754z-e705876e4d477d7b-1---d8754z-;rport=26946 Max-Forwards: 69 Contact: sip:3039201@193.28.184.10:26946;nat=yes To: "100011"sip:100011@ipshka.com From: "Fishka"sip:3039201@ipshka.com;tag=b40d1f09 Call-ID: MDVlNmIzNDEzNGNkNTg1ZDc2ZjljMTQ5ZDE2MTI1Zjc. CSeq: 1 SUBSCRIBE Subject: Expires: 3600 Accept: multipart/related, application/rlmi+xml, application/pidf+xml Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO User-Agent: Bria release 2.2 stamp 45414 Event: presence Content-Length: 0
12:29:15.0 SENDING TO: 193.28.184.13:5060 SIP/2.0 202 Accepted To: "100011"sip:100011@ipshka.com;tag=27420b15 From: "Fishka"sip:3039201@ipshka.com;tag=b40d1f09 Via: SIP/2.0/UDP 193.28.184.13;branch=z9hG4bK47b8.3e380593.0;received=193.28.184.13 Via: SIP/2.0/UDP 10.0.1.13:26946;received=193.28.184.10;branch=z9hG4bK-d8754z-e705876e4d477d7b-1---d8754z-;rport=26946 Call-ID: MDVlNmIzNDEzNGNkNTg1ZDc2ZjljMTQ5ZDE2MTI1Zjc. CSeq: 1 SUBSCRIBE Contact: sip:100011@193.28.184.10:6144 Expires: 300 Content-Length: 0
12:29:15.0 SENDING TO: 193.28.184.10:26946 NOTIFY sip:3039201@193.28.184.10:26946;nat=yes SIP/2.0 To: "Fishka"sip:3039201@ipshka.com;tag=b40d1f09 From: "100011"sip:100011@ipshka.com;tag=27420b15 Via: SIP/2.0/UDP 193.28.184.10:6144;branch=z9hG4bK-d87543-545941037-1--d87543-;rport Call-ID: MDVlNmIzNDEzNGNkNTg1ZDc2ZjljMTQ5ZDE2MTI1Zjc. CSeq: 2 NOTIFY Contact: sip:100011@193.28.184.10:6144 Max-Forwards: 70 Content-Type: application/pidf+xml User-Agent: eyeBeam release 3006o stamp 17551 Subscription-State: active;expires=300 Event: presence Content-Length: 539
<?xml version="1.0" encoding="UTF-8"?> <presence xmlns="urn:ietf:params:xml:ns:pidf" xmlns:pp="urn:ietf:params:xml:ns:pidf:person" xmlns:et="urn:ietf:params:xml:ns:pidf:rpid:rpid-tuple" xmlns:ep="urn:ietf:params:xml:ns:pidf:rpid:rpid-person" xmlns:es="urn:ietf:params:xml:ns:pidf:rpid:status:rpid-status" xmlns:ci="urn:ietf:params:xml:ns:pidf:cipid" entity="sip:100011@ipshka.com"> <tuple id="t1"> <contact priority="1">sip:100011@ipshka.com</contact> <status> <basic>open</basic> </status> </tuple> </presence>
12:29:15.5 SENDING TO: 193.28.184.10:26946 NOTIFY sip:3039201@193.28.184.10:26946;nat=yes SIP/2.0 To: "Fishka"sip:3039201@ipshka.com;tag=b40d1f09 From: "100011"sip:100011@ipshka.com;tag=27420b15 Via: SIP/2.0/UDP 193.28.184.10:6144;branch=z9hG4bK-d87543-545941037-1--d87543-;rport Call-ID: MDVlNmIzNDEzNGNkNTg1ZDc2ZjljMTQ5ZDE2MTI1Zjc. CSeq: 2 NOTIFY Contact: sip:100011@193.28.184.10:6144 Max-Forwards: 70 Content-Type: application/pidf+xml User-Agent: eyeBeam release 3006o stamp 17551 Subscription-State: active;expires=300 Event: presence Content-Length: 539
<?xml version="1.0" encoding="UTF-8"?> <presence xmlns="urn:ietf:params:xml:ns:pidf" xmlns:pp="urn:ietf:params:xml:ns:pidf:person" xmlns:et="urn:ietf:params:xml:ns:pidf:rpid:rpid-tuple" xmlns:ep="urn:ietf:params:xml:ns:pidf:rpid:rpid-person" xmlns:es="urn:ietf:params:xml:ns:pidf:rpid:status:rpid-status" xmlns:ci="urn:ietf:params:xml:ns:pidf:cipid" entity="sip:100011@ipshka.com"> <tuple id="t1"> <contact priority="1">sip:100011@ipshka.com</contact> <status> <basic>open</basic> </status> </tuple> </presence>
You have to enable record_routing. E.g. try:
route { record_route();
.... }
regards klaus
Clients<-------->MainProxy<------>Presence Proxy
Andrew O. Zhukov schrieb:
Klaus Darilion пишет:
Andrew O. Zhukov schrieb:
Is there any samples let's forwarded Subscribe fix the Contact: I mean Proxy URI not the customer mapped.
?????
If the proxy should forward a SUBSCRIBE and fix the contact, just call fix_nated_contact() for the SUBSCRIBE request.
It fixed by fix_nated_contact(). However, it should be Openser, not customer IP:PORT outside NAT box. I guess :)
Openser receive registration of both X Lite clients from the same NAT box 193.28.184.10:xxx
12:29:14.9 RECEIVING FROM: 193.28.184.13:5060 SUBSCRIBE sip:100011@193.28.184.10:6144 SIP/2.0 Via: SIP/2.0/UDP 193.28.184.13;branch=z9hG4bK47b8.3e380593.0 Via: SIP/2.0/UDP 10.0.1.13:26946;received=193.28.184.10;branch=z9hG4bK-d8754z-e705876e4d477d7b-1---d8754z-;rport=26946
Max-Forwards: 69 Contact: sip:3039201@193.28.184.10:26946;nat=yes To: "100011"sip:100011@ipshka.com From: "Fishka"sip:3039201@ipshka.com;tag=b40d1f09 Call-ID: MDVlNmIzNDEzNGNkNTg1ZDc2ZjljMTQ5ZDE2MTI1Zjc. CSeq: 1 SUBSCRIBE Subject: Expires: 3600 Accept: multipart/related, application/rlmi+xml, application/pidf+xml Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO User-Agent: Bria release 2.2 stamp 45414 Event: presence Content-Length: 0
12:29:15.0 SENDING TO: 193.28.184.13:5060 SIP/2.0 202 Accepted To: "100011"sip:100011@ipshka.com;tag=27420b15 From: "Fishka"sip:3039201@ipshka.com;tag=b40d1f09 Via: SIP/2.0/UDP 193.28.184.13;branch=z9hG4bK47b8.3e380593.0;received=193.28.184.13 Via: SIP/2.0/UDP 10.0.1.13:26946;received=193.28.184.10;branch=z9hG4bK-d8754z-e705876e4d477d7b-1---d8754z-;rport=26946
Call-ID: MDVlNmIzNDEzNGNkNTg1ZDc2ZjljMTQ5ZDE2MTI1Zjc. CSeq: 1 SUBSCRIBE Contact: sip:100011@193.28.184.10:6144 Expires: 300 Content-Length: 0
12:29:15.0 SENDING TO: 193.28.184.10:26946 NOTIFY sip:3039201@193.28.184.10:26946;nat=yes SIP/2.0 To: "Fishka"sip:3039201@ipshka.com;tag=b40d1f09 From: "100011"sip:100011@ipshka.com;tag=27420b15 Via: SIP/2.0/UDP 193.28.184.10:6144;branch=z9hG4bK-d87543-545941037-1--d87543-;rport Call-ID: MDVlNmIzNDEzNGNkNTg1ZDc2ZjljMTQ5ZDE2MTI1Zjc. CSeq: 2 NOTIFY Contact: sip:100011@193.28.184.10:6144 Max-Forwards: 70 Content-Type: application/pidf+xml User-Agent: eyeBeam release 3006o stamp 17551 Subscription-State: active;expires=300 Event: presence Content-Length: 539
<?xml version="1.0" encoding="UTF-8"?>
<presence xmlns="urn:ietf:params:xml:ns:pidf" xmlns:pp="urn:ietf:params:xml:ns:pidf:person" xmlns:et="urn:ietf:params:xml:ns:pidf:rpid:rpid-tuple" xmlns:ep="urn:ietf:params:xml:ns:pidf:rpid:rpid-person" xmlns:es="urn:ietf:params:xml:ns:pidf:rpid:status:rpid-status" xmlns:ci="urn:ietf:params:xml:ns:pidf:cipid" entity="sip:100011@ipshka.com">
<tuple id="t1"> <contact priority="1">sip:100011@ipshka.com</contact> <status> <basic>open</basic> </status> </tuple> </presence>
12:29:15.5 SENDING TO: 193.28.184.10:26946 NOTIFY sip:3039201@193.28.184.10:26946;nat=yes SIP/2.0 To: "Fishka"sip:3039201@ipshka.com;tag=b40d1f09 From: "100011"sip:100011@ipshka.com;tag=27420b15 Via: SIP/2.0/UDP 193.28.184.10:6144;branch=z9hG4bK-d87543-545941037-1--d87543-;rport Call-ID: MDVlNmIzNDEzNGNkNTg1ZDc2ZjljMTQ5ZDE2MTI1Zjc. CSeq: 2 NOTIFY Contact: sip:100011@193.28.184.10:6144 Max-Forwards: 70 Content-Type: application/pidf+xml User-Agent: eyeBeam release 3006o stamp 17551 Subscription-State: active;expires=300 Event: presence Content-Length: 539
<?xml version="1.0" encoding="UTF-8"?>
<presence xmlns="urn:ietf:params:xml:ns:pidf" xmlns:pp="urn:ietf:params:xml:ns:pidf:person" xmlns:et="urn:ietf:params:xml:ns:pidf:rpid:rpid-tuple" xmlns:ep="urn:ietf:params:xml:ns:pidf:rpid:rpid-person" xmlns:es="urn:ietf:params:xml:ns:pidf:rpid:status:rpid-status" xmlns:ci="urn:ietf:params:xml:ns:pidf:cipid" entity="sip:100011@ipshka.com">
<tuple id="t1"> <contact priority="1">sip:100011@ipshka.com</contact> <status> <basic>open</basic> </status> </tuple> </presence>
Hi, I don't understand the question, could you explain it a bit more?
Iñaki Baz Castillo
<ibc at aliax.net>
Openser receive registration of both X Lite clients from the same NAT box 193.28.184.10:xxx
12:29:14.9 RECEIVING FROM: 193.28.184.13:5060 SUBSCRIBE sip:100011@193.28.184.10:6144 SIP/2.0 Via: SIP/2.0/UDP 193.28.184.13;branch=z9hG4bK47b8.3e380593.0 Via: SIP/2.0/UDP 10.0.1.13:26946;received=193.28.184.10;branch=z9hG4bK-d8754z-e705876e4d477d7b-1---d8754z-;rport=26946
Max-Forwards: 69 Contact: sip:3039201@193.28.184.10:26946;nat=yes To: "100011"sip:100011@ipshka.com From: "Fishka"sip:3039201@ipshka.com;tag=b40d1f09 Call-ID: MDVlNmIzNDEzNGNkNTg1ZDc2ZjljMTQ5ZDE2MTI1Zjc. CSeq: 1 SUBSCRIBE Subject: Expires: 3600 Accept: multipart/related, application/rlmi+xml, application/pidf+xml Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO User-Agent: Bria release 2.2 stamp 45414 Event: presence Content-Length: 0
12:29:15.0 SENDING TO: 193.28.184.13:5060 SIP/2.0 202 Accepted To: "100011"sip:100011@ipshka.com;tag=27420b15 From: "Fishka"sip:3039201@ipshka.com;tag=b40d1f09 Via: SIP/2.0/UDP 193.28.184.13;branch=z9hG4bK47b8.3e380593.0;received=193.28.184.13 Via: SIP/2.0/UDP 10.0.1.13:26946;received=193.28.184.10;branch=z9hG4bK-d8754z-e705876e4d477d7b-1---d8754z-;rport=26946
Call-ID: MDVlNmIzNDEzNGNkNTg1ZDc2ZjljMTQ5ZDE2MTI1Zjc. CSeq: 1 SUBSCRIBE Contact: sip:100011@193.28.184.10:6144 Expires: 300 Content-Length: 0
12:29:15.0 SENDING TO: 193.28.184.10:26946 NOTIFY sip:3039201@193.28.184.10:26946;nat=yes SIP/2.0 To: "Fishka"sip:3039201@ipshka.com;tag=b40d1f09 From: "100011"sip:100011@ipshka.com;tag=27420b15 Via: SIP/2.0/UDP 193.28.184.10:6144;branch=z9hG4bK-d87543-545941037-1--d87543-;rport Call-ID: MDVlNmIzNDEzNGNkNTg1ZDc2ZjljMTQ5ZDE2MTI1Zjc. CSeq: 2 NOTIFY Contact: sip:100011@193.28.184.10:6144 Max-Forwards: 70 Content-Type: application/pidf+xml User-Agent: eyeBeam release 3006o stamp 17551 Subscription-State: active;expires=300 Event: presence Content-Length: 539
<?xml version="1.0" encoding="UTF-8"?> <presence xmlns="urn:ietf:params:xml:ns:pidf" xmlns:pp="urn:ietf:params:xml:ns:pidf:person" xmlns:et="urn:ietf:params:xml:ns:pidf:rpid:rpid-tuple" xmlns:ep="urn:ietf:params:xml:ns:pidf:rpid:rpid-person" xmlns:es="urn:ietf:params:xml:ns:pidf:rpid:status:rpid-status" xmlns:ci="urn:ietf:params:xml:ns:pidf:cipid" entity="sip:100011@ipshka.com"> <tuple id="t1"> <contact priority="1">sip:100011@ipshka.com</contact> <status> <basic>open</basic> </status> </tuple> </presence>
12:29:15.5 SENDING TO: 193.28.184.10:26946 NOTIFY sip:3039201@193.28.184.10:26946;nat=yes SIP/2.0 To: "Fishka"sip:3039201@ipshka.com;tag=b40d1f09 From: "100011"sip:100011@ipshka.com;tag=27420b15 Via: SIP/2.0/UDP 193.28.184.10:6144;branch=z9hG4bK-d87543-545941037-1--d87543-;rport Call-ID: MDVlNmIzNDEzNGNkNTg1ZDc2ZjljMTQ5ZDE2MTI1Zjc. CSeq: 2 NOTIFY Contact: sip:100011@193.28.184.10:6144 Max-Forwards: 70 Content-Type: application/pidf+xml User-Agent: eyeBeam release 3006o stamp 17551 Subscription-State: active;expires=300 Event: presence Content-Length: 539
<?xml version="1.0" encoding="UTF-8"?> <presence xmlns="urn:ietf:params:xml:ns:pidf" xmlns:pp="urn:ietf:params:xml:ns:pidf:person" xmlns:et="urn:ietf:params:xml:ns:pidf:rpid:rpid-tuple" xmlns:ep="urn:ietf:params:xml:ns:pidf:rpid:rpid-person" xmlns:es="urn:ietf:params:xml:ns:pidf:rpid:status:rpid-status" xmlns:ci="urn:ietf:params:xml:ns:pidf:cipid" entity="sip:100011@ipshka.com"> <tuple id="t1"> <contact priority="1">sip:100011@ipshka.com</contact> <status> <basic>open</basic> </status> </tuple> </presence>
2009/8/25 Andrew O. Zhukov andre@telegroup.com.ua:
Openser receive registration of both X Lite clients from the same NAT box 193.28.184.10:xxx
12:29:14.9 RECEIVING FROM: 193.28.184.13:5060 SUBSCRIBE sip:100011@193.28.184.10:6144 SIP/2.0 Via: SIP/2.0/UDP 193.28.184.13;branch=z9hG4bK47b8.3e380593.0 Via: SIP/2.0/UDP 10.0.1.13:26946;received=193.28.184.10;branch=z9hG4bK-d8754z-e705876e4d477d7b-1---d8754z-;rport=26946 Max-Forwards: 69 Contact: sip:3039201@193.28.184.10:26946;nat=yes
It doesn't make sense. The UA uses UDP and send requests from port 193.28.184.13:5060, but it announces address 193.28.184.10:26946 in the Contact header (it means that it's listening in 193.28.184.10:26946), it doesn't make sense.
I assume both are the same network (192.28.184.X), right? then it doesn't make sense at all. How is your scenario between UA and OpenSER?
I assume both are the same network (192.28.184.X), right? then it doesn't make sense at all.
Now both UA are over the Symmetric NAT in the 10.0.1.* network
How is your scenario between UA and OpenSER?
It's the provider network without certain scenario. My main goal force the UA send all requests __only__ over Openser not P2P.
Andrew O. Zhukov wrote:
I assume both are the same network (192.28.184.X), right? then it doesn't make sense at all.
Now both UA are over the Symmetric NAT in the 10.0.1.* network
How is your scenario between UA and OpenSER?
It's the provider network without certain scenario. My main goal force the UA send all requests __only__ over Openser not P2P.
Please check again X-lite config On Account tab in Domain Proxy box Send outbound via ( ) domain (*) proxy Address : x.x.x.x
Where x.x.x.x your proxy address or dns name
Cheers, Misi
-
Andrew O. Zhukov -
Andrew O. Zhukov -
Iñaki Baz Castillo -
Klaus Darilion -
MÉSZÁROS Mihály