OpenSBC - 404 not found

Jun 20, 2013 02:15 AM PDT
Jim Herold
Palatine Police Department
I have a situation where-by I'd like to use SIP phones that would be behind NAT attached to my Shoretel system. I'm trying to use OpenSBC to do this and have had some success.

I can successfully register the SIP phone to my Shoretel system through OpenSBC, and can call the phone and have bidirectional audio.

The issue is that anytime I try to call from the SIP phone, whether an extension on my system, or to the PSTN I get a 'SIP 2.0/404 Not Found' message from Shoretel.

I've been looking at the packets and comparing a successfull call that isn't going through NAT or OpenSBC to a call that does and the differences are very minor. In both cases the To and From sections of the SIP Invite are identical.

Anybody have any thoughts? Where would I go for troubleshooting info on the Shoretel to get a better idea of what exactly it has issue with?

Thanks
Jun 24, 2013 06:58 PM PDT
Jim Herold
Palatine Police Department
'k, that may be helpful. I see in the register it's contact is sip:pmobile@172.16.0.106:5062, but when it invites it's sip:pmobile@172.16.0.106. So if I'm interpreting correctly that's likely the issue, and I don't see anything on OpenSBC to help me with that.

I'll try to set it up as a SIP Trunk and see if I can get further that way. Thanks for the help.
Jun 25, 2013 05:17 AM PDT
Jim Herold
Palatine Police Department
Thanks Juan. I'm using it for a SIP extension. In B2BUAUpperReg
mode. If I use B2BUA doesn't that mean I have to have OpenSBC doing
the registrations? I'd rather leave that to ShoreTel if possible.
It is overwriting the CONTACT header. Here's the Invite going to
OpenSBC: Session Initiation Protocol (INVITE) Request-Line: INVITE
sip:6273@sip.palatine.il.us SIP/2.0 Method: INVITE Request-URI:
sip:6273@sip.palatine.il.us Request-URI User Part: 6273 Request-URI
Host Part: sip.palatine.il.us [Resent Packet: False] Message Header
Via: SIP/2.0/UDP
192.168.17.100:41584;rport;branch=z9hG4bKPjFDQNM3jOx8HYIOmF6J1Elw6zts.Q4b9a
Transport: UDP Sent-by Address: 192.168.17.100 Sent-by port: 41584
RPort: rport Branch: z9hG4bKPjFDQNM3jOx8HYIOmF6J1Elw6zts.Q4b9a
Max-Forwards: 70 From: 'PD Mobile'
;tag=LCmoVaNuVSe-cXIh.bcKncK9pUEbx8ox SIP Display info: 'PD Mobile'
SIP from address: sip:pmobile@sip.palatine.il.us SIP from address
User Part: pmobile SIP from address Host Part: sip.palatine.il.us
SIP from tag: LCmoVaNuVSe-cXIh.bcKncK9pUEbx8ox To: SIP to address:
sip:6273@sip.palatine.il.us SIP to address User Part: 6273 SIP to
address Host Part: sip.palatine.il.us Contact: Contact URI:
sip:pmobile@172.31.9.43:41584;ob Contact URI User Part: pmobile
Contact URI Host Part: 172.31.9.43 Contact URI Host Port: 41584
Contact URI parameter: ob Call-ID: PtqHQa5Zeu8tqZvpTrUZB.TQmDnV39Ii
CSeq: 27583 INVITE Sequence Number: 27583 Method: INVITE Route:
Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE,
NOTIFY, REFER, MESSAGE, OPTIONS Supported: replaces, 100rel, timer,
norefersub Session-Expires: 1800 Min-SE: 90 User-Agent:
CSipSimple_sunfire-10/r2225 Content-Type: application/sdp
Content-Length: 295 Message Body Session Description Protocol
Session Description Protocol Version (v): 0 Owner/Creator, Session
Id (o): - 3581176380 3581176380 IN IP4 192.168.17.100 Session Name
(s): pjmedia Connection Information (c): IN IP4 192.168.17.100 Time
Description, active time (t): 0 0 Media Description, name and
address (m): audio 4000 RTP/AVP 8 0 101 Connection Information (c):
IN IP4 192.168.17.100 Media Attribute (a): rtcp:4001 IN IP4
192.168.17.100 Media Attribute Fieldname: rtcp Media Attribute
Value: 4001 IN IP4 192.168.17.100 Media Attribute (a): sendrecv
Media Attribute (a): rtpmap:8 PCMA/8000 Media Attribute Fieldname:
rtpmap Media Format: 8 MIME Type: PCMA Sample Rate: 8000 Media
Attribute (a): rtpmap:0 PCMU/8000 Media Attribute Fieldname: rtpmap
Media Format: 0 MIME Type: PCMU Sample Rate: 8000 Media Attribute
(a): rtpmap:101 telephone-event/8000 Media Attribute Fieldname:
rtpmap Media Format: 101 MIME Type: telephone-event Sample Rate:
8000 Media Attribute (a): fmtp:101 0-15 Media Attribute Fieldname:
fmtp Media Format: 101 [telephone-event] Media format specific
parameters: 0-15 And here's what it looks like from OpenSBC to
Shoretel: Session Initiation Protocol (INVITE) Request-Line: INVITE
sip:6273@172.17.0.12 SIP/2.0 Method: INVITE Request-URI:
sip:6273@172.17.0.12 Request-URI User Part: 6273 Request-URI Host
Part: 172.17.0.12 [Resent Packet: False] Message Header From: 'PD
Mobile' ;tag=LCmoVaNuVSe-cXIh.bcKncK9pUEbx8ox SIP Display info: 'PD
Mobile' SIP from address: sip:pmobile@172.17.0.12 SIP from address
User Part: pmobile SIP from address Host Part: 172.17.0.12 SIP from
tag: LCmoVaNuVSe-cXIh.bcKncK9pUEbx8ox To: SIP to address:
sip:6273@172.17.0.12 SIP to address User Part: 6273 SIP to address
Host Part: 172.17.0.12 Via: SIP/2.0/UDP
172.16.0.106:5060;iid=16463;branch=z9hG4bK4b68edab3c0a19108e328c6e26e46810;uas-addr=172.17.0.12;rport
Transport: UDP Sent-by Address: 172.16.0.106 Sent-by port: 5060
iid=16463 Branch: z9hG4bK4b68edab3c0a19108e328c6e26e46810
uas-addr=172.17.0.12 RPort: rport CSeq: 27583 INVITE Sequence
Number: 27583 Method: INVITE Call-ID:
PtqHQa5Zeu8tqZvpTrUZB.TQmDnV39Ii-0x005a Contact: Contact URI:
sip:pmobile@172.16.0.106 Contact URI User Part: pmobile Contact URI
Host Part: 172.16.0.106 User-Agent: OpenSBC v1.1.5-85 Max-Forwards:
69 Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE,
NOTIFY, REFER, MESSAGE, OPTIONS Supported: replaces, 100rel, timer,
norefersub Session-Expires: 1800 Min-SE: 90 Content-Type:
application/sdp Content-Length: 291 Message Body Session
Description Protocol Session Description Protocol Version (v): 0
Owner/Creator, Session Id (o): - 3581176380 3581176380 IN IP4
192.168.17.100 Session Name (s): pjmedia Connection Information
(c): IN IP4 172.16.0.106 Time Description, active time (t): 0 0
Media Description, name and address (m): audio 4002 RTP/AVP 8 0 101
Connection Information (c): IN IP4 172.16.0.106 Media Attribute
(a): rtcp:4001 IN IP4 192.168.17.100 Media Attribute Fieldname:
rtcp Media Attribute Value: 4001 IN IP4 192.168.17.100 Media
Attribute (a): sendrecv Media Attribute (a): rtpmap:8 PCMA/8000
Media Attribute Fieldname: rtpmap Media Format: 8 MIME Type: PCMA
Sample Rate: 8000 Media Attribute (a): rtpmap:0 PCMU/8000 Media
Attribute Fieldname: rtpmap Media Format: 0 MIME Type: PCMU Sample
Rate: 8000 Media Attribute (a): rtpmap:101 telephone-event/8000
Media Attribute Fieldname: rtpmap Media Format: 101 MIME Type:
telephone-event Sample Rate: 8000 Media Attribute (a): fmtp:101
0-15 Media Attribute Fieldname: fmtp Media Format: 101
[telephone-event] Media format specific parameters: 0-15 I'll look
into the B2BUA config (without the UpperReg) and see where that
leads. If there's anything here you have any thoughts on I'd
appreciate it. Thanks, jh
Jun 25, 2013 05:21 AM PDT
Jim Herold
Palatine Police Department
Sorry 'bout that. The formatting turned our really ugly there. Not
sure what I did wrong. It looked nothing like that when I hit the
post button. Here's the Client to OpenSBC: Session Initiation
Protocol (INVITE) Request-Line: INVITE sip:6273@sip.palatine.il.us
SIP/2.0 Method: INVITE Request-URI: sip:6273@sip.palatine.il.us
Request-URI User Part: 6273 Request-URI Host Part:
sip.palatine.il.us [Resent Packet: False] Message Header Via:
SIP/2.0/UDP
192.168.17.100:41584;rport;branch=z9hG4bKPjFDQNM3jOx8HYIOmF6J1Elw6zts.Q4b9a
Transport: UDP Sent-by Address: 192.168.17.100 Sent-by port: 41584
RPort: rport Branch: z9hG4bKPjFDQNM3jOx8HYIOmF6J1Elw6zts.Q4b9a
Max-Forwards: 70 From: 'PD Mobile'
;tag=LCmoVaNuVSe-cXIh.bcKncK9pUEbx8ox SIP Display info: 'PD Mobile'
SIP from address: sip:pmobile@sip.palatine.il.us SIP from address
User Part: pmobile SIP from address Host Part: sip.palatine.il.us
SIP from tag: LCmoVaNuVSe-cXIh.bcKncK9pUEbx8ox To: SIP to address:
sip:6273@sip.palatine.il.us SIP to address User Part: 6273 SIP to
address Host Part: sip.palatine.il.us Contact: Contact URI:
sip:pmobile@172.31.9.43:41584;ob Contact URI User Part: pmobile
Contact URI Host Part: 172.31.9.43 Contact URI Host Port: 41584
Contact URI parameter: ob Call-ID: PtqHQa5Zeu8tqZvpTrUZB.TQmDnV39Ii
CSeq: 27583 INVITE Sequence Number: 27583 Method: INVITE Route:
Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE,
NOTIFY, REFER, MESSAGE, OPTIONS Supported: replaces, 100rel, timer,
norefersub Session-Expires: 1800 Min-SE: 90 User-Agent:
CSipSimple_sunfire-10/r2225 Content-Type: application/sdp
Content-Length: 295 Message Body Session Description Protocol
Session Description Protocol Version (v): 0 Owner/Creator, Session
Id (o): - 3581176380 3581176380 IN IP4 192.168.17.100 Session Name
(s): pjmedia Connection Information (c): IN IP4 192.168.17.100 Time
Description, active time (t): 0 0 Media Description, name and
address (m): audio 4000 RTP/AVP 8 0 101 Connection Information (c):
IN IP4 192.168.17.100 Media Attribute (a): rtcp:4001 IN IP4
192.168.17.100 Media Attribute Fieldname: rtcp Media Attribute
Value: 4001 IN IP4 192.168.17.100 Media Attribute (a): sendrecv
Media Attribute (a): rtpmap:8 PCMA/8000 Media Attribute Fieldname:
rtpmap Media Format: 8 MIME Type: PCMA Sample Rate: 8000 Media
Attribute (a): rtpmap:0 PCMU/8000 Media Attribute Fieldname: rtpmap
Media Format: 0 MIME Type: PCMU Sample Rate: 8000 Media Attribute
(a): rtpmap:101 telephone-event/8000 Media Attribute Fieldname:
rtpmap Media Format: 101 MIME Type: telephone-event Sample Rate:
8000 Media Attribute (a): fmtp:101 0-15 Media Attribute Fieldname:
fmtp Media Format: 101 [telephone-event] Media format specific
parameters: 0-15
Jun 25, 2013 05:21 AM PDT
Jim Herold
Palatine Police Department
It's not getting better, so I'll quit while I'm ahead.
Jun 25, 2013 06:37 PM PDT
Jim Herold
Palatine Police Department
I was successful in making it work. I followed this document http://support.shoretel.com/products/ip_phones/downloads/ip_8000_config_guide.pdf to get the SIP Trunk setup. Once the SIP Trunk was setup I was able to register using OpenSBC and make both outbound and inbound calls successfully with audio function in both directions.

Thanks for your help Juan.

To reply to this post please Sign In