FW: Reg the Access to external Sip server.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi all,
Help me solving the issue below.

Best Regards,
Prabhu.


> Date: Thu, 24 Jan 2008 15:13:36 +0000
> From: bennylp@xxxxxxxxx
> To: prabhu.k at hotmail.com
> Subject: Re: Reg the Access to external Sip server.
> CC: vijayaraghavan_d at yahoo.com
>
> Hi Prabhu,
>
> for technical questions, I would suggest trying pjsip mailing list
> where more people would be able to help.
>
> kind regards,
> -benny
>
> On 1/24/08, Prabhu Kasthuri Ranga Samy  wrote:
>>
>>
>> Hi Benny,
>> Thanks, now i'm able to register with the public SIP server sucessfully
>> using public STUN server.
>>
>> But then, unable to make voice calls.
>>
>> Let me explain you in detail:
>> I have a Mobile client with a private IP(say Device A) that registers to
>> the public Sip server thru the company's router.When trying to call the
>> Mobile client(say Device B) with a public ip, the voice gets transmitted to
>> the Mobile client- Device B. But in the reverse direction the voice doesn't
>> get transmitted to Mobile client-Device A, as this has a private IP.
>>
>>
>>
>> I have also analyzed the logs from the Mobile client to check for the
>> absence of Voice and figured out a difference in the log generated by
>> Kapanga/X-Lite with that generated by the Mobile client. The difference is
>> coming in the SDP part when the client generates it.
>>
>>
>>
>> In the SDP info there is a field called as the Connection information
>> (represented by "c= " in the logs) and that field is filled by the Router's
>> Public IP (The value returned by the STUN Server) in case of Kapanga /
>> X-Lite. But for the Mobile client it is being filled by the Private IP that
>> assigned to the device.
>>
>>
>>
>> Is it possible to edit connection Information field to contain the IP that
>> was returned by the STUN server
>>
>>
>>
>> Kapanga/X-Lite Log:
>>
>>
>>
>> SIP/2.0 200 OK
>>
>> Via: SIP/2.0/UDP 122.169.243.35:5060;branch=z9hG4bK139532810143240
>>
>> Via: SIP/2.0/UDP 122.169.243.35:5060;branch=z9hG4bK433294692091956
>>
>> Via: SIP/2.0/UDP 122.169.243.35:5060;branch=z9hG4bK585635356702736
>>
>> User-Agent: Kapanga Softphone Desktop 1.00/2166s+1200897673_0018DEA55EAC
>>
>> From:
>> ;tag=23263168238867615_local.1201082481921_112_141
>>
>> To:
>> ;tag=411F89BDDD4F41AE14511EBCC8CFE33E
>>
>> Call-ID: 08580307826182665 at 122.169.243.35
>>
>> CSeq: 2 INVITE
>>
>> Contact: 
>>
>> Allow: INVITE, INFO, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER,
>> SUBSCRIBE, REFER, PUBLISH, UPDATE, MESSAGE
>>
>> Session-Expires: 1800;refresher=uac
>>
>> Content-Type: application/sdp
>>
>> Content-Length: 235
>>
>>
>>
>> v=0
>>
>> o=LapKap 1201088238 1201088253 IN IP4 10.238.116.67
>>
>> s=Kapanga [1201088238]
>>
>> c=IN IP4 203.99.209.151
>>
>> t=0 0
>>
>> m=audio 5100 RTP/AVP 0 8 101
>>
>> a=sendrecv
>>
>> a=maxptime:20
>>
>> a=ptime:20
>>
>> a=rtpmap:101 telephone-event/8000
>>
>> a=fmtp:101 0-15
>>
>>
>>
>>
>>
>> Mobile Client Log:
>>
>>
>>
>> 200 OK
>>
>> Via: SIP/2.0/UDP
>> 122.169.243.35:5060;received=122.169.243.35;branch=z9hG4bK193420002898656;ibmsid=local.1201153638093_24_29
>>
>> Via: SIP/2.0/UDP
>> 122.169.243.35:5060;branch=z9hG4bK287558343300969;ibmsid=local.1201153638093_23_28
>>
>> Via: SIP/2.0/UDP
>> 122.169.243.35:5060;branch=z9hG4bK347090155832467;ibmsid=local.1201153638093_22_27
>>
>> Call-ID: 6054879737724844 at 122.169.243.35
>>
>> From:
>> ;tag=44536314788759124_local.1201153638093_22_27
>>
>> To: ;tag=6292000683362064fe18
>>
>> CSeq: 2 INVITE
>>
>> Contact: 
>>
>> Allow: INVITE, ACK, BYE, CANCEL, SUBSCRIBE, NOTIFY, PUBLISH, REFER, MESSAGE,
>> OPTIONS
>>
>> Supported: replaces, norefersub
>>
>> Content-Type: application/sdp
>>
>> Content-Length: 243
>>
>>
>>
>>
>>
>>
>>
>> v=0
>>
>> o=- 3355689078 3355689079 IN IP4 10.238.116.67
>>
>> s=pjmedia
>>
>> c=IN IP4 10.238.116.67
>>
>> t=0 0
>>
>> m=audio 4000 RTP/AVP 0 101
>>
>> a=rtcp:4001 IN IP4 10.238.116.67
>>
>> a=rtpmap:0 PCMU/8000
>>
>> a=sendrecv
>>
>> a=rtpmap:101 telephone-event/8000
>>
>> a=fmtp:101 0-15
>>
>>
>>
>>
>>
>> Best Regards,
>>
>> Prabhu.
>>
>>
>>
>>
>> ________________________________
>> Date: Fri, 18 Jan 2008 07:21:17 +0000
>> From: bennylp@xxxxxxxxx
>> To: prabhu.k at hotmail.com
>> Subject: Re: Reg the Access to external Sip server.
>>
>> Hi Prabhu,
>>
>> PJSUA-LIB has the same functionality, but it is only activated when you
>> enable STUN in pjsua_config.stun_host. When you do, it'll do exactly like
>> what you mentioned.
>>
>> cheers,
>> -benny
>>
>>
>> On 1/17/08, Prabhu Kasthuri Ranga Samy  wrote:
>>
>> Hi Benny,
>> Let me first explain you the scenario / setup that we are testing the
>> client under.
>>
>> We have our company's Network and our Lab Network (Different from the
>> Company's Network). The SIP Server is running in the Lab Network on the
>> Public IP and we have one of the X-Lite clients running on one of the
>> Laptop's Connected via Wi-Fi connected to the Company's Network. For that
>> Laptop we have got the firewalls opened to connect to the Lab Network
>> (Firewall opened because the Lab network is not a part of Company's
>> Network). Now when we try to register the X-lite from that laptop to the SIP
>> server the client is registering successfully. But the X-Lite client is
>> sending multiple requests to the SIP Server.
>>
>> Because of these multiple registrations that are occurring the calls are
>> properly landing on the X-Lite even though the it is behind the router. But
>> when we check for the Mobile Client though it is registering successfully it
>> is sending only one request. It is not sending another request with the IP
>> of the router. Due to which when we try to call Mobile phone the client is
>> not ringing, because the Sip server is trying to send the request to the
>> Company's internal IP and that is not correct. The correct scenario would be
>> SIP server forwarding the request to the Company's router and then the
>> router in turn forwarding the request to the client (as happening for the
>> X-Lite)
>>
>> Is it possible to build such kind of functionality into the Mobile Client.
>> If so where this has to be changed in the application.
>>
>> Below is the log generated.
>>
>> X-lite is sending the first request with the Private IP(internal IP) and
>> eventhough its getting the success response from the server it is again
>> modifying the Contact field to the public IP and sending the request again.
>>
>>
>> Request 1:
>>
>> REGISTER sip:192.168.20.1 SIP/2.0
>> Via: SIP/2.0/UDP
>> 10.238.116.67:8000;branch=z9hG4bK-d87543-176aa55e204dec7d-1--d87543-;rport
>> Max-Forwards: 70
>> Contact: > 10.238.116.67:8000;rinstance=cec37dc14f68d167>
>> To: "Laptop1"
>> From: "Laptop1";tag=92707628
>> Call-ID:
>> 56288f2da25bb70dOGRiYzQzYTI4MWMxNjA4YTA3NzE0YThiNzJkMmNkZjk.
>> CSeq: 1 REGISTER
>> Expires: 3600
>> Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE,
>> SUBSCRIBE, INFO
>> User-Agent: X-Lite release 1002tx stamp 29712
>> Content-Length: 0
>>
>>
>> SIP/2.0 200 OK
>> Contact: ;expires=3600
>> Call-ID:
>> 56288f2da25bb70dOGRiYzQzYTI4MWMxNjA4YTA3NzE0YThiNzJkMmNkZjk.
>> CSeq: 1 REGISTER
>> From: "Laptop1" ;tag=92707628
>> To: "Laptop1" >>;tag=7592732651031109_local.1199363693919_83_90
>> Via: SIP/2.0/UDP
>> 10.238.116.67:8000;branch=z9hG4bK-d87543-176aa55e204dec7d-1--d87543-;rport;received=
>> 203.99.209.151
>> Date: Thu, 03 Jan 2008 07:01:14 GMT
>> Content-Length: 0
>>
>>
>>
>> Request 2:
>>
>> REGISTER sip:192.168.20.1 SIP/2.0
>> Via: SIP/2.0/UDP
>> 10.238.116.67:8000;branch=z9hG4bK-d87543-d95db715296be26b-1--d87543-;rport
>> Max-Forwards: 70
>> Contact: > 203.99.209.151:8000;rinstance=01cac0038b9bf03f>
>> To: "Laptop1"
>> From: "Laptop1";tag=92707628
>> Call-ID:
>> 56288f2da25bb70dOGRiYzQzYTI4MWMxNjA4YTA3NzE0YThiNzJkMmNkZjk.
>> CSeq: 3 REGISTER
>> Expires: 3600
>> Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE,
>> SUBSCRIBE, INFO
>> User-Agent: X-Lite release 1002tx stamp 29712
>> Content-Length: 0
>>
>>
>> SIP/2.0 200 OK
>> Contact: ;expires=3600
>> Call-ID:
>> 56288f2da25bb70dOGRiYzQzYTI4MWMxNjA4YTA3NzE0YThiNzJkMmNkZjk.
>> CSeq: 3 REGISTER
>> From: "Laptop1" ;tag=92707628
>> To: "Laptop1" >>;tag=06817725023763255_local.1199363693919_85_92
>> Via: SIP/2.0/UDP
>> 10.238.116.67:8000;branch=z9hG4bK-d87543-d95db715296be26b-1--d87543-;rport;received=
>> 203.99.209.151
>> Date: Thu, 03 Jan 2008 07:01:14 GMT
>> Content-Length: 0
>>
>> Kindly help me with the possible resolution for this.
>>
>> Best Regards,
>> Prabhu
>>
>>
>> ________________________________
>> Post free auto ads on Yello Classifieds now! Try it now!
>>
>> ________________________________
>> It's about getting married. Click here! Try it!

_________________________________________________________________
Post free property ads on Yello Classifieds now! www.yello.in
http://ss1.richmedia.in/recurl.asp?pid=220


[Index of Archives]     [Asterisk Users]     [Asterisk App Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [Linux API]
  Powered by Linux