I started with the sample residential script from some time back. GRUU was 
enabled in the 
sample. When I started working with a UA that registers a GRUU I noticed it was 
not receiving 
BYE when the other end released the call. I have since experimented with 
checking for GRUU 
while in dialog. That seems to work. The documentation doesn't mention anything 
about 
modifying the script other than enabling or disabling GRUU. Do you have any 
tips regarding 
GRUU in the script? Are there corner cases I should be aware of?

Rob

On Wednesday, November 14, 2018 6:14:20 AM PST Bogdan-Andrei Iancu wrote:


    Hi Robert,            According to docs, the gruu is by default off - 
seehttp://www.opensips.org/
html/docs/modules/2.3.x/registrar.html#idp5567984[1]
    
Bogdan-Andrei IancuOpenSIPS Founder and Developer  
http://www.opensips-solutions.com[2]OpenSIPS Bootcamp 2018  
http://opensips.org/training/
OpenSIPS_Bootcamp_2018/[3]    
On 11/07/2018 10:09 PM, Robert Dyck      wrote:        
                  
My understanding is that GRUU processing in opensips is automatic, provided it 
is not disabled. 
No further configuration or scripting is required. Is that correct.      
      
A GRUU capable UA rergisters and receives  public and temporary GR identities. 
The UA 
establishes a dialog with another UA. The callee ends the call. The caller does 
not recive the 
BYE.      
      
Caller :      
    Request-Line: INVITE sip:7@192.168.1.2[4] SIP/2.0      
Contact URI: 
sip:4@192.168.1.2:5060;gr=urn:uuid:35dfa98a-2feb-482a-bde7-7568a86348b1[5]      
      
Callee:      
    Status-Line: SIP/2.0 200 OK      
      
Caller:      
    Request-Line: ACK sip:7@192.168.1.3:5062[6] SIP/2.0      
      
Callee:      
    Request-Line: BYE sip:4@192.168.1.2:5060;gr=urn:uuid:35dfa98a-2feb-482a-
bde7-7568a86348b1[5] SIP/2.0      
      
Proxy ( opensips @ 192.168.1.2 )      
    Status-Line: SIP/2.0 404 Not here      
      
Am I missing something?      
      
Should "opensipsctl ul show" show the GRUU?      
      
AOR:: 4       Contact:: sip:4@192.168.1.72:5062;transport=udp[7] Q=             
   ContactID:: 
3518589640418194                Expires:: 3586                Callid:: 
OL1gvsViBJ                Cseq:: 21 
               User-agent:: LinphoneAndroid/4.0.1 (belle-sip/1.6.3)             
   State:: CS_NEW 
               Flags:: 0                Cflags::                 Socket:: 
udp:192.168.1.2:5060 
               Methods:: 4294967295                SIP_instance:: 
<urn:uuid:35dfa98a-2feb-482a-
bde7-7568a86348b1>      
                        
_______________________________________________Users mailing 
listus...@lists.opensips.org[8]http://lists.opensips.org/cgi-bin/mailman/listinfo/users[9]
          



--------
[1] http://www.opensips.org/html/docs/modules/2.3.x/registrar.html#idp5567984
[2] http://www.opensips-solutions.com
[3] http://opensips.org/training/OpenSIPS_Bootcamp_2018/
[4] sip:7@192.168.1.2
[5] sip:4@192.168.1.2:5060;gr=urn:uuid:35dfa98a-2feb-482a-bde7-7568a86348b1
[6] sip:7@192.168.1.3:5062
[7] sip:4@192.168.1.72:5062;transport=udp
[8] mailto:Users@lists.opensips.org
[9] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Reply via email to