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 Shaun E on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

SBC Contact header

Status
Not open for further replies.
RedTech443

RedTech443

MIS
Nov 22, 2013
600
US
I am having some difficulty manipulating a contact header in the avaya SBC 7.1.

I have edited the topology hiding to change my to, from and request-line. But I need to edit the "contact" field so it can be routed back to the outside device properly, it is automatically populating the contact field currently with the IP address of my SBC which I think is wrong and should be the IP of my device on the outside beyond the public interface. I could be wrong but this is the only difference I can find from a known working connection on another system.

/----------------------------------------------------------------------------------------------------------------------------------------------------------------13:17:19.880 | | 10.1.30.91:46004 --TCP-> 10.1.30.171:5060 |
13:17:20.007 | |----------------------------------------------------------------------------------------------------------------------------------------------------------------|
13:17:51.012 | |REGISTER sip:homelab.com SIP/2.0 |
13:17:55.168 | |From: <sip:1050@homelab.com>;tag=qv2j6EC1qyaGzCZHEX4IUviUEJ3XVX0R |
13:17:55.171 | |To: <sip:1050@homelab.com> |
13:17:55.297 | |CSeq: 55002 REGISTER |
13:18:26.303 | |Call-ID: gnWnbEM7jX.yIbBcN6esyn7muOauMIPJ |
13:19:27.659 | |Contact: <sip:1050@10.1.30.91:5060;transport=tcp;ob;subid_ipcs=1799186741>;reg-id=1;+sip.instance="<urn:uuid:72ca3512-a3a1-4157-8fcb-ee34cddc5d47>" |
13:19:27.662 | |Route: <sip:172.85.xx.xxx:5060;transport=tcp;lr> |
13:19:27.800 | |Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS |
13:19:58.806 | |Supported: outbound, path |
13:20:52.650 | |User-Agent: CSipSimple_hero2qltevzw-23/r2457 |
13:20:52.653 | |Max-Forwards: 69 |
13:20:52.789 | |Via: SIP/2.0/TCP 10.1.30.91:5060;branch=z9hG4bK-s1632-001403696825-1--s1632- |
13:21:23.795 | |Expires: 900 |
13:22:32.971 | |Content-Length: 0 |
13:22:32.974 | \----------------------------------------------------------------------------------------------------------------------------------------------------------------/



10.1.30.91 is the ip address of my A1 interface on the private side of the SBC

IPs are

10.1.30.91 = A1 Private side
192.168.0.99 = B1 = Public side with firewall natting 5060 and a few hundread media ports to this ip.
10.1.30.171 = Session Manage security module IP

outside public IP is 172.85.xxx.xxx


 
Sort by date Sort by votes
I grabbed a full trace trying to connect, perhaps it will help.



13:44:15.502 | |<-------REGISTER-------| (435) <sip:1050@homlab.com> Exp:900
13:44:15.505 | |-----Unauthorized----->| (435) 401 Unauthorized
13:44:15.609 | |<-------REGISTER-------| (435) <sip:1050@homelab.com> Exp:900
13:44:46.615 | |--Server Internal Err->| (435) 500 Server Internal Error: Destination Unreachable




/----------------------------------------------------------------------------------------------------------------------------------------------------------------13:32:00.357 | | 10.1.30.91:40521 --TCP-> 10.1.30.171:5060 |
13:32:00.504 | |----------------------------------------------------------------------------------------------------------------------------------------------------------------|
13:32:31.509 | |REGISTER sip:homelab.com SIP/2.0 |
13:33:40.437 | |From: <sip:1050@homelab.com>;tag=oaXsqLjDjthY8jY8Cx0veEgnxhU7bXDA |
13:33:40.438 | |To: <sip:1050@homelab.com> |
13:33:40.606 | |CSeq: 58925 REGISTER |
13:34:11.611 | |Call-ID: dQxYP83vIFJ-LY4r2hVPNHroE7hpr0RR |
13:35:04.928 | |Contact: <sip:1050@10.1.30.91:5060;transport=tcp;ob;subid_ipcs=1799186741>;reg-id=1;+sip.instance="<urn:uuid:72ca3512-a3a1-4157-8fcb-ee34cddc5d47>" |
13:35:04.930 | |Route: <sip:172.85.xxx.xxx:5060;transport=tcp;lr> |
13:35:05.094 | |Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS |
13:35:36.099 | |Supported: outbound, path |
13:36:41.559 | |User-Agent: CSipSimple_hero2qltevzw-23/r2457 |
13:36:41.562 | |Max-Forwards: 69 |
13:36:41.677 | |Via: SIP/2.0/TCP 10.1.30.91:5060;branch=z9hG4bK-s1632-001009373691-1--s1632- |
13:37:12.683 | |Expires: 900 |
13:38:03.918 | |Content-Length: 0 |
13:38:03.921 | \----------------------------------------------------------------------------------------------------------------------------------------------------------------/





