Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

Register Log in
  • Congratulations derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

No Incoming SIP

Status
Not open for further replies.
KyBoy

KyBoy

Technical User
Joined
Jan 4, 2010
Messages
119
Location
US
Should i be able to see my phone number in monitor if the IPO is rejecting the incoming call to SIP trunk 17. i have followed Avaya application notes and cannot receive inbound.
 
Sort by date Sort by votes
333519mS SIP Reg/Opt Tx: 17
REGISTER sip:10.10.3.1 SIP/2.0
Via: SIP/2.0/UDP 10.10.3.2:5060;rport;branch=z9hG4bK82bf4e59d650c4bacd8f6d047e8c5bb3
From: <sip:pbxadmin@10.10.3.1>;tag=a8737fe54443c81d
To: <sip:pbxadmin@10.10.3.1>
Call-ID: 76385ab5309ac17ec9c6fd5e6523fddb
CSeq: 1681855912 REGISTER
Contact: "Unknown" <sip:pbxadmin@10.10.3.2:5060;transport=udp>
Expires: 3600
Max-Forwards: 70
User-Agent: IP Office 9.0.5.0 build 972
Supported: timer
Content-Length: 0

Windstream says this is the reason i cannot receive inbound. from 10.10.3.1 to 10.10.3.1
 
Upvote 0 Downvote
On the SIP line tab on the ip office, is your call routing method "to header" or "request uri"?
 
Upvote 0 Downvote
To header
 
Upvote 0 Downvote
Change to "request uri"... Looks like your provider is using an edgemark device.
 
Upvote 0 Downvote
I will try it thanks
 
Upvote 0 Downvote
That's a REGISTER event, the question is what answer you get?
Is the trunk actually registered towrads the SIP provider?

What happens when you do an outgoing call?

Changing the routing method won't do much good if you don't even get the INVITE to the IPO.

"Trying is the first step to failure..." - Homer
 
Upvote 0 Downvote
Yes I can make outbound just fine. In system status line 17 I can see peered with windstream and lines idle
 
Upvote 0 Downvote
Actually the call routing method is request URI
 
Upvote 0 Downvote
I tried to header and still no inbound. I have a challenge $100 to the person that can figure this problem out with litte info mind you. Haha
 
Upvote 0 Downvote
I guess everyone is SIP intolerant
 
Upvote 0 Downvote
Janni78 when calling from a cell I get busy. When calling on internal meta switch I get a network problem your call can not be completed
 
Upvote 0 Downvote
This is wild guessing as you do not provide any info.
Incoming means most of the time no URI configure for incoming calls.
Make a monitor trace when you try to call in and stop when you are hangup.

BAZINGA!

I'm not insane, my mother had me tested!

 
Upvote 0 Downvote
For the first step to find out what happens you can also gave a look with SSA into the SIP line with call details enabled.
 
Upvote 0 Downvote
OK I am now able to see the IPO reject the call. I have a ICR DID 859219XXXX set with line group 17 to extension 229. in the SIP tap of 229 i have the DID programmed under SIP name and contact name. I have 2 URI set up

1: VIA 10.10.3.2 2: VIA 10.10.3.2
local URI use internal data local URI *
contact use internal data contact *
display name use internal data display name *
PIA use internal data PIA none
Registration 1: pbxadmin Registration 1: pbxadmin
incoming group 18 incoming group 17
outgoing group 17 outgoing group 18
max call per channel 10 max call per channel 10

Here is what i get in monitor, however i dont see my cell number in the invite any where
10.10.3.1 is proxy and 10.10.3.2 is WAN

393431mS SIP Tx: UDP 10.10.3.2:5060 -> 10.10.3.1:5060
OPTIONS sip:10.10.3.1 SIP/2.0
Via: SIP/2.0/UDP 10.10.3.2:5060;rport;branch=z9hG4bK520c44b49c347889f4893d20d3bddaed
From: <sip:10.10.3.2>;tag=6d89f31bdf239246
To: <sip:10.10.3.1>
Call-ID: b2feb70f569100611aac298246a26e6f
CSeq: 1082045782 OPTIONS
Contact: <sip:10.10.3.2:5060;transport=udp>
Max-Forwards: 70
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,INFO,NOTIFY,UPDATE
Supported: timer
User-Agent: IP Office 9.0.5.0 build 972
Content-Length: 0
 
