| Key: |
XPH-108
|
| Type: |
Bug
|
| Status: |
Closed
|
| Resolution: |
Fixed
|
| Priority: |
Critical
|
| Assignee: |
Unassigned
|
| Reporter: |
Raghu Venkataramana
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
|
This issue happened only once and I have predictable steps to reproduce. It may be required to look into the code to try and find out how this might have happened.
On a sipsoftphone that had STUN enabled and had registered itself, I sent out an INVITE and had audio issues. When I looked into the logs, I found the following lines in the sdp body:
v=0
o=sipX 5 5 IN IP4 59.92.137.30176.25.1.213
s=phone-call
c=IN IP4 59.92.137.30176.25.1.213
t=0 0
In the above lines 59.92.137.30 is my public address and 176.25.1.213 is my PCs IP address. They are concatinated in the sdp message sent out.
I restarted the phone and this problem wasn't seen
Attached :
sip logs
user config
pinger config
|
|
Description
|
This issue happened only once and I have predictable steps to reproduce. It may be required to look into the code to try and find out how this might have happened.
On a sipsoftphone that had STUN enabled and had registered itself, I sent out an INVITE and had audio issues. When I looked into the logs, I found the following lines in the sdp body:
v=0
o=sipX 5 5 IN IP4 59.92.137.30176.25.1.213
s=phone-call
c=IN IP4 59.92.137.30176.25.1.213
t=0 0
In the above lines 59.92.137.30 is my public address and 176.25.1.213 is my PCs IP address. They are concatinated in the sdp message sent out.
I restarted the phone and this problem wasn't seen
Attached :
sip logs
user config
pinger config |
Show » |
Sort Order:
|
SDP in Invite had wrong IP address
Attached are two set of logs
1) When the phone sent out the SIP message with sdp set to its private address
2) When the phone sent out the SIP messages with sdp set to its public address (expected behavior)
In both the cases we verified that STUN is working fine (used ethereal captures)