/----------------------------------------------------------------------------------------------------------------------------------------------------------------13:32:31.509 | | 10.1.30.171:5060 --TCP-> 10.1.30.91:40521 |
13:33:40.437 | |----------------------------------------------------------------------------------------------------------------------------------------------------------------|
13:33:40.438 | |SIP/2.0 401 Unauthorized |
13:33:40.606 | | Digest realm="homelab.com",qop="auth",opaque="1234567890abcedef",nonce="159b80b261060ff37505628ca334a002273d9fc383e",algorithm=MD5,stale=false |
13:34:11.611 | |Call-ID: dQxYP83vIFJ-LY4r2hVPNHroE7hpr0RR |
13:35:04.928 | |CSeq: 58925 REGISTER |
13:35:04.930 | |From: <sip:1050@homelab.com>;tag=oaXsqLjDjthY8jY8Cx0veEgnxhU7bXDA |
13:35:05.094 | |To: <sip:1050@homelab.com>;tag=9362177145256857_local.1484840891520_5982_5998 |
13:35:36.099 | |Via: SIP/2.0/TCP 10.1.30.91:5060;branch=z9hG4bK-s1632-001009373691-1--s1632- |
13:36:41.559 | |Av-Global-Session-ID: 47001100-de77-11e6-8bcd-000c291a55ea |
13:36:41.562 | |Server: AVAYA-SM-6.3.17.0.631705 |
13:36:41.677 | |Content-Length: 0 |
13:37:12.683 | \----------------------------------------------------------------------------------------------------------------------------------------------------------------/




/----------------------------------------------------------------------------------------------------------------------------------------------------------------13:32:00.357 | | 10.1.30.91:40521 --TCP-> 10.1.30.171:5060 |
13:32:00.504 | |----------------------------------------------------------------------------------------------------------------------------------------------------------------|
13:32:31.509 | |REGISTER sip:homelab.com SIP/2.0 |
13:33:40.437 | |From: <sip:1050@homelab.com>;tag=oaXsqLjDjthY8jY8Cx0veEgnxhU7bXDA |
13:33:40.438 | |To: <sip:1050@homelab.com> |
13:33:40.606 | |CSeq: 58926 REGISTER |
13:34:11.611 | |Call-ID: dQxYP83vIFJ-LY4r2hVPNHroE7hpr0RR |
13:35:04.928 | |Contact: <sip:1050@10.1.30.91:5060;transport=tcp;ob;subid_ipcs=1799186741>;reg-id=1;+sip.instance="<urn:uuid:72ca3512-a3a1-4157-8fcb-ee34cddc5d47>" |
13:35:04.930 | |Route: <sip:172.85.xxx.xxx:5060;transport=tcp;lr> |
13:35:05.094 | |Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS |
13:35:36.099 | |Supported: outbound, path |
13:36:41.559 | |User-Agent: CSipSimple_hero2qltevzw-23/r2457 |
13:36:41.562 | |Max-Forwards: 69 |
13:36:41.677 | |Via: SIP/2.0/TCP 10.1.30.91:5060;branch=z9hG4bK-s1632-001763007635-1--s1632- |
13:37:12.683 | |Expires: 900 |
13:38:03.918 | |Authorization: Digest username="1050", realm="homelab.com", nonce="159b80b261060ff37505628ca334a002273d9fc383e", uri="sip:172.85.xxx.xxx:5060", response="8f6d7320|
13:38:03.921 | |d75d2870a03eaf827953cea0", algorithm=MD5, cnonce="vDTgDQcHVnosPsO358jQo8b5Pa3Rgw1B", opaque="1234567890abcedef", qop=auth, nc=00000001 |
13:38:04.028 | |Content-Length: 0 |
13:38:35.034 | \----------------------------------------------------------------------------------------------------------------------------------------------------------------/




/----------------------------------------------------------------------------------------------------------------------------------------------------------------13:33:40.437 | | 10.1.30.171:5060 --TCP-> 10.1.30.91:40521 |
13:33:40.438 | |----------------------------------------------------------------------------------------------------------------------------------------------------------------|
13:33:40.606 | |SIP/2.0 500 Server Internal Error: Destination Unreachable |
13:34:11.611 | |Server: AVAYA-AP-6.3.17.0.631701 AVAYA-SM-6.3.17.0.631705 |
13:35:04.928 | |Av-Global-Session-ID: 47103da0-de77-11e6-8bcd-000c291a55ea |
13:35:04.930 | |Record-Route: <sip:10.1.30.172:15060;transport=tcp;ibmsid=local.1484840891520_5983_5999;lr> |
13:35:05.094 | |From: <sip:1050@homelab.com>;tag=oaXsqLjDjthY8jY8Cx0veEgnxhU7bXDA |
13:35:36.099 | |To: <sip:1050@homelab.com>;tag=AP516f24d9-18a045ec |
13:36:41.559 | |Call-ID: dQxYP83vIFJ-LY4r2hVPNHroE7hpr0RR |
13:36:41.562 | |CSeq: 58926 REGISTER |
13:36:41.677 | |Via: SIP/2.0/TCP 10.1.30.91:5060;branch=z9hG4bK-s1632-001763007635-1--s1632- |
13:37:12.683 | |Content-Length: 0 |
13:38:03.918 | \----------------------------------------------------------------------------------------------------------------------------------------------------------------/
13:38:03.921 | |-----Unauthorized----->| (385) 401 Unauthorized
 