Upvote 0 Downvote
This is the only caller ID it shows


393433mS SIP Rx: UDP 10.10.3.1:5060 -> 10.10.3.2:5060
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.10.3.2:5060;rport;branch=z9hG4bK520c44b49c347889f4893d20d3bddaed
From: <sip:10.10.3.2>;tag=6d89f31bdf239246
To: <sip:10.10.3.1>
Call-ID: b2feb70f569100611aac298246a26e6f
CSeq: 1082045782 OPTIONS
Contact: <sip:10.10.3.2:5060;transport=udp>
Content-Length: 0
 
Upvote 0 Downvote
The URI info is messed up
2 URI set up
1 via 10.10.3.2 local URI, contact, display name and PAI is use internal data- Registration pbxadmin - incoming group 18 - outgoing group 17 - max calls per channel 10.

2 VIA 10.10.3.2 local URI *, contact name *, display name * and PAI none - Registration pbxadmin - incoming group 17 - outgoing group 18 - max calls per channel 10.
 
Upvote 0 Downvote
Which part of this sentence don't you understand?

Make a monitor trace when you try to call in and stop when you are hangup.

Make a monitor trace while you try to call the number.
Your part of the trace shows nothing at all.

BAZINGA!

I'm not insane, my mother had me tested!

 
Upvote 0 Downvote
I did Peter if you go up in the post you will see a monitor trace
 
Upvote 0 Downvote
393431mS SIP Reg/Opt Tx: 17
OPTIONS sip:10.10.3.1 SIP/2.0
Via: SIP/2.0/UDP 10.10.3.2:5060;rport;branch=z9hG4bK520c44b49c347889f4893d20d3bddaed
From: <sip:10.10.3.2>;tag=6d89f31bdf239246
To: <sip:10.10.3.1>
Call-ID: b2feb70f569100611aac298246a26e6f
CSeq: 1082045782 OPTIONS
Contact: <sip:10.10.3.2:5060;transport=udp>
Max-Forwards: 70
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,INFO,NOTIFY,UPDATE
Supported: timer
User-Agent: IP Office 9.0.5.0 build 972
Content-Length: 0

393431mS SIP Tx: UDP 10.10.3.2:5060 -> 10.10.3.1:5060
OPTIONS sip:10.10.3.1 SIP/2.0
Via: SIP/2.0/UDP 10.10.3.2:5060;rport;branch=z9hG4bK520c44b49c347889f4893d20d3bddaed
From: <sip:10.10.3.2>;tag=6d89f31bdf239246
To: <sip:10.10.3.1>
Call-ID: b2feb70f569100611aac298246a26e6f
CSeq: 1082045782 OPTIONS
Contact: <sip:10.10.3.2:5060;transport=udp>
Max-Forwards: 70
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,INFO,NOTIFY,UPDATE
Supported: timer
User-Agent: IP Office 9.0.5.0 build 972
Content-Length: 0

393433mS SIP Rx: UDP 10.10.3.1:5060 -> 10.10.3.2:5060
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.10.3.2:5060;rport;branch=z9hG4bK520c44b49c347889f4893d20d3bddaed
From: <sip:10.10.3.2>;tag=6d89f31bdf239246
To: <sip:10.10.3.1>
Call-ID: b2feb70f569100611aac298246a26e6f
CSeq: 1082045782 OPTIONS
Contact: <sip:10.10.3.2:5060;transport=udp>
Content-Length: 0