Upvote 0 Downvote
You can probably manipulate that with a sigma script. There might be checkboxes in the SBC to convert it as a stock feature, otherwise all the devconnect notes to interop with SIP vendors have something like that to change certain parameters going out to the carrier.


I need to get better at writing them...

Maybe you need to pass your account number like the 6 digit one. Otherwise, this might change your contact header:

within session "ALL"
{
act on message where %DIRECTION="OUTBOUND" and %ENTRY_POINT="POST_ROUTING" and

{
if(exists(%HEADERS["Contact"][1]))then
{
Remove(%HEADERS["Contact"][1]);
append(%HEADERS["Contact"][1],"1050@whateverIPyouwant");
}
}
}
 
Upvote 0 Downvote
The only way I could get it to save was to tweak it a bit, but it still did not fix my problem after applying it to the server flow. Something else is causing my headache it appears. I get various result when playing with the topology hiding and URI Groups for allowed extensions I created. I will test more later.




within session "ALL"
{
act on message where %DIRECTION="OUTBOUND" and %ENTRY_POINT="POST_ROUTING"
{
if(exists(%HEADERS["Contact"][1]))then
{
%DivUser = %HEADERS["Contact"][1];

remove(%HEADERS["Contact"][1].DISPLAY_NAME);
append(%HEADERS["Contact"][1],"1050@xxx.xxx.xx.xxx");
}
}
}

 
Upvote 0 Downvote
I'd say maybe use public unknown numbering in CM to send the test # the sip service gave you rather than 1050. If they don't know about 1050, maybe that's why they're rejecting you?
 
Upvote 0 Downvote
Sorry think I forgot to mention in this post, this is for a single Remote worker logging in through the SBC via android device using either Csipsimple or Avaya Equinox.
I am fairly sure it has something to do with the Topology hiding but I can't seem to figure it out, changing the contact header did not make any difference, but playing with topology hiding has various results.



 
Upvote 0 Downvote
So you want a remote worker to call out your sip trunks? I'd say maybe get an on-net user out first and go from there.

I still think you'd need to be "from" a valid extension that the SIP carrier gave you, so public numbering would still be relevant
 
Upvote 0 Downvote
For simplicity right now I think I will just send all calls sip out my current CO trunks. So if a Remote worker logs in via android/one-x they will route calls out my CO trunks. Once I get that working and the remote worker logged in correctly I can then work on the sip trunk and routing for that trunk.



 
Upvote 0 Downvote
So first appearance is you want to NAT the external address. You can do this by assigning the public address in the network settings of the network interfaces. This should update your contact header. Make sure any SIP AGL is disabled in your NAT device.
 
Upvote 0 Downvote
Finally was able to get a device to register, for some reason I decided to use one of my tablets laying around with 4g connection. That worked right away, my other android device I was testing with does not work at all for some reason. There is no difference between the 2 devices as they are both newish. Both traces show up exactly the same except the one that does not work just hangs at registering like its being firewall blocked or something.

The one tablet that connects can accept calls but I only get audio for about 1/2 - 1 second then it drops audio but remains in call. It can not dial out to internal extensions or outside numbers yet. I suspect I am going to have to battle my opensource firewall to get it to work properly as I think pfsense firewalls have lots of issues with RTP traffic and sip related stuff still.

I am getting there in baby steps. Soon ill have this down and will be able to help others for a change lol :)




 
Upvote 0 Downvote
Guess I spoke too soon.

After a few successful logins I started to get the below error, however if I wait about 10 minutes I can log back in.. Very odd.


SIP: 400 Invalid Request (more than one contact in REGISTER)

|
18:03:01.222 |--NOTIFY\----------------------------------------------------------------------------------------------------------------------------------------------------------------/
18:03:09.234 |--NOTIFY-->| | | | | | SIP: sip:1050@10.1.30.91:5060 Ev:reg Exp:0
18:03:33.261 |<-Request--| | | | | | SIP: 408 Request Timeout
18:03:41.269 |<-Request--| | | | | | SIP: 408 Request Timeout
18:03:49.277 | |<-REGISTE--| | | | | SIP: sip:192.168.0.99:5060 Exp:900
18:03:49.277 |<-REGISTE--| | | | | | SIP: sip:kb1ojr.com Exp:900
18:03:49.277 |--Unautho->| | | | | | SIP: 401 Unauthorized
18:03:49.277 | |--Unautho->| | | | | SIP: 401 Unauthorized
18:03:49.277 | |<-REGISTE--| | | | | SIP: sip:192.168.0.99:5060 Exp:0
18:03:49.277 |<-REGISTE--| | | | | | SIP: sip:homelab.com Exp:0
18:03:49.277 |--Invalid->| | | | | | SIP: 400 Invalid Request (more than one contact in REGISTER)
18:03:49.277 | |--Invalid->| | | | | SIP: 400 Invalid Request (more than one contact in REGISTER)
18:03:52.280 |--NOTIFY-->| | | | | | SIP: sip:1050@10.1.30.91:5060 Ev:reg
18:04:24.319 |<-Request--| | | | | | SIP: 408 Request Timeout
18:04:45.346 | |<-REGISTE--| | | | | SIP: sip:192.168.0.99:5060 Exp:900
18:04:45.347 |<-REGISTE--| | | | | | SIP: sip:homelab.com Exp:900
18:04:45.347 |--Unautho->| | | | | | SIP: 401 Unauthorized
18:04:45.347 | |--Unautho->| | | | | SIP: 401 Unauthorized
18:04:46.348 | |<-REGISTE--| | | | | SIP: sip:192.168.0.99:5060 Exp:0
18:04:46.348 |<-REGISTE--| | | | | | SIP: sip:homelab.com Exp:0
18:04:46.348 |--Invalid->| | | | | | SIP: 400 Invalid Request (more than one contact in REGISTER)
18:04:46.348 | |--Invalid->| | | | | SIP: 400 Invalid Request (more than one contact in REGISTER)


below is zoomed in on the last invalid line.

/----------------------------------------------------------------------------------------------------------------------------------------------------------------18:02:26.167 |<-Reques| 192.168.0.99:5060 --UDP-> 174.199.7.183:8053 |
18:02:41.190 ||----------------------------------------------------------------------------------------------------------------------------------------------------------------|
18:02:43.194 ||SIP/2.0 400 Invalid Request (more than one contact in REGISTER) |
18:02:43.194 ||From: <sip:1050@192.168.0.99:5060>;tag=s689+1+425d0000+59b7057e |
18:02:43.194 ||To: <sip:1050@192.168.0.99:5060>;tag=7957125597684703_local.1484916539664_22679_22945 |
18:02:43.194 ||CSeq: 48341 REGISTER |
18:02:43.194 ||Call-ID: Og4NzYvBK-5jFgFbrML2Pc9ksM9LNxBC |
18:02:43.194 ||Via: SIP/2.0/UDP 174.199.7.xxx:8053;rport=8053;branch=z9hG4bK+7f92e1476578d6bb8f6ac3a5893614081+s689+1 |
18:02:43.194 ||Server: AVAYA-SM-6.3.17.0.631705 |
18:02:43.194 | |Av-Global-Session-ID: d5a087d0-df64-11e6-92e5-000c291a55ea |
18:03:01.222 ||Content-Length: 0 |






 
Upvote 0 Downvote
Its like a roller coaster.

OK so now I turned off shuffling on the signaling group and was able to call from internal network to external SBC device and everything worked, calling back in rings the internal device but it quickly hangs up. Any suggestions, I am at a wall for this evening with this thing.


update: Trace shows below when I dial from inside network to outside SBC device. Like it is getting routed wrong or something.


18:29:04.479 | |<--CANCEL--| | | SIP: sip:1050@10.1.30.91:5060
18:29:04.479 | |--Call Le->| | | SIP: 481 Call Leg/Transaction does not exist





 
Upvote 0 Downvote
Status
Not open for further replies.

Similar threads

jesryll27
  • Question
SIP trunking between Audiocodes SBC M800 to Avaya CM7
Replies
4
Views
251
mattKnight
mattKnight
fondog2
  • Locked
  • Question
SBC Signal Manipulation script 1
Replies
4
Views
1K
JefferP
JefferP
fondog2
  • Locked
  • Question
ASM to SBC link down
Replies
2
Views
827
fondog2
fondog2
fondog2
  • Locked
  • Question
SBC Trunk/Remote worker registration
Replies
0
Views
486
fondog2
fondog2
Saaggs
  • Locked
  • Question
Incoming calls not showing the contact name
Replies
0
Views
525
Saaggs
Saaggs

Part and Inventory Search

Sponsor

Back
Top