393434mS SIP Reg/Opt Rx: 17
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.10.3.2:5060;rport;branch=z9hG4bK520c44b49c347889f4893d20d3bddaed
From: <sip:10.10.3.2>;tag=6d89f31bdf239246
To: <sip:10.10.3.1>
Call-ID: b2feb70f569100611aac298246a26e6f
CSeq: 1082045782 OPTIONS
Contact: <sip:10.10.3.2:5060;transport=udp>
Content-Length: 0

393530mS SIP Reg/Opt Tx: 17
REGISTER sip:10.10.3.1 SIP/2.0
Via: SIP/2.0/UDP 10.10.3.2:5060;rport;branch=z9hG4bKbcec8d9634d6878249e5871eae2ff0f0
From: <sip:pbxadmin@10.10.3.1>;tag=5aa9a6d8186937eb
To: <sip:pbxadmin@10.10.3.1>
Call-ID: 76385ab5309ac17ec9c6fd5e6523fddb
CSeq: 1681855914 REGISTER
Contact: "Unknown" <sip:pbxadmin@10.10.3.2:5060;transport=udp>
Expires: 3600
Max-Forwards: 70
User-Agent: IP Office 9.0.5.0 build 972
Supported: timer
Content-Length: 0

393530mS SIP Tx: UDP 10.10.3.2:5060 -> 10.10.3.1:5060
REGISTER sip:10.10.3.1 SIP/2.0
Via: SIP/2.0/UDP 10.10.3.2:5060;rport;branch=z9hG4bKbcec8d9634d6878249e5871eae2ff0f0
From: <sip:pbxadmin@10.10.3.1>;tag=5aa9a6d8186937eb
To: <sip:pbxadmin@10.10.3.1>
Call-ID: 76385ab5309ac17ec9c6fd5e6523fddb
CSeq: 1681855914 REGISTER
Contact: "Unknown" <sip:pbxadmin@10.10.3.2:5060;transport=udp>
Expires: 3600
Max-Forwards: 70
User-Agent: IP Office 9.0.5.0 build 972
Supported: timer
Content-Length: 0

393532mS SIP Rx: UDP 10.10.3.1:5060 -> 10.10.3.2:5060
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.10.3.2:5060;rport;branch=z9hG4bKbcec8d9634d6878249e5871eae2ff0f0
From: <sip:pbxadmin@10.10.3.1>;tag=5aa9a6d8186937eb
To: <sip:pbxadmin@10.10.3.1>
Call-ID: 76385ab5309ac17ec9c6fd5e6523fddb
CSeq: 1681855914 REGISTER
Contact: "Unknown" <sip:pbxadmin@10.10.3.2:5060;transport=udp>;expires=60
Content-Length: 0

393534mS SIP Reg/Opt Rx: 17
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.10.3.2:5060;rport;branch=z9hG4bKbcec8d9634d6878249e5871eae2ff0f0
From: <sip:pbxadmin@10.10.3.1>;tag=5aa9a6d8186937eb
To: <sip:pbxadmin@10.10.3.1>
Call-ID: 76385ab5309ac17ec9c6fd5e6523fddb
CSeq: 1681855914 REGISTER
Contact: "Unknown" <sip:pbxadmin@10.10.3.2:5060;transport=udp>;expires=60
Content-Length: 0
 
Upvote 0 Downvote
Status
Not open for further replies.

Similar threads

William C290
  • Solved
Avaya SBC – Dual SIP Trunks via VLAN Tagging (No Gateway Reachability)
Replies
5
Views
269
William C290
William C290
Jouik
  • Locked
  • Question Question
Incoming calls Caller ID Name not showing on SIP Phones although received in Monitor trace
Replies
1
Views
492
Mo. Abdullah
Mo. Abdullah
Imran555
  • Locked
  • Question Question
Incoming caller ID with SIP server IP over SIP Trunks
Replies
1
Views
1K
ipohead
ipohead
DiyFrea
  • Locked
  • Question Question
SIP trunk - no audio
Replies
9
Views
2K
derfloh
derfloh
sheldoom
  • Locked
  • Question Question
No response to SIP Options Messages
Replies
1
Views
626
sheldoom
sheldoom

Part and Inventory Search

Sponsor

Back
